this post was submitted on 22 Aug 2024
17 points (94.7% liked)

Selfhosted

40677 readers
327 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
17
Rustdesk not connecting externally (self.selfhosted)
submitted 4 months ago by ironhydroxide to c/[email protected]
4 comments fedilink hide all child comments
 

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.

top 4 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 4 months ago (1 children)

But key mismatch error when trying to actually connect between two internal systems.

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 :(

[–] ironhydroxide 1 points 4 months ago

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. :/

[–] ironhydroxide 1 points 4 months ago

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. :/

[–] ironhydroxide 1 points 4 months ago

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.