Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No connection from outside of our LAN #200

Closed
Banane6077 opened this issue Feb 20, 2023 · 5 comments
Closed

No connection from outside of our LAN #200

Banane6077 opened this issue Feb 20, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@Banane6077
Copy link

Hello i want to deploy a Ubuntu Server with rustdesk!

I ran the script which was given by https://rustdesk.com/docs/en/self-host/install/ and it works in our LAN but not from outside.

I made a NAT with our the public IP to the intern IP.

I opened the ports:

tcp 21115-21119; 80; 8000 and 443

udp: 21116-21119

and made a subdomain which is directing to the right IP.

I tested it already with my phone and i am able to connect to the apache webserver but not with the RustDesk Server in my client.

We have a Watchguard Firewall and i am not seeing anything blocked by the Firewall, at least with the IP's i am trying to connect with the RustDesk Client.

Can you help me?

Is there anything on my Ubuntu Server that could block the connection from outside or do i miss to install since i only installed by the given script?

@Banane6077 Banane6077 added the bug Something isn't working label Feb 20, 2023
@Alexybg
Copy link

Alexybg commented May 2, 2023

Same problem. Working only LAN or only Outside. Can't connect both .
image

@rustdesk
Copy link
Owner

https://github.com/rustdesk/rustdesk/wiki/FAQ#deploy-rustdesk-server-in-intranet

@rustdesk rustdesk pinned this issue May 11, 2023
@bartowl
Copy link

bartowl commented May 11, 2023

I found a dns-based solution and this took a bit for me to understand how the relay mechanism works.
In short - when configuring relay on host A - this host connects to server and tells the server that whoever wants to connect to it may go via "relay-exactly-as-given-by-host-A".

If this is a DNS name, and host-B is in the same network as the server (LAN) this host name has to resolve to the local IP of the relay. Then you will not need any hairpin-nat solution. When host-B is on internet, then it has to resolve to the public IP of the relay. And the only place where the setting is relevant is on the side we want connect to (here host-B -> host-A).
It is also the same case in the other way, so the best have a DNS domain, that locally resolves to the local IP and remotely to the public and use this hostname (not IP) on both sides as relay setting. This will work like a treat.

@Alexybg
Copy link

Alexybg commented May 12, 2023

@bartowl Thanks

I use mikrotik with RustDesk Docker on it. In my case with the DNS name of mikrotik public IP work great without hairpin-nat solution. Just with nat rediction to 172.20.0.91 ( veth91 interface ).

Many thanks for simple and working idea.

@rustdesk
Copy link
Owner

rustdesk commented May 14, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants