rustdesk-server
rustdesk-server copied to clipboard
rustdesk
Debian 11
Has anyone able to get rustdesk server working on Debian? I followed instructions on Rustdesk.com self-install docs. I tried docker and without docker. I even tried building the executables from source. Nothing works.
Tried the s6 images, both the latest and latest-amd64 on debian 11. Nope it didn't work. I am only able to get the rustdesk server working on Windows so far
In both cases, the docker images loaded fine with out any errors. Docker status shows both hbbs and hbbr are running. Then I configured the ID/relay server in the client with the debian server IP. The clients just show "Connecting to the RustDesk network" . I tried both the lan IP, public IP, and the dynamic DNS host. I have forwarded TCP/UDP ports 21115-21119
Then I set up RD server on a Windows machine, I am able to connect from the rustdesk clients only using the LAN IP of the Windows box. I have disabled the built-in Windows firewall. I am able to connect to the Windows machine from outside the LAN using RDP and the dynamic DNS hostname.
I have it working in Debian 11, no docker. Can you actually connect to RD server tcp ports (21115-21119) using putty or similar (from the device you attempt to run client on)? If not, maybe it's hairpin nat issue?
I tried telnet from another client and was able to connect to the RD server on the ports 21115-21119
Could you outline the steps that you used to set up your RD server without docker?
Downloaded https://github.com/rustdesk/rustdesk-server/releases/download/1.1.6/rustdesk-server-linux-x64.zip , extracted to /opt/rustdesk-server, crafted systemd services as per https://github.com/rustdesk/rustdesk-server/tree/master/systemd, I use hbbs with -r fqdn. Reload daemon config, enable services and that was it.
You could run both executables simply in terminal (after stopping services), prepending them with RUST_LOG=debug like this: RUST_LOG=debug ./hbbs
Maybe you get some hints what's going on.
on CentOS 7.9 and Ubuntu Server 22.04 i have exactly same problem. i tried all steps like author before but nothing happened. Docker container starts normally without errors, but "connecting to the rust network" and so on
It does not seem to work in a hyper-v VM running debian 11. I then set up RD server on a physical machine running Debian 11. It only works with clients on the LAN. When trying to connect from clients outside the LAN, I keep getting the error "....failed to connect via relay server..." The status both inside and outside clients shows green "ready"
No issue here on Debian 11.
Maybe the issue is on your firewall? try disabling it for minute for testing or open it properly. Been running server(both) on debian 11 from begging, absolutly no issue.
Same problem here, on Debian 11 or Ubuntu 22.04, running as a VM in Hyper-V. With or without docker, everything seems to run fine (no problem to be seen in the logs files, container running), but it doesn't work. Client stuck on "Connecting to server". I tried to create multiple VM, fresh installs, with the exact same parameters... And sometimes, it will work ! No firewall at all on the client/server, same network.
Seems to be truly random, but the common point is the virtualization of the servers with Hyper-V.
Tried everything @raystek did, exact same results.
@LBer7835 You are using OS inside OS, are you sure you are fowarding IP packets correctly, and NATed and OPENed correct ports on correct machines. Sound like you are trying to connect to firewalled machine that is also NATed by your hypervisor. The best way to confirm that is to setup Server on Debian/Ubuntu machine and use rustdesk on same machine, if that works then your problem is with NAT/Firewall.
Hi @bigretromike Our VMs are directely connected to the network, there's no such things as NAT or Firewall on our Hyper-V. We have over 300 VMs on our infrastructure, we never encounters such problems and I can say with confidence that we know what we are doing with our network. Moreover, we traced the packet from the client, to the server with Wireshark and TCPDump, the packets are correctly getting to the server. But, as I said, nothing happened on the application side. Like raystek, I can telnet to every port of the app.
We can't dedicate an entire physical server to this app, and so will probably a lot of company. It would be a shame if this problem is left as it is, because most companies use virtualization and would be in need of such a tool.
@LBer7835 I didn't knew your envirement. Sorry about succesting what could be wrong. It's strange because we use RustDesk_Server on Debian11 on VPS ourself and its flawless experience, but yeah, from mine information that VPS ain't working on Hyper-V, so maybe its something with Microsoft Hypervisor.
I also assume you only typed the correct ip/hostname on client settings inside ID Server and not anywhere else.
@bigretromike Yeah no problem at all ! I also tried using the IP adresss and a FQDN to join the server, but no luck.
The strangest thing is that sometimes, under the exact same circunstances... It will work. If not, I would have assume that it's not working at all - maybe an incompatibility of some kind - but no... And I don't know much about software developpement to investigate the issue myself.
other than that I would assume IP conflict - but You probably checked that.
I'm not familliar with HyperV envirement sadly so I cannot help with that. I would only assume that default ufw firewall on debian would deny the connection, but you check that already. If the envirement is big maybe you are using VLANs there, Hardware IDS/IPS/Firewall ? some funky firewall ruls on main router (with connection status tracking).... other than that I'm out of ideas.
Hope you get sorted it out, but I can only assure that Debian11 as a Host if working ok on VPS.