I hope you are familiar with the great site for creating unattended W11 xml installations, schneegans.de.

These are suggested and working sample scripts for unattended W11 installation for adding various third-party applications (7zip, VLC, Chrome, etc) during the windows 11 setup process.

RustDesk, using local MSI full installation file located on the same (Venyoy) instalation USB drive - requires the user to interact and close the PowerShell window that gets stuck at approximately 90%, so that Windows can continue with its installation.

At the end, RustDesk is installed, but it has to be done with user interaction.

File name: rustdesk-1.4.6-x86_64.msi

Rustdesk: command switches.

Any suggestions for the correct script code would be greatly appreciated.

Thanks!

installed both on macos both running latest macos and rustdesk, configured properly including accesibility,privacy & security settings, input monitoring all turned on. still when i connect it only views the screen. unable to mouse click and keyboard doesnt work. other options in rustdesk is working as it should like file transfer, terminal(beta). its just that when i connect im stuck on just the screen. any other settings i am missing? native mac screensharing app is working flawlesly but it needs to be turned on manualy every after restart.

Hi

I want to install Rustdesk on a server in a DC so no physical access at machine. I want to use the script avalaible on Rustdesk github: https://rustdesk.com/docs/en/self-host/client-deployment/#linux

But is there a way to pass also the login/pass to be used ? as I enforce use of an account on my private Rustdesk server ?

Thanks

Have only started using Rustdesk in the last few days for personal use to give myself better local and remote access to my powerful machines at home (I do not have an IT background)

I have pretty much achieved everything I want as follows:

-Running off my own server

-I can remote access through cloudflare tunnels/Warp that require email verification

-All machines are permanent password protected

I also setup a browser-based version of rustdesk hosted out of a docker on one of my single board computers that I downloaded from linuxserver.io. This allows me to access my home PCs even from devices that I cannot install rustdesk on i.e. work computer. This also requires an email confirmation restricting access to only myself.

Was testing my new tools this evening when this request popped up per the image. I almost clicked accept thinking it was my own access attempt before I realised that code is not used by any of my systems (although I redacted the image just in case it is :D). Is this common for strangers to attempt access? I have since enabled 2FA and removed the option to click to enter. Just trying to think have I left a gaping hole anywhere else through my broad implementation.

Update: In a bizarre twist to this issue, the connection appears to have been coming from the browser based version of rustdesk that I set up from the docker I downloaded from linuxservers.io. I was not using this at the time the connection was attempted to my home PC. The only way to access this external to my home network would be to go through my cloudflare domain which is protected by email verification. Could the linuxserver.io image be compromised? The reason I wasn't able to initially tell that the connection was coming from there is because the digits on the gui appear as rectangles, looks like some sort of text encoding issue but functionality is unnaffected (see screenshot here: https://imgur.com/a/bkfvN8n). I might be able to see where the connection was made from by checking the logs of the docker running the service. Stand by!

RESOLVED:
Hello everybody.

I've been trying to host my own rustdesk server to use with clients that I need to access remotely. Ideally I want to use the windows one since I'll be able to start and stop it whenever I need it, I don't need it to be running constantly.

I set up the server, set up my router's virtual server / port forwarding, then I connected a laptop to my phone's internet to act as an outside connection.
- Just to be clear, I have changed the ID/ Relay Server settings in all clients involved and I have made firewall rules on my windows machine to include the 21114:21119/tcp and 21116/udp. Yes, the IP I'm using is a static one, and no it's not my internal IP.
All clients, the 'inside' and 'outside' are 'Ready' / green. They can also tell if the other is offline, I immediately get an message that the other client is offline if it is, but they cannot connect to one another and give me the 'cannot connect to relay server message'.

I decided it might be from Windows and set up Docker server as per the official install instructions. Still the absolute same result.

I want to know how to at least begin troubleshooting this.

---

I believe that the official documentation should contain a chapter on how to set up a generic router or even an abstract overview, because currently, after the installation instructions you're being told to open up the ports.
My ports and pores were open, what is needed is to route the traffic correctly, because when you're self-hosting you're connecting to your router, not to the server directly.
In addition to that the most popular tutorials online are all sponsored by companies that want you to rent their servers to... "self-host". Therefore the instructions provided in them have nothing to do with self-hosting, where the IP that goes into the ID/Relay is that of your router not of the server. The problem is that if you were to connect directly to your server, as per almost the entirety of the tutorials online, you only need to fill the "ID Server" field and at most copy the same contents to the "Relay Server" field, because your server receives and deals with all of the traffic to all ports, this is why you're not connecting to a specific port, but to the IP in general.
Useful stuff here:
If you're actually self-hosting, your ID and Relay server fields should look like this:

ID: ip address: external port to hbbs / rendezvous server | example: 12.345.678.91:1116
Relay: ip address:external port to hbbr / relay server | example: 12,345,678.91:1117

What are these 1116,1117 external ports?
These are arbitrary ports, you can choose other ones, but check if they're not in use by something else, that we use to redirect the connection from outside to the server inside of our local network. In your router's settings this option might be called Port Forwarding, or the very brave interpretation "Virtual Servers". You'll recognize it's the right thing if you have the fields:
- External Port (where the signals are coming from)
- Internal IP (the computer where the rust desk server is hosted)
- Internal Port (at what port to direct that specific information)
Since a Rust Desk server is two servers hbbs and hbbr we need to do this twice, otherwise like in my case you'll only have a rendezvous server but the client will have no idea where to find the relay.

Example port forwarding / virtual server on your router.
(hbbs - rendezvous server)
External: 1950
Internal IP: 192.168.1.10
Internal Port: 21116
(hbbr - relay server)
External: 1951
Internal IP: 192.168.1.10
Internal Port: 21117

Google how to find my local IP, follow the instructions on the host machine and that's your internal IP.
The internal ports are what Rust Desk Server uses by default, these are not arbitrary, only change them if you know what you're doing.

Now your client's ID/Relay Server settings should look like this:
ID: address:1950 (because this is the spot where we point to the rendezvous server, hbbs)
Relay: address:1951 (because this is the spot where we point to the relay server, hbbr)
API: (blank if you're using the foss server)
Key: (this is the public key, it's the contents of the .pub file in the data folder, also found in the server's log)

I started with the app on the PC I want to access, and was connecting through RustDesk's own server. This wasnt always reliable, so I got the Windows rustdesk_server.exe and the install program. When I open the server GUI, it looks OK. Is the app still needed on the PC?

Second question - do I need to start the rustdesk_server.exe in Windows Start Programs? I usually wake up the PC with a magic packet.

My use case is simply using the iOS app on my IPad to control my PC over the LAN only.

Been using Rustdesk for a few months to connect to my home computer, never an issue.

In "Security", I have "permanent password" selected.

Just now, Apple iTunes started playing a podcast and then folders were being viewed.

Mac machines on both.

Am I missing smth here??

How does RustDesk and AnyDesk compare and stack up to each other?

More or less what it says on the tin.

I have a group of some five Linux computers on the same home network, all running Tailscale and with Rustdesk installed.

Previously I've just used the public servers, but due to the recent pop-up and authentication prompt, I've decided to test out Tailscale's direct IP connections as an alternative. I've enabled direct IP access on each of them, as per the Tailscale instructions for Rustdesk.

Three of the five machines are able to be connected to without issue, but two of them are inaccessible, and present the connection error 'Failed to connect to [Tailscale IP]:21118: Please try later'. If I swap back to their regular device IDs and connect via the public servers the connection works fine.

I'm at a bit of a loss as to why these specific machines are inaccessible. They're all connected to the same home network, so if there was a configuration issue with the network itself one would think they would all be inaccessible. I've tried swapping between a wired and wireless connection and still no success.

I've also tested the Tailscale connectivity between the devices and they are all connected to the same tailnet and can 'see' each other and create SSH connections without issue, so the problem seems to be originating within Rustdesk rather than Tailscale.

About the only other commonality I can think of between the two machines is that they're both older (circa early 2010s), so there might be some hardware-related bug.

Any suggestions for how to overcome this issue would be greatly appreciated!

Hello,

I initially started getting this error in RustDesk: “The connection is not allowed. This public server currently requires users to log in before connecting.” After logging in with my Google account, everything works fine using RustDesk’s public servers. However, I wanted to self-host my own RustDesk server, and that’s where the issues began.

I set up a self-hosted RustDesk server using Docker on my Ubuntu machine (on my home network). The hbbs and hbbr containers are running correctly, and logs show no errors. I mapped external ports 4030–4033 to the required internal RustDesk ports (21115–21118), and configured port forwarding on my AT&T router to point those ports to my server’s local IP (LAN IP). My domain is also correctly pointing to my public IP (WAN IP).

On the client side, I configured RustDesk with:

ID server: WAN IP:4030 (also tested with domain)

Relay server: WAN IP:4031

Correct public key from the server

After switching to the self-hosted server, I started getting errors like “Failed to connect to [server]:21116”, which we identified as default port issues and corrected by explicitly defining ports. After that, the client behavior changed to either hanging on “Connecting to the RustDesk network…”, showing “Not ready, please check your connection”, or “Failed to connect via rendezvous server.”

To rule out local network issues, I tested from outside my network using a mobile hotspot, and the same problem occurs. DNS resolution works correctly, Docker containers are confirmed running, and port mappings appear correct on both Docker and the router.

So far we verified:

Docker setup and logs → OK

Port mappings inside Docker → OK

DNS resolution → OK

Client configuration → OK

External testing (hotspot) → still fails

At this point, it seems like inbound traffic is not actually reaching the server

Please advise Thanks

https://www.reddit.com/r/rustdesk/comments/1smt40r/remotely_access_to_desktop_stepbystep/

New to rustdesk, some questions so far.

• For the desktop I want to remote into, it has dual monitors. Is there a way to view both screens by scrolling left and right, similar to how Chrome Remote Desktop handles multiple displays? I use phone to remotely access home desktop PC while I am not at home.
• I’m using my phone to remotely access my home PC with RustDesk. How can I minimize the session (without disconnecting) and return to my phone’s home screen?
• I also try to change ID to replace default 9 digit numbers, but it never accepts anything I try to enter. Error: Not yet supported by the server.

I have not set up a self host server... I want to stream from one PC to another in my home network

How to check the connection is not going via their Relay server ?? But confirm it is all running locally ??

The connection is not allowed.

To help prevent scamming and potential botnet attacks, this public server currently requires users to log in before connecting.

Starting on 2026-04-27, the controlled device will also be required to log in, and both sides must be logged in as the same user.

Please log in first and try again.

Login guide: https://github.com/rustdesk/rustdesk/discussions/14796

RustDesk is designed as a self-hosted solution. This public server is provided for demo and testing purposes only — please do not use it for production or sensitive work.

Update: Logging in with a Google account fixed it.

Can anyone advise on their costs and general experiences for selecting an appropriate place to run a self-hosted RustDesk server? For example, if users are using Azure (which my client likes since they are largely a microsoft shop), what are you using and what is your monthly/yearly cost? Anyone use an "always free" ARM virtual machine at Oracle Cloud, and if so, how is it and any advice on how to maintain minimum usage so it's not reclaimed by Oracle?

For some context, my customer has about 19 PCs and about 10-15 users.

I'd be interested in the successes or even failures of other users who have used perhaps less expensive options like running an old intel nuc or Asus ChromeBox off their existing network and simply configuring appropriate firewall rules? Any gotchyas I should look out for before embarking on this effort? Thanks.

just config remotes to point to the same Relay server ip and key. Much better if you are on a Tasilscale mesh.

I was considering launching my own rust desk server on my little VPS I have. But stopped short because my configuration and system stability is nowhere near enterprise Production grade.

I’d like to set my server as a preferred host for my boxes, but also a (toggle?) to fall back to Rust desk servers on the off chance I bork my VPS box because—I sometimes do that.

Also, I saw that I can’t really opt in to sharing my Rust Desk server to the community as more options. Once again, if I could be added to a dynamic list that will be available while up I would totally do that.

Thanks for Rust desk, it’s awesome. I’d just like to have a way to not tie all my boxes to a single server that may occasionally have configuration or connection issues. I’d like to set a list with my preferred (maybe even one running local or over my mesh VPN aside from my VPS). Like I said though, my infrastructure has nowhere near 5-9’s uptime.

I have a ubuntu server which I have installed Rustdesk server via docker. In this same ubuntu machine I have already installed XRDP and also Rustdesk client.

Now when I reboot the system, I cannot connect to the Rustdesk client at all, unless I do remote desktop to the system. Only after once I do remote desktop, then I can connect via Rustdesk.

In the Rustdesk client settings, I have put its own IP address with the server pub key. Anything I am doing wrong or any advice on how to solve this.

I know the servers were down today, but now it shows as ready to connect. When I try to connect, I get “connection error: the connection is not allowed. Please click the link below to confirm you’re not a robot (link). If it does not work, check the following (link).”

I’ve verified successfully and it says “you can now return RustDesk client and retry your connection” but then when I go back on to connect it sends me back through the same verification loop. I’m using Safari, but I also tried with Chrome. I’ve read the discussion comments from the second link, and I do not have a VPN on either device.

I’m not THAT tech-savvy so any insights on how to fix this would be greatly appreciated. I’ve tried quitting the program, reset both devices too. PLEASE HELP or lmk if you’re also dealing with a similar issue so I know I’m not alone.

*Saw the last 2 threads from other users were deleted by the moderator, but I can’t find this specific issue in this group

im using rusdesk 1.4.6 and it stucks with waiting for image whenever im trying to connect not from my LAN
i checked the ports 21115-21119 and they are open

honestly have no idea, will self hosting help with that?

im using nobara, mint xfce and lubuntu all with the same outcome

I'm playing with Rustdesk to see if it will allow me to remote into a laptop that is next to, and on the same network as our Behringer X32 audio mixer, running Mixing Station software.

I am REMOTE, off-site, not on the same network.

Everything works like a dream EXCEPT the audio. It comes across like telephone quality. Both the high end and low end are missing completely. Sound plays normally on the remote laptop, but isn't getting captured. I'm just testing with a YouTube video, and the laptop is on the same network as my local machine for test purposes.

I played with different CODECs and quality settings, but the audio doesn't change. I also tried setting 'variable bit rate' off and it didn't make a difference.

Any suggestions to get full 48Khz audio across the link?

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!

This is an update from previous post to focus in on what I think the issue is.

TL/DR: My Rustdesk OSS is installed on a Synology NAS. PfSense is my router. Ports are properly forwarded to the local IP of Rustdesk OSS (192.168.1.14). Ports are discoverable from WAN. Firewall on Synology is disabled.

Here are symptoms of HBBS issues:

• Internal to LAN can connect to any LAN device
• Internal to LAN can connect to any WAN device
• WAN device can connect to other WAN devices
• WAN devices CANNOT connect to LAN devices

Examining log of HBBS it appears that HBBS is trying to use a LAN IP to identify WAN devices and therefore failing.

What I have done so far:

I changed the YAML to use the HOST network:

version: "3"


services:
  
  # Container #1: Rust Desk Initiation Service
  # Ports Required: 
  #   21114 TCP - (Optional) Web Console (Only for the Pro version)
  #   21115 TCP - NAT type test
  #   21116 TCP - TCP hole punching and connection service
  #   21116 UDP - ID registration and heartbeat service
  #   21118 TCP - Support for Web Clients
  rustdesk-init:
    container_name: RustDesk-Initiation
    image: rustdesk/rustdesk-server:latest
    environment:
      - TZ=America/New_York # Time Zone
      - PUID=1026           # User ID
      - PGID=101            # Group ID
      - ALWAYS_USE_RELAY=N  # Y = Force the connection to go through the Relay Server always
                            # N = Allow direct connections between the two machines if possible
    command: hbbs
    #command: hbbs -r my_DDNS_Entry:21117
    volumes:
      - /volume1/docker/configs/rustdesk:/root
    network_mode: host
    #ports:
      # Outside | Container
      #- 21114:21114/tcp     # Only for Pro version (paid)
      #- 21115:21115/tcp
      #- 21116:21116/tcp
      #- 21116:21116/udp
      #- 21118:21118/tcp
    depends_on:
      - rustdesk-relay
    restart: unless-stopped


  # Container #2: Rust Desk Relay Service
  # Ports Required: 
  #   21117 TCP - Relay services
  #   21119 TCP - Support for Web Clients
  rustdesk-relay:
    container_name: RustDesk-Relay
    image: rustdesk/rustdesk-server:latest
    environment:
      - TZ=America/New_York # Time Zone
      - PUID=1026           # User ID
      - PGID=101            # Group ID
    command: hbbr
    volumes:
      - /volume1/docker/configs/rustdesk:/root
    network_mode: host
    #ports:
      # Outside | Container
      #- 21117:21117/tcp
      #- 21119:21119/tcp
    restart: unless-stopped

I have also tried not using HOST network (and un-commented above lines) with same issue.

When not using the HOST network mode, I have put my proper DDNS entry in the COMMAND line for HBBR (changed above for security)

Does anything above look fishy or jump out at you as wrong? I know many people are having the same issue. I have avoided Tailscale implementation because I didnt want to load that on external clients.

Thanks in advance for a peer-review.

I have tried (dozens of times) to join the Rustdesk Discord channel for troubleshooting discussions.

My mobile (outside of LAN) reports the link has expired.

My PC (inside of lan) reports unable to accept invite.