RustDesk Help

RustDesk FAQ

Find answers about RustDesk remote connections, client installation, self-hosted Server OSS, permissions, platform limitations and Server Pro. Use the download page for installers and the documentation for hbbs, hbbr, ports and Docker Compose deployment.

Remote Connections

Does every RustDesk connection pass through a Relay Server?

No. RustDesk first uses the ID Server to locate the remote device and coordinate the endpoints. It then attempts NAT hole punching to establish a direct P2P connection. If the direct connection fails, communication can fall back to the Relay Server.

What changes when I use my own RustDesk Server?

When both endpoints are configured for your self-hosted environment, they use your own ID and Relay infrastructure instead of the default RustDesk public infrastructure for registration, connection coordination and relay fallback.

Do two devices on the same network still need the relay?

Not necessarily. If the endpoints can establish a direct connection, the remote session does not need to pass through hbbr. Whether direct connectivity succeeds depends on routing, NAT, firewall rules and the actual network environment.

Can RustDesk transfer files and use the clipboard?

Yes. RustDesk supports remote desktop sessions, clipboard synchronization and file-transfer workflows. The exact features available depend on the client platform, permissions and session settings.

What should I check when RustDesk cannot connect?

For a self-hosted setup, confirm that both endpoints use the correct ID Server and Key, that hbbs and hbbr are running, and that the required ports are reachable. If the connection starts but the screen or input does not work, also check operating-system permissions. See the troubleshooting section.

What does someone need to connect to my device?

They need the RustDesk ID of the device they want to reach and must complete the configured authorization method, such as a one-time password, permanent password or local confirmation. Each RustDesk device has its own ID.

Platforms

Which platforms does RustDesk support?

RustDesk provides clients for desktop, mobile and web environments. Installation methods and the ability to act as a controller or controlled endpoint vary by platform. See the download page for current packages.

Can an Android phone be controlled remotely?

Yes. Android can receive RustDesk control requests after its screen-sharing service is started and the necessary permissions are granted. Screen Capture is required to share the display, while Input Control is required for remote taps and gestures.

Can RustDesk remotely control an iPhone or iPad?

No. The current iOS client can act as a controller and connect to other supported devices, but an iPhone or iPad cannot currently be used as a controlled RustDesk endpoint.

Can RustDesk connect to the Linux login screen after a reboot?

It depends on the display environment. RustDesk has experimental Wayland support, but remote access to the Linux login screen still requires an X11 login environment in the standard client. Do not assume every Linux installation supports unattended access from the login screen by default.

Do Apple Silicon and Intel Macs use different downloads?

Yes. Apple Silicon Macs use the ARM64 build, while Intel Macs use the x86_64 build. Both can use RustDesk, but you should install the package that matches the processor architecture.

What if the main download cards do not list my architecture?

Check the Other Builds section on the download page. RustDesk provides additional Windows, Linux and Android packages for different processor architectures and package formats.

Installation

Why does RustDesk show a device ID after installation?

When the client starts and reaches its configured ID Server, the device registers and receives its own RustDesk ID. That ID identifies the individual device; multiple devices do not share one ID.

Do I have to self-host a server before using RustDesk?

No. The standard RustDesk client can use RustDesk public infrastructure. If you want to operate your own ID and Relay infrastructure, configure the client to use RustDesk Server OSS or Server Pro.

Where should I install RustDesk on Android and iOS?

RustDesk's Android documentation provides the APK through its GitHub distribution, while the iPhone and iPad client is available through the Apple App Store. Use the current download page to reach the appropriate package or store listing.

Can I deploy RustDesk with my server settings already configured?

Yes. Self-hosted settings can be configured manually, exported and imported between clients, or applied through deployment scripts and the --config command-line option. Server Pro also provides a Custom Client Generator for managed custom clients.

Self-Hosting

What services are required for RustDesk Server OSS?

RustDesk Server OSS consists of two core services. hbbs is the ID, rendezvous and signaling server used for registration, discovery and connection coordination. hbbr is the Relay Server used when the endpoints cannot establish a direct connection.

Which ports does RustDesk Server use?

The documented core range is TCP 21114–21119 plus UDP 21116. For basic RustDesk operation, ports 21115–21117 plus UDP 21116 are the minimum set used for signaling, NAT traversal and relay. Web Client and Server Pro features can require additional ports.

What is the difference between Server OSS and Server Pro?

Server OSS is the free, open-source self-hosted backend built around hbbs and hbbr. Server Pro adds centralized administration including a Web Console, API, OIDC, LDAP, 2FA, device management, access control, address books, log management and multiple relay management.

Does self-hosting force all remote traffic through my server?

No. RustDesk still attempts a direct P2P connection first. Your hbbr server is used when NAT traversal or other network conditions prevent the two endpoints from connecting directly.

Is Docker alone enough for a production RustDesk Server?

Docker is a common deployment method, but the server also needs correct networking, firewall rules, reachable ports, DNS or IP addressing, persistent data and appropriate security controls. Production requirements depend on your environment.

Can RustDesk Server run only inside an intranet?

Yes, if every client that needs to use the server can reach it. An internal-only deployment can use private addressing, while access from external networks requires an appropriate route such as public reachability, VPN or another network design.

Client Configuration

What settings do most self-hosted clients need?

Most clients need an ID Server and the server Key. The ID Server normally points to hbbs. Relay Server is often optional because RustDesk can infer it, while API Server is mainly used with Server Pro account and Web Console features.

What is the Key in RustDesk network settings?

It is the public key used for encrypted communication with the self-hosted RustDesk Server. It is normally generated when hbbs first runs and stored in id_ed25519.pub. It is not the same thing as a Server Pro license key.

Do all of my devices use the same RustDesk ID?

No. Every device has its own RustDesk ID. Multiple clients can use the same ID Server and Relay Server infrastructure, but their device identities remain separate.

Does every client have to be configured manually?

No. You can manually configure a small number of devices, export and import Server Config, or use deployment scripts and the --config option for larger rollouts.

Can I use my own name, logo and icon?

RustDesk Server Pro includes a Custom Client Generator that supports custom name, logo, icon, configuration and signing options. This should not be confused with the basic Server OSS feature set.

Can different users or teams have different access policies?

Local client permissions can be configured per device. Organizations using Server Pro can add centralized access control, roles, strategies and other policy features to manage which users can reach particular devices and what actions they are allowed to perform.

Permissions and Security

Why does a remote Mac show a black screen?

A common cause is missing macOS permissions. A Mac that will be controlled remotely normally needs Screen Recording and Accessibility permissions. Input Monitoring may also be needed when keyboard or mouse input still does not work.

Why can I see an Android screen but not control it?

Screen sharing and remote input use separate Android permissions. Screen Capture allows RustDesk to share the display, while Input Control enables remote touch input through the RustDesk Input accessibility service.

Can clipboard, file transfer and input permissions be controlled separately?

Yes. RustDesk client security settings can restrict different remote-session capabilities. Server Pro can add centralized access-control and policy management on top of local client permissions.

How should I secure unattended access?

Use a strong, unique permanent password and only enable unattended access where it is required. Limit who receives device IDs and credentials, review client security settings and use additional controls such as allowlists or two-factor authentication where your deployment supports them.

Logs, Address Books and Data

Does Server OSS include a centralized address book and audit console?

No. Server OSS primarily provides hbbs and hbbr for connection infrastructure. Centralized address books, device management, Web Console administration and log-management features belong to RustDesk Server Pro.

What logging features are available in Server Pro?

Server Pro includes log-management features for activities such as remote connections, file transfers and security alarms, along with administrative management through the Web Console.

Can rustdeskapp.com see my remote desktop screen?

Browsing this website does not give the site access to your RustDesk remote screen, keyboard input, clipboard or remote files. Remote-session behavior depends on the RustDesk clients and infrastructure you actually use. See the Privacy Policy.

Who controls access to devices in a self-hosted deployment?

Access depends on the client security settings and the server edition you deploy. Server OSS provides the connection infrastructure, while Server Pro can add centralized user, device and access-control policies.

Use Cases

Is RustDesk suitable for remote IT support?

Yes. An authorized support technician can connect to a remote device, view its desktop and, when the required permissions are granted, operate the system and use supported session tools such as clipboard or file transfer.

Can RustDesk be used for remote work?

Yes. A user can connect to an available work device from another location and use applications and files through the remote desktop, subject to the security and access settings configured on the remote device.

Can RustDesk manage machines that stay online in a server room?

Yes, but unattended behavior depends on the operating system and display environment. On Linux in particular, Wayland login screens are not currently supported in the standard client, so X11 may be required for access after a reboot or logout.

Can I start a RustDesk session from a browser?

RustDesk provides a Web Client. A self-hosted Web Client requires the appropriate WebSocket ports and HTTPS/WSS reverse-proxy configuration, and browser security restrictions can make its capabilities differ from the native desktop client.

Choosing a RustDesk Setup

Should I use RustDesk public infrastructure or self-host?

The standard client can use RustDesk public infrastructure to get started without running a server. Self-hosting is appropriate when you want to operate your own ID and Relay infrastructure and control how it fits into your own network environment.

Should I choose Server OSS or Server Pro?

Choose Server OSS when you mainly need a free, open-source self-hosted ID and Relay backend. Consider Server Pro when you need centralized users, device management, OIDC or LDAP, 2FA, access control, address books, audit or log management, multiple relays or custom clients.

Is RustDesk the same as traditional VNC?

No. RustDesk includes device IDs, rendezvous and signaling, NAT traversal and relay fallback as part of its connection model. Traditional VNC deployments more commonly depend on direct network reachability, port forwarding or a separate VPN or gateway.

Is RustDesk open source?

Yes. RustDesk publishes its open-source client and Server OSS code. Server Pro is the commercial self-hosted option that adds centralized management and enterprise-oriented features on top of the RustDesk Server core.

Configure or Troubleshoot RustDesk

RustDesk FAQ - Connection, Self-Hosting, Install & Security