A remote-support session on Linux starts with choosing a tool that can connect one computer to another. RustDesk is an open-source remote desktop client that lets you control another device through its public servers or a server you run yourself.
I’ll show you how to connect to another device with RustDesk on Linux and explain what you need to maintain if you run your own server.
TL;DR: RustDesk as a TeamViewer alternative
RustDesk is a reasonable TeamViewer alternative when you want an open-source remote desktop client and the option to operate your own connection servers. The main decision is whether the public-server setup is enough or whether your team can maintain a self-hosted service.
- Install the Linux package that matches your distribution from RustDesk’s official release page.
- For an attended session, exchange the peer ID and one-time password through a trusted channel.
- Self-hosting gives you control of the rendezvous and relay infrastructure, and adds server, network and update work.
- RustDesk’s Linux documentation calls Wayland support experimental and says access to a Wayland login screen still requires X11.
What is RustDesk?
RustDesk is an open-source remote desktop client for connecting to and controlling another device. It can use RustDesk’s public servers or a server that you deploy and configure yourself.
TeamViewer is a managed remote-access service, while RustDesk’s distinctive option is its self-hostable backend. That changes who runs the connection infrastructure, not the basic task of opening a remote session. The official RustDesk client documentation lists Linux distributions, Windows, macOS, Android and other clients, with platform-specific limits.
How does a RustDesk connection work?
The ID server, called hbbs in the self-hosting docs, helps clients find one another and try a direct connection. When a direct peer connection cannot be established, the relay server, hbbr, carries the session traffic.
Clients first try a direct connection. Self-hosting means you maintain the rendezvous and relay services when needed.
How to connect with RustDesk on Linux
A standard attended session starts with both people running RustDesk clients, then the connecting person enters the other device’s ID. Use the official Linux guide to choose a package, because its release assets and distribution formats can change.
Step 1: Choose the matching Linux package
Open RustDesk’s official releases page and select the asset for your distribution and CPU architecture. Its Linux documentation maps Debian-based distributions to DEB packages, Fedora-based systems to RPM, Arch and Manjaro to package archives, and also documents AppImage and Flatpak options. Prefer your distribution’s native package when it is available.
Do not copy an old versioned download URL from a tutorial. The release page currently presents its latest build and points readers to additional Fedora, Arch, SUSE and AppImage downloads. Confirm the filename against your system before installing it.
Step 2: Open the client and find its ID
Start RustDesk from your desktop’s application menu. Its client guide says the home screen shows your device ID and one-time password, plus a field for entering another computer’s ID. Keep the password private and share it only with the person you intend to let into that session.
For support, give the helper your ID and share the one-time password only when you are ready to approve the request. They enter your ID and select Connect. Confirm the request on the device being controlled.
Step 3: Point both clients to a self-hosted server
If you run RustDesk Server OSS or Pro, configure the connecting and controlled clients to use the server’s ID address and public Key. In the client, open the menu beside your ID, go to Settings, then Network, and unlock the network settings before entering the values.
For a basic self-hosted setup, configure the ID Server address and public Key. The public Key encrypts connections, not a commercial license. Follow the deployment guide before changing firewall rules.
Step 4: Confirm the session and permissions
A successful connection opens the remote desktop. Confirm it is the intended device, allow only needed access and end the session when support is done.
What changes when you self-host RustDesk?
RustDesk clients can use public servers, so self-hosting is optional. A private deployment fits a team that needs to operate its own rendezvous and relay services and has an administrator to maintain them.
| Choice | Who operates the servers | What to plan for |
|---|---|---|
| RustDesk public servers | RustDesk | Quick start, with reliance on the public service |
| Server OSS | You | Deploy and maintain hbbs/hbbr, keys and network access |
| Server Pro | You | Self-hosted backend and commercial administration features |
RustDesk’s docs say hbbs helps clients find each other and attempt a direct connection. If that fails, hbbr relays the session. Check the official port requirements before exposing a server.
Self-host only if someone can maintain updates, keys, backups and network access. It shifts operational control and responsibility to you, it does not guarantee security.
Server OSS is the open-source backend. Server Pro adds commercial administration features, so check the current product docs for terms.
Linux limits to check before switching
RustDesk’s Linux support depends on the desktop session and package format. Check these limits on the machines you support.
| Area | Documented boundary | Check |
|---|---|---|
| Wayland | Experimental support | Test your desktop session |
| Login screen | Wayland login screen is unsupported | X11 is required for that workflow |
| Linux updates | Manual download and install | Track the package format and releases |
For connection problems, compare the ID Server and public Key first, then check server reachability. Expose only ports required for the features you use.
Conclusion: choose the server model you can maintain
RustDesk can replace TeamViewer for Linux users who want an open-source remote desktop client and are comfortable with its public-server or self-hosted model. Try an attended session first, then make self-hosting a separate decision based on who will maintain the service and whether your Linux desktop workflow is supported.
For the next step, check the official RustDesk Linux installation guide and the self-hosting documentation. On LinuxForDevices, see our guides to installing TeamViewer, installing AnyDesk, running AppImages, installing DEB packages, and using Paru on Arch Linux.
FAQ
These answers cover the decisions that change whether RustDesk fits your remote-support setup.
Is RustDesk a free TeamViewer alternative?
RustDesk’s client and Server OSS are open source, and its public client can be used without running your own server. Server Pro is a separate commercial offering, so check the current RustDesk pricing and feature pages for its terms.
Does RustDesk work on Linux with Wayland?
RustDesk documents Wayland support as experimental. Controlling the login screen under Wayland is not supported, so RustDesk’s Linux guide says that workflow still requires X11.
Do I need to self-host a server to use RustDesk?
No. RustDesk clients can use the public servers. Self-host a server when you want to operate the rendezvous and relay infrastructure yourself and can maintain it.
What information does a self-hosted RustDesk client need?
For a basic self-hosted setup, configure the ID Server address and the server’s public Key. Relay Server can generally remain blank unless you need to set it explicitly, and API Server is used for Pro features.