Guide · RustDesk
Stand up a private RustDesk relay server
Keep remote-control traffic on your own network by hosting the RustDesk ID and relay servers in-house.
| Tool | RustDesk |
|---|---|
| Section | Remote access & support |
| Updated | 2026-11-05 |
Why run your own relay
By default, RustDesk clients coordinate through public ID servers. In a company, that coordination — and the relayed session data — really ought to sit on infrastructure you control.
Hosting it comes down to two small services: hbbs (the ID/rendezvous server) and hbbr (the relay). Both are light and sit comfortably on a modest Linux host.
What you need first
A Linux host the clients can reach, with TCP 21115–21119 and UDP 21116 open.
A stable address — IP or DNS name — that every client can resolve.
Point the clients at your server
In each client, open Settings → Network, set the ID and relay servers to the host’s address, and apply the server’s public key.
For a fleet, bake these values into the client config so machines find the relay on their own.
Check it worked
Connect two machines and confirm the session comes up. On the server, tail the hbbs and hbbr logs to make sure your in-house relay — not a public one — is carrying the connection.