Client incorrectly uses internal IP for relay server despite public domain configuration (v1.4.3) #3779

New issue

Closed

opened 2026-02-21 01:36:54 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-21 01:36:54 -05:00

Owner

Originally created by @City-Zero on GitHub (Nov 4, 2025).

Bug Description

When connecting through a self-hosted RustDesk server, the client ignores the configured public domain for the relay server and attempts to use an internal IP address instead, causing connection failures.

Environment:
Client Version: 1.4.3 (60)
Server Setup:
Hosted on home server (internal IP: 192.168.2.20)
Port forwarding configured for public access
Dynamic DNS (DDNS) domain: mydomain(replace with actual domain)
Configuration:
ID Server: mydomain:21116
Relay Server: mydomain:21117

How to Reproduce

Set up a self-hosted RustDesk server on a machine with internal IP (e.g., 192.168.2.20)
Configure port forwarding: external ports 21116-21117 → internal IP ports 21116-21117
Set up DDNS pointing to your public IP (e.g., mydomain)
On the client, configure custom servers:
ID Server: mydomain:21116
Relay Server: mydomain:21117
Start a connection attempt to another device
Monitor network traffic (using tools like Wireshark or tcpdump)
Observe that the client incorrectly tries to connect to 192.168.2.20:21117instead of the configured mydomain:21117

Expected Behavior

Client should consistently use the configured public domain (mydomain:21117) for relay connections.

Operating system(s) on local (controlling) side and remote (controlled) side

osx -> windows10

RustDesk Version(s) on local (controlling) side and remote (controlled) side

1.4.3->1.4.3

Screenshots

Additional Context

No response

Originally created by @City-Zero on GitHub (Nov 4, 2025). ### Bug Description When connecting through a self-hosted RustDesk server, the client ignores the configured public domain for the relay server and attempts to use an internal IP address instead, causing connection failures. Environment: Client Version: 1.4.3 (60) Server Setup: Hosted on home server (internal IP: 192.168.2.20) Port forwarding configured for public access Dynamic DNS (DDNS) domain: mydomain(replace with actual domain) Configuration: ID Server: mydomain:21116 Relay Server: mydomain:21117 ### How to Reproduce Set up a self-hosted RustDesk server on a machine with internal IP (e.g., 192.168.2.20) Configure port forwarding: external ports 21116-21117 → internal IP ports 21116-21117 Set up DDNS pointing to your public IP (e.g., mydomain) On the client, configure custom servers: ID Server: mydomain:21116 Relay Server: mydomain:21117 Start a connection attempt to another device Monitor network traffic (using tools like Wireshark or tcpdump) Observe that the client incorrectly tries to connect to 192.168.2.20:21117instead of the configured mydomain:21117 ### Expected Behavior Client should consistently use the configured public domain (mydomain:21117) for relay connections. ### Operating system(s) on local (controlling) side and remote (controlled) side osx -> windows10 ### RustDesk Version(s) on local (controlling) side and remote (controlled) side 1.4.3->1.4.3 ### Screenshots <img width="448" height="109" alt="Image" src="https://github.com/user-attachments/assets/256d7b16-40ab-47c2-a0d8-d1ba3d897fb8" /> <img width="392" height="366" alt="Image" src="https://github.com/user-attachments/assets/282384e7-6d5e-4e2e-a5ea-f093afdf090c" /> ### Additional Context _No response_