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

Rust desk not working unless "Host network" box is checked. #533

Open
orrinwitt opened this issue Sep 26, 2024 · 3 comments
Open

Rust desk not working unless "Host network" box is checked. #533

orrinwitt opened this issue Sep 26, 2024 · 3 comments
Assignees

Comments

@orrinwitt
Copy link

Title says it all. Server is up and running, and set up correctly in both clients. All necessary ports are forwarded in router. Without "Host network" box checked, it will not work. Once I checked it, all of a sudden it works.

My suggestion is to either change the default to have this box checked, or to include whatever else would need fixed or configured to make it work otherwise.

Am I missing something obvious? Do I need to be running something additional (like Nginx or Traefik) that manages these ports to allow traffic to the docker containers?

@stavros-k stavros-k self-assigned this Sep 30, 2024
@stavros-k
Copy link
Contributor

stavros-k commented Sep 30, 2024

Hello, mine works (shows ready) without the need of host network.

Of course here I used local network only. but host network does not make a difference as long as the port forward is done correctly.

See here https://rustdesk.com/docs/en/self-host/rustdesk-server-oss/install/
what ports needs to be opened (note that a few are both tcp and udp)

Below are screens from my laptop and the 10.20.30.6 is my server running rust-desk.

Client Config:
image

Status:
image

Server config:
image

Please share logs and screenshots if you still having issues.

@orrinwitt
Copy link
Author

So, is it better to use the local ip of the server for the local workstation, and the server.example.com domain name for the remote workstation? I think that may be part of my problem, as i do get the "ready" with the green light on both machines, but the connection was failing.

@stavros-k
Copy link
Contributor

It shouldn't matter, as long as the server.example.com resolves to the local IP when the machine is inside your network.

If a local workstation resolves server.example.com to your public IP, it makes a weird scenario where your traffic goes out your WAN and back to your LAN (kinda, depends on the router and the Hairpin support etc, but still not ideal).

When it fails does it give an error message?
Do you see any logs on the rust-desk container while you are trying to connect?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants