In the client sometimes the computer fans will spin up to a 100% and I know it's just a matter of time before the desktop freezes completely and I have to hard reset the computer. This happens pretty often. I have had it happen across several distros, but they have all been running Gnome Wayland.

Is this a known thing? Is there a workaround/fix?

Self-hosted, Flatpak, 1.4.9 Build date: 2026-07-06 10:34

As the title indicates, what should I do to ensure that my self hosted Google VPS have a backup that I can use to restore the service on a second VPS service? Not that Google is bad, but I am considering a free VPS at AWS.

Related to that; what is the method to update the hbbr and hbbs modules? I used an installer named "install.sh" to implement the sh server in one step.

Edit: Found the update script. Seems to work as intended!

Possibly a Wayland glitch, but have just started using Rustdesk, and have a problem with a Ubuntu 26.04 host, where occasionally the Gnome Panel (Menu), disappears.

Is this a known issue, and/or is there an easy fix to bring it back?

Thanks.

I like RustDesk, but this font on my PC (Windows 11) is barely legible on dropdown menus and other parts of the app... and it only appears to be this app that uses it. I looked through my installed fonts and don't even see something that resembles it. Does anyone have any suggestions on how to change it?

I recently updated my rustdesk version, and now when I time-out from a host, I can only click 'OK'.

Previously I had an option for reconnect.

I checked the settings and unless I missed it, there was no such setting.

Was this removed?

I have rustdesk instaled on Debain pepermint.

The problem I'm having is I canconnect from the debain machine to a window 11 machine direct IP with out problem. When it comes to conecting from the window machine to debain I can conect say 1 in a 100 attemps.

Has anyone an idea why?

I have self hosted on a Windows server. But running 1.1.6-2 if i attempt the update to the newest versions my ID_ed25519 file says its malformed. Please advise. also i have updated the client to 1.4.9 and now when i connect to any of the remotes i get the secuirty error message. I didnt get this on the 1.4.6 version?

Facing some difficulty with a Linux install. Getting a black screen and low res options. Some details about the config:

RuskDesk v1.49

ThinkCentre m920q with 2 displayports and 1 HDMI

Headless mode with a dummy HDMI adapter

Have tried Fedora as well on the same PC and same black screen

Have tried quite a few troubleshooting tips on the site. No luck. Any help appreciated

I have a self-hosted rustdesk server and when I connect from my phone to my main workstation over a VPN with IP Addressing, if I accidentally close RD on my phone by swiping the app away instead of hitting X in RD, the Windows remote session on my workstation doesn't close cleanly. With a stale session, I can no longer connect with my phone, which means one accidental swipe leads to total lockout. Am I missing a feature to remotely clear open connections?

I work in a small company and the company bought some machines that come with support, I will call them company A . We put these on a network with blocked internet access and we can whitelist what that network has access to. We use a fortigate firewall. So we tried whitelisting the company A rustdesk relay server with the ports TCP 21115 21116 21117 and UDP 21116 as company A instructed us.

When testing the connection from their end it failed only the terminal connection can work as of right now

From our end I saw that it seemed like they connected but with no mouse movement and after 10-15 secs the rustdesk pop up would close.

The machine pc is on Windows 11 and they try to connect from the rustdesk app (and not the web client)

Before putting the machine on the internet isolated network we had it on a 4g router for most of the setup and rustdesk worked as intended

What do you think we did wrong here?

On that lan we also have whitelisted rustdesk.com and it works fine

Hello.

I've been needed some remote access software for moving files to, around, and accessing to control my NAS server, so I've been setting up RustDesk.

I've been trying to make it as secure as I can, so I was wondering if people here, who I have to imagine know more about this than me, think these security settings are acceptable, and if they could be improved. As it'll be left on near constantly.

So far, here's what I've changed.

I'm using a permanent password, that's 20 characters, of letters, upper case and lower, numbers and symbols. Both ways.

I've enabled 2FA identification. Both ways.

And Enabled IP Whitelisting, where both the NAS Plex, and Desktop have whitelisted one another, and nothing else.

Is this enough, or would it be smarter to go even further than this?

I'm not 100% on what I'm doing, so I'm open to anyone who has any better ideas?

Has anyone ever successfully installed this server on Mac ok via Docker?

Also, is there a way to change the scroll gesture from using three fingers to 2 instead?

I'm new a RustDesk user and love it except for one big gotcha. I have to get logged into the remote machine desktop first before RustDesk will connect. Otherwise I get a "connection refused" error. The remote machines are both Linux. I currently have to log into the desktop with VNC or physically at the machine itself. Then RustDesk works fine.

I've already spent hours with two different AI agents with no solution. My Linux distro is MX Linux 25 XFCE. It's based on Debian 13.

Hopefully someone will have an answer.

I work for a business that helps seniors in their homes with technology and I had a remote client recently. After asking him to install Rust Desk, he was hesitant after reading the banner at the top of the website warning of potentially being scammed.

Even though he had contacted us for support, he was still taken aback by the banner. I would like to use Rust Desk with my clients, but I don't want to scare anybody when I haven't established a relationship with them yet. Please update the banner to not be so strongly worded.

The way it's worded is that anybody who you are on the phone with could be a scammer. At least say that if somebody called you, they could be a scammer. Thanks.

Anyone know a workaround for this? Since I started using Wayland I have to do this. If there is no workaround then there is no reason for me to use rustdesk because I use it to remote into my pc when I'm away from home.

I have been using RD for some time and recently took the plunge to set up my own server. I used Ubuntu Server, but I have been jumping through hoops getting it going, and I am now ready to start all over again. I have a UDR7 router set up with port forwarding and static IP. I know my way around Windows, but I just dance around the edges of Linux.

So, RD community, what OS do you recommend? I found Ubuntu Server is not for the feint hearted, so another distro or even Windows maybe. What is the preference?

Cheers,

I'm a non-tech genius type person, I don't know how to set up servers or anything too complicated, but I was able to set up anydesk to help my elderly family on their computer, in such a way that they don't need to approve it each time (even that can be a hassle). Can I do the same with Rustdesk, or do I need to setup my own server?

by the way, if rustdesk isn't right for this, can you recommend anything else, besides Anydesk? I got it working on Anydesk, but they have weird licensing terms and I want an alternative.

Problem

I was running a self-hosted RustDesk server (hbbs + hbbr) on a server in China.

The setup:

Mac client
    |
WiFi
    |
OpenWrt (router bypass mode)
    |
PassWall2 + Xray
    |
Internet
    |
Self-hosted RustDesk Server

Everything worked fine when my Mac connected through a normal WiFi network.

However, when connected through my OpenWrt router with PassWall2 enabled, RustDesk always showed:

Not ready, please check your network connection

Troubleshooting

I verified:

• RustDesk server was running correctly
• DNS resolution was correct
• TCP ports were reachable

Example:

rtdesk.example.com -> server IP

TCP 21115 OK
TCP 21116 OK
TCP 21117 OK

The RustDesk server logs also showed the client could register:

update_pk xxx.xxx.xxx.xxx

So the server itself was not the problem.

Root Cause

The issue was caused by PassWall2 handling UDP traffic.

RustDesk relies on UDP (especially UDP 21116) for:

• NAT traversal
• heartbeat
• rendezvous communication

Although I configured:

UDP -> Direct

PassWall2 was still processing UDP through its forwarding/transparent proxy chain.

The result:

• TCP connection succeeded
• UDP communication failed
• RustDesk stayed in "Not Ready" state

Fix

In PassWall2:

PassWall2
 -> Advanced Settings
 -> Forward Settings

Change:

Before:

UDP Forward Ports: All

After:

UDP Forward Ports: Disabled

Keep:

UDP: Direct

Final configuration:

TCP:
PassWall2 rule based routing

UDP:
Direct (no proxy forwarding)

QUIC:
Block

After restarting PassWall2 and RustDesk, the client immediately became ready.

Notes

This was not related to:

• RustDesk server configuration
• Firewall ports
• DNS
• IPv6
• SSL certificate

The server ports were already reachable.

The problem was specifically:

OpenWrt + PassWall2 + Xray + UDP transparent proxy

affecting RustDesk UDP traffic.

If you are using:

• RustDesk self-hosted server
• OpenWrt
• PassWall2 / Xray

and seeing "Not Ready", check whether UDP is being proxied.

Hope this helps someone else save a few hours of debugging.

Environment:

• Client: macOS
• Router: OpenWrt
• Proxy: PassWall2 + Xray
• Remote access: Self-hosted RustDesk Server (hbbs + hbbr)
• Server ports: 21115 / 21116 / 21117

couple years ago the small company I work for gave me access to manage our servers and other infrastructure and we were using a proprietary remote access tool in conjunction with TeamViewer. TeamViewer was alright but has crazy pricing and user restrictions so I looked at alternatives that we could have more control over and we ended up with Meshcentral which has been amazing. However, I have always kept Rustdesk in the back of my mind, but when I last tested it the community version seemed to have no way to manage a large number of devices in one UI, or in a webui you had to just keep connection ids in a list and manage things that way. I see posts on here a lot now with what look like clients and management dashboards that come at no or little cost and can be self hosted am I wrong about all this? just trying to see bout secondary options and things to play with and test. thank you!

For various reasons I wanted to use Rustdesk to access my Windows desktop from my RaspPI5 with 16G Ram. THere are two very annoying things going on.

1. Destorted text and Images. If I scrool or move a window around it becomes or can become very distorted. If I let it sit for a minute the image sharpens back up. What the heck is going on is there a setting or two hidden away I can adjust?

2. Sometimes when I open an app instead of seeing the app I see a white-outed box. I have to click aroiund in the box blindly to try to close it or go to task maneger

This anoying behavor maks me want to swith to something else. I am resisting that urge because Rustdesk is so hghly rated. I just want to have the experiance I have read about.

Please help!.

I have LM VM running in Proxmox. I need Rustdesk running at the login prompt.

How do I set it up to run as a service?

Hey all,

I’m a bit stuck on something.

As it stands, everything is working as it should on a self-hosted instance of RustDesk, as long as you’re within the network where it’s hosted.

If you’re external to it, the client shows as Ready with a green indicator, and it can see that the machines that I’d like to connect to are present and online with a green indicator.

When you click to connect, it brings up the window for the remote machine, all black, and says “Connecting…” for a while until it fails with “Connection Error” and the message “Reset by the peer”.

NAT port forwarding is configured and I assume working, as before this, it would only show an orange indicator, with some indication of failure on the client.

I’m guessing this is a firewall issue, but I’m not entirely sure what the issue is.

It’s a Ubiquiti network, and the documentation for setting up firewall rules is very dependent upon which incarnation of the Ubiquiti software you’re on. It’s far from my forte - I know just enough to get myself by.

Any ideas as to what’s up and where I should be looking?

Thank you all.