Replies: 0 comments 2 replies
-
|
Nevermind, finally found the problem, leaving empty the "Relay server" configuration on the client make the thing work! Before I had it set to the same domain as the ID server, I suspect maybe the server was doing a DNS lookup of whatever you put there, obtaining the local address and returning it, but I don't really know. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Oh nope, thought it was solved, but was my laptop changing WiFi to the local network without me noticing, instead of the WAN shared on my phone. Still doesn't work :( |
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.
-
I have deployed rustdesk server 1.1.14 on my home network, configured NAT on my router and pointed several clients to it. When on the local network everything works great. But when I try connecting from the WAN, connection with
hbbssucceeds but connection tohbbrfails because client tries connecting using a local IP address. I have verified this by capturing the process with Wireshark:At first I thought it might be related to this, but followed the guide, set the DNS record on Pi-Hole and problem persists. Other things I tried is using
hbbs -r <wan_ip_address>(and verifying on the logs the setting gets applied), settingALWAYS_USE_RELAY=Y, but no matter what I do, the client always tries connecting tohbbrusing a local IP address. In Wireshark I can also see how the last data sent byhbbson port 21116 contains the local IP address, so I don't know why but it seems whatever I do,hbbsalways sends the local IP address to the client.What am I doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions