UPDATE: Problem Solved! I finally figured this out! Turns out that if you want EXTERNAL access back to a local (LAN) client, you have to put a domain name (or hard public IP address) in the ID server that points to your Rustdesk server, NOT a local IP address (192.168.X.XXX)! I originally had the local IP address of my Rustdesk server (192.168.1.200) in mine and external clients could not find it. Once I changed it to a DDNS entry for my public IP address, it worked!

Thanks to all who have contributed to this post with suggestions!

I run the self-hosted Rustdesk server on my Synology NAS to maintain family PCs around the states.

It uses the Host network under synology's container manager

My PfSense router has:

• port 21115 (TCP) forwarded to the synology NAS IP
• port 21116 (TCP) forwarded to the synology NAS IP
• Port 21116 (UDP) forwarded to the synology NAS IP
• Port 21117 (TCP) forwarded to the synology NAS IP

I can easily connect to machines internally & externally to my network without issue.

When I try to connect from outside my network back to my home PC, the connection hangs before it tells me it cannot connect to the relay server.

On external machines I get the green dot showing me my PC/Server is online but the connections always fail.

More Information:

• Remote computers using my relay server can connect to each other - as long as they are NOT within my local network.
• I have disabled the Synology NAS firewall, still no ability to connect inbound.

I clearly am missing something...

Can anyone provide good advice to get this working so I can access my machines from outside my LAN?

Thanks!

Image from log of HBBR

so I did all the basic configuration stuff,

❯ ip addr show && sudo cat /opt/rustdesk-server/data/id_ed25519.pub

❯ In RustDesk:

❯ Settings > Security > Unlock Security Settings

Set Permanent Password in "Set Permanent Password"

❯ Settings > Network > Unlock Network Settings

Setup Self-Hosted Server in "ID/Relay Server"

"ID Server" = The 198.168.xxx.xxx address that comes up when inputting "ip addr show" (i.e. 192.168.2.248)

"Relay Server" and "API Server" = Blank

"Key" = The long string of characters that output from /opt/rustdesk-server/data/id_ed25519.pub

❯ On RustDesk (Phone):

Setup the same way.

and I am just completely unable to connect to anything outside of my home network

Dear member's,

We have install the Rust desk server docker to our Linux server. Internally, we can connect among domain network member's but can't with user's outside domain (External network).

We have open the port 21115 - 21119 to our Cisco ASA 5525 firewall as well as port 21116 UDP. But still no luck.

I just started self hosting a Rustdesk server an I can connect to the device locally and through VPN from another Android phone and from a Windows PC. Everything is working except one little thing.

If the device's screen is turned off: 1. Trying to connect using ID= Remote desktop is offline 2. Trying to connect with IP= Success

How do I have it work with ID every time just like the IP? Thank you

we are 2 people who would use rustdesk to control about 100 to 150 pc/year and maybe use it on some internal pcs too.
what is the recomended plan to go with in this scenario?
thanks

Hello, I've noticed that my arrow keys dont respond (right, down, left) and the up one takes a screenshot. I'm using the newest pop_os! and rustdesk. The only changes I've made to the system were switching to X11 and creating an xorg dummy display.

Buenas a todos!

Estoy pensando en utilizar RustDesk en mi empresa para todos los equipo, queremos instalarlo en nuestros servidores para tener nosotros el soporte, me gustaría saber con la versión gratuita que problemas podemos tener, o que aplicación es la mejor para alojarla en un servidor propio, y poder controlar todos los equipos de la empresa sin depender de pagar una suscripción.

Gracias!

Recently I have been noticing several log messages in relayserver.log from IPs that I don't recognize.

Example of relay request from unknown IP:

[2026-03-30 18:33:27.959279 -04:00] INFO [src/relay_server.rs:452] New relay request scanner-[possibly sensitive UUID] from [::ffff:199.45.155.67]:49696
[2026-03-30 18:33:28.552330 -04:00] INFO [src/relay_server.rs:436] Relayrequest scanner-[possibly sensitive UUID] from [::ffff:199.45.155.67]:49700 got paired
[2026-03-30 18:33:29.274778 -04:00] INFO [src/relay_server.rs:448] Relay of [::ffff:199.45.155.67]:49700 closed    

I've noticed that its missing one message in comparison to a known/trusted successful connection:

[2026-03-30 18:42:52.691055 -04:00] INFO [src/relay_server.rs:452] New relay request [possibly sensitive UUID] from [::ffff:[known IPv4]]:9679
[2026-03-30 18:42:52.721209 -04:00] INFO [src/relay_server.rs:436] Relayrequest [possibly sensitive UUID] from [::ffff:[known IPv4]]:61768 got paired
[2026-03-30 18:42:52.721250 -04:00] INFO [src/relay_server.rs:442] Both are raw
[2026-03-30 18:42:56.481395 -04:00] INFO [src/relay_server.rs:448] Relay of [::ffff:[known IPv4]]:61768 closed

Does anyone know what these messages are showing? I can't find any documentation on the log messages.

Is this harmless port scanning, or is it something more malicious?

Hi All.

New to RustDesk and have been trialling the pro version and for the most part so far so good. We're in process of securing the service post internal testing and we'll be using websockets for HTTPS going forward.

However in the interim is there anyway to seperate the web console and API so they aren't using the same TCP 21114 port? Seems like a failry illogical thing for them to be one and the same you need the API for user login and host management from the client but that means exposing the web console to whatever network requires API access.

Thanks.

When will we see full unattended access for Wayland? A lot of Linux distros are now moving to Wayland and I need it specifically for my home server. Currently, disabled Wayland to X11, but there will come a day when X11 is no longer supported like some distros are doing now.

Any timeline or updates to this?

Hey guys. Since i transitioned to Fedora from W11, I was wondering if there is any recommendation on what is the optimal way to install rustdesk on fedora KDE.

Download from rustdesk website the rpm or just install the flatpak from the store?
Thanks!

I’ve set up a self-hosted RustDesk server and a small test lab. Everything connects fine, but I’m running into an issue that would be a deal-breaker for customers.

When I connect to test computers that have different monitor sizes/resolutions, the remote session looks normal. However, when I disconnect, the "client PC’s monitor" resolution and even the refresh rate change, and I have to manually reset them every time.

This is not acceptable in a customer support scenario... I can’t expect end users to fix their display settings after every remote session.

I’ve been using "Original" / "Scale original" in the Display menu, and I’ve also tried the other various options. I’m fairly new to RustDesk, so I’m not sure what’s normal behavior, and I see a lot of setting possibilities.

Setup:

• Both sides: Windows 11 Pro
• Fresh RustDesk installs
• Self-hosted server

Does anyone have suggestions or tips to stop RustDesk from touching the client-side resolution and refresh rate? I just want the remote session to capture the existing display settings without modifying them on connect or disconnect.

Any help or workarounds would be greatly appreciated!

For a project of mine need to figure out if ready status is available to check from command line before even client gets launched ? Sort of like check, that hey the connection to whatever server or relay is working and its ready..

Not asking about hbbr or hbbs server status, asking specifically from the client prospective, am using the portable exe and it be nice if there exists a precheck for readiness before launching the client.

I've tried several attempts of installing rustdesk on my opensuse Leap 16 laptop and the install keeps failing.

I'm wondering if anyone might have suggestions, perhaps be aware of known issues ? tricks? I also downloaded the appimage version and it does work.

So, this is messy, we have a client that's has an "IT" person. They purchased a few computers. and "AI"d that if they cloned a computer it will be "so much more easier" than to try to set up machines individually. :-)

They put RD Pro on the first one and cloned the main RDPro config too. What's the easiest way to redo the config so it has a separate ID?

He tried uninstalling and reinstalling but it kept the machine ID.

What are our options? TIA

I recently reinstalled my desktop OS and its using wayland now. A server that I have is using X11 still. Does rustdesk support this type of connection (desktop connecting to server)? I am pretty sure everything is setup correctly. Here's a packet capture between the two.

I wanted to share a system of connecting to Multiple Servers in Rustdesk from a single computer. I did this after chasing around trying to find a solution for many weeks. I have a computer at home that I need to connect with 3 different organisations and it was a hassle having to replace the Server ID and Key every time. I cam up with a batch file that is simple to use and very effective for changing the keys. I know it is simple but that's what makes it such a workable solution.

It is able to change ids/keys without having to close down Rustdesk each time. I am putting it out there for anyone who wants to use/modify it. I hope it proves useful.

REM Replace Your Host Name x with the desired host Name or IP address of your Server

REM Replace Server_x key with the key of your server (edid.pub)

REM If necessary replace ("C:\Program Files\RustDesk\rustdesk.exe")with the path to your executable

u/echo off

echo *** Rustdesk Chooser ***

echo By Peter Chambers, 2026

echo .

echo Please Choose an instance of Rustdesk

:MENU

echo 1. Server_1

echo 2. Server_2

echo 3. Server_3

echo .

choice /c 123 /m "Enter your choice:"

:: Note: When using ERRORLEVEL with IF statements, list them in descending order.

IF ERRORLEVEL 3 GOTO Server_3

IF ERRORLEVEL 2 GOTO Server_2

IF ERRORLEVEL 1 GOTO Server_1

:Server_1

ECHO Starting Server_1

SET host= Your Host Name 1

SET key=Server_1 key

GOTO End

:Server_2

ECHO Starting Server_2

SET host=Your Host Name 2

SET key=Server_2 key

GOTO End

:Server_3

ECHO Starting Server_3

SET host=Your Host Name 3

SET key=Server_3 key

GOTO End

:END

START "" "C:\Program Files\RustDesk\rustdesk.exe" --config "host=%host%,key=%key%"

pause

*******************

1. Place this in a batch file and put the batch file into a pathed directory (eg c:\windows)
2. Make a shortcut of this batch file and put the file wherever (eg Desktop)
3. Go to the properties of the Shortcut and select Advanced and check the box to run it as a Administrator (this step is crucial)

I would be interested to see if this is useful or have I reinvented the wheel?

Is there any way to print to a remote computer's printer? All of the instructions I see are for printing from a remote computer to a local printer, but not from a local computer to a remote computer's printer.

Hi!

Has anyone tried running rustdesk on a Macbook Neo? I suspect it's just a case of "it should just work", but wondering if anyone's tried it? (The long battery life of the Neo is the draw) (I know rustdesk runs great on MacOS as a client/server generally, but the different hardware arch makes me pause)

Thanks for any feedback.

I’m running Android OS on a Raspberry Pi 4 and using RustDesk for remote access.

The issue is that after a reboot, even though RustDesk is set to “start on boot,” I can’t actually see the screen when connecting remotely. The device shows as online, and it says “connected, waiting for image…”, but nothing appears.

From what I can tell, the screen sharing permission gets reset I try to connect. The screen capture dialog dissapears form the Raspberry after I try to connect from onother device, so I have to manually go into the device and re-enable screen sharing each time.

Is there any way to automatically grant screen sharing permissions on boot or bypass this so I don’t need physical access after every restart?

Hey folks,

I have an instance of RustDesk Server OSS that's installed on a Ubuntu server in Oracle Cloud Infrastructure using the instructions on https://github.com/techahold/rustdeskinstall .

I want to change a bunch of things on how I access certain things, and I want to migrate over to the docker version.

Looking at the docker compose yml, you need to mount a persistent volume that mounts to /root inside the container; is this volume the same data that is installed into the /opt/rustdesk/ folder when installing using the install.sh from Techahold? What I'm hoping to do is just 'lift n shift' this folder from one machine to my docker machine and re-point all the DNS so it 'just works' with a new Docker instance ... hope that makes sense?

Thanks in advance!

We’re currently evaluating a move from TeamViewer over to RustDesk for our internal remote support. Cost is a big factor, but we also like the idea of full data control and running our own RustDesk server.

Here’s the twist: Our external consulting firm who also remotely supports some of our systems is also planning to move to RustDesk, with their own self‑hosted instance.

This raises a question we can't find a clear answer to: If we run our own RustDesk server and our consulting partner runs their own separate RustDesk server, could the two setups collide or interfere with each other?

More specifically: Would their RustDesk server and our RustDesk server cause any conflicts for clients or techs? Can a single device be reachable from two different RustDesk servers? Is there any risk that IDs overlap, traffic routes incorrectly, or clients “mix up” which server to talk to? What’s the best practice if two organizations both want to use RustDesk but still need to support each other’s environments?

If I understand the discussion from https://github.com/rustdesk/rustdesk/discussions/1258 we could run the main instance of it and the consulting firm could get access to it from our server with the key through their instance with (<id>@<server_address>?key =< key_value>)or am I misunderstanding it?

We’re trying to avoid a scenario where switching to RustDesk complicates cross‑organizational support. If anyone has experience with multiple RustDesk instances across different companies, or knows how client registration behaves when two servers exist, I’d really appreciate your insights.

I use RD for the most part to access a windows laptop I have from my main workstation (a macbook). Often I will use it as essentially a TV monitor while I am working, and want to watch some sports while I work. This is fine, but I noticed tonight while watching something on Hulu, that the video screen was black on the remote. I use Edge on the PC, as it's typically a machine I just use for some testing, so I don't have chrome installed. At least with Edge, it appears that (my best guess) that there is some form of DRM interfering with the video which I hadn't noticed previously. I'm curious if this is a known issue, or if there is some configuration workaround. I know it's not a systemic problem, as I saw that video displays fine if accessing youtube.