Self-Hosting

RustDesk Remote Desktop: Client Configuration, Security Hardening, and Use Cases (Part 2)

Configure your RustDesk clients, set up key-based authentication, and harden your self-hosted remote desktop server.

Julio
· 1 min read

Enforcing Security and Client Setup in RustDesk

Running a private RustDesk server requires correct client-side configuration and cryptographic key verification to prevent unauthorized access.

Client-Side Connection Configuration

  1. Open the RustDesk client on your remote and local machines.
  2. Click the three dots next to your ID -> Network.
  3. Enter your VPS public IP or domain in the ID Server and Relay Server fields.
  4. Enter the public key (.pub) generated by your hbbs container in the Key field. This key is located in the server's data folder (e.g., /opt/rustdesk/data/id_ed25519.pub).

Restricting Access via Encryption Keys

Ensure that only authorized users who possess your public key can connect: 1. Ensure the hbbs and hbbr containers are started with the -k _ parameter in your docker-compose.yml. 2. This mandates key authentication. Any client attempting a handshake without the matching key will be rejected immediately by the coordinator.

Production Firewall Rules

Only expose required ports to the internet: - TCP: 21115, 21116, 21117, 21118, 21119 - UDP: 21116