RustDesk Clients
How to point a RustDesk client at the self-hosted RustDesk Pro server, and how to operate that
server. The server runs on the DigitalOcean edge node edge-node.fzymgc.house, outside the k3s
cluster. Its Docker Compose project at /opt/docker-compose/rustdesk/ on that host is not in this
repository. Only its public DNS records are.
Quick reference
Section titled “Quick reference”| Property | Value |
|---|---|
| Server hostname | rd.fzymgc.net |
| Server software | rustdesk/rustdesk-server-pro, Docker Compose on edge-node |
| Admin web console | https://rd.fzymgc.net (Caddy in front of host port 21114) |
| Server public key | the content of id_ed25519.pub on the server. See Read the public key. |
| Public DNS | cloudflare_dns_record.fzymgc_net_rd_a and fzymgc_net_rd_aaaa in tf/cloudflare/dns-fzymgc_net.tf, both unproxied |
The DNS records must stay unproxied. The Cloudflare proxy cannot carry RustDesk’s TCP and UDP ports.
Client configuration
Section titled “Client configuration”Every client, desktop or mobile, needs four fields. A client with a wrong key fails its handshake with no error in the UI.
| Field | Value | Notes |
|---|---|---|
| ID Server | rd.fzymgc.net |
The hbbs rendezvous server. The client tries 21116 and falls back through 21115, 21118 and 21119. Do not add a port. |
| Relay Server | rd.fzymgc.net, or blank |
hbbs advertises the relay address. Leave it blank unless you want to override what the server sends. |
| API Server | https://rd.fzymgc.net |
Needed only for Pro features (address book, user accounts, audit log). The https:// prefix is required. |
| Key | the server’s id_ed25519.pub |
A mismatch is a silent connection failure. |
No per-client license key, API token or password is needed for basic connectivity. The server holds the license, and clients are free.
Where to enter it
Section titled “Where to enter it”| Client | Path |
|---|---|
| macOS, Windows or Linux desktop | Gear icon, Settings, Network. Fill ID Server and Key. Apply. |
| iOS or Android | Settings (top right), ID/Relay Server. Fill the same fields. |
Web client at https://rd.fzymgc.net |
Nothing to enter. The web client uses the server’s own configuration. |
Paste a configuration string
Section titled “Paste a configuration string”Desktop clients accept a base64 configuration string through Import server config from clipboard under Settings, Network. Generate one with the current key:
KEY=$(ssh root@edge-node 'cat /opt/docker-compose/rustdesk/data/id_ed25519.pub')python3 -c 'import base64, json, syscfg = {"host": "rd.fzymgc.net", "key": sys.argv[1], "api": "https://rd.fzymgc.net", "relay": ""}print(base64.b64encode(json.dumps(cfg).encode()).decode())' "$KEY" | pbcopyThe admin console can also produce a QR code string under Settings, Strategies.
Pro features
Section titled “Pro features”After the basic configuration, a user signs in inside the client under Settings, Account, Sign In, with a username and password created in the admin console under Users. The address book then syncs into the client, the server records every session in the audit log, and group permissions apply.
Server operations
Section titled “Server operations”First admin setup
Section titled “First admin setup”- Browse to
https://rd.fzymgc.netand sign in with the default credentials. Change them at once. - Under Settings, License, make sure that the Pro license is registered. It binds to the server’s machine identity.
- Under Users, create a real admin account, then disable or delete the default
admin.
Read the public key
Section titled “Read the public key”ssh root@edge-node 'cat /opt/docker-compose/rustdesk/data/id_ed25519.pub'Do not delete /opt/docker-compose/rustdesk/data/. If id_ed25519 is regenerated, every
client’s stored key is invalid and every connection fails silently. A key rotation is a
coordinated change: regenerate, then update the Key field on every client.
Check a client connection
Section titled “Check a client connection”Tail the hbbs container while the client connects:
ssh root@edge-node 'docker logs -f rustdesk-hbbs 2>&1 | grep -E "Punch hole|Listen|tcp"'A successful connection logs Punch hole <id> <peer-ip>:<port> request from <client-ip>:<port>.
No such line after the client tries means that the client never reached hbbs: DNS, a firewall, or
a wrong key.
Restart, logs and license
Section titled “Restart, logs and license”ssh root@edge-node 'cd /opt/docker-compose/rustdesk && docker compose restart'ssh root@edge-node 'docker logs --tail 200 rustdesk-hbbs' # rendezvous and signalssh root@edge-node 'docker logs --tail 50 rustdesk-hbbr' # relayhbbs and hbbr read id_ed25519 from /opt/docker-compose/rustdesk/data/ at start, so a restart
keeps the key. The hbbs log records a license check with License OK. If a check fails, hbbs
refuses new connections.
| Port | Service | Protocol | Use |
|---|---|---|---|
| 443 | Caddy | TCP, TLS | Admin and API console, proxied to 21114 |
| 21114 | hbbs | TCP | Web console and API, host-only behind Caddy |
| 21115 | hbbs | TCP | NAT type test |
| 21116 | hbbs | TCP and UDP | Rendezvous and signal, the primary client port |
| 21117 | hbbr | TCP | Relay, when a direct connection fails |
| 21118 | hbbs | TCP (WebSocket) | Web client signal fallback |
| 21119 | hbbr | TCP (WebSocket) | Web client relay fallback |
Troubleshooting
Section titled “Troubleshooting”The client stays on “Trying to connect”
Section titled “The client stays on “Trying to connect””In order of likelihood:
- Wrong key. Compare the Key field with the server’s
id_ed25519.pub. The client shows no error for a key mismatch and retries forever. - A firewall blocks 21116 or 21117. The signal and relay ports are not HTTP, and some networks
block non-HTTP outbound traffic. Test from the client’s network:
nc -zv rd.fzymgc.net 21116. - DNS points at the wrong host.
dig rd.fzymgc.net A AAAAmust return the edge node’s addresses from the LAN as well as from the internet. There is no in-cluster RustDesk. - The license lapsed. Read the hbbs log for
License check failed.
The address book is empty after sign-in
Section titled “The address book is empty after sign-in”The API Server field is missing or has the wrong scheme. It must be https://rd.fzymgc.net.
“Permission denied” on remote control
Section titled ““Permission denied” on remote control”A Pro permission group denies the action. Read Users, Permissions in the admin console for the signed-in user.