Selfhosted

40180 readers

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

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Rustdesk not connecting externally (sh.itjust.works)

submitted 2 months ago by ironhydroxide@sh.itjust.works to c/selfhosted@lemmy.world

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.

you are viewing a single comment's thread
view the rest of the comments

[–] ironhydroxide@sh.itjust.works 1 points 2 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.