RustDesk Self-Hosted: Client Fails to Connect Despite Open Ports #643
Unanswered
electriquo
asked this question in
Q&A
Replies: 1 comment
-
|
same here |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary of the Issue
Request
Any guidance on why the client cannot complete the connection (despite successful TCP connectivity) would be appreciated.
Environment
Docker Compose Setup
I created the following
compose.yaml, inspired by:Firewall Check
Verified that the macOS firewall is disabled
Running the Services
Started the Server and Relay containers
Key Observations from Logs
Port Connectivity Test
On another terminal, verify all required ports appear reachable locally:
Client Configuration
Configured the client manually using ID Server and Key
Client UI
Initial state: "Connecting to the RustDesk network..."
Final state: "Not ready. Please check your connection"
Server Logs During Client Attempts
Each client attempt results in a short-lived TCP connection:
This repeats periodically, suggesting:
Additional Notes
Instead of using
localhostincompose.yamland Client Configuration, I tried using the machine's local IP address.$ ipconfig getifaddr en0 #"$(route get 0.0.0.0/32 | grep interface: | awk '{print $2}')"Beta Was this translation helpful? Give feedback.
All reactions