Rustdesk not connecting externally
submitted a month ago by ironhydroxide
So, I'm trying to setup self hosted rustdesk. I have it running in a docker container. I have allowed the ports through the firewall. I have setup the same ports forwarded in my router, to the server running rustdesk. I have set the private key on both clients.
on systems internal network, I can setup the clients to connect with internal IP. And get the "ready" at the bottom. But key mismatch error when trying to actually connect between two internal systems.
If I setup the client with my external up (and I've tried domain name as well) I get a delay then, "not ready please check your connection", as well as the key mismatch.
I feel I'm running into two different problems, but I can't find any hints looking through the container logs (in fact, once the containers are running, I don't really get any logs populating when trying to connect a client)
Any suggestions? I'm at a loss here.
Can you confirm that there are no spaces before or after the key on the client end? Sometimes, copy and pasting can add extra spaces that cause invalid passwords, etc.
I'm not having issues running my self-hosted Rustdesk (docker) externally, but I can't offer much more than that :(
I got past the key mismatch internally. Maybe it was blank spaces.idk.
But still having issues externally. Just doesn't connect for some reason, though I've confirmed all the ports are open. :/
It seems I may have "fixed"(?) One problem, as internal network connections succeed now (same key, same settings, just restarted the containers a few times and let it sit?)
External connections still show the same. :/
Ok. Found some DNS settings on my router, and fixed the internal domain name "problem" but it's still only internal. If I set my public IP(internally) it doesn't connect.
I can connect to an internal computer from external, even though the client says "not ready".
I cannot connect from internal to external computer. Instantly shows "remote desktop is offline"
This leads me to think that somehow I have something wrong in router settings, or I have a security feature blocking something. I just don't know enough about routing to know where to look.