RustDesk Server Pro 1.7.1 on Windows: clients show Offline (orange) but connect after enabling "Always Use Relay" #13312

nizo67 · 2025-10-27T11:06:47Z

nizo67
Oct 27, 2025

We are running RustDesk Server Pro 1.7.1 with Pro licence on Windows Server 2022 behind pfSense.
Public host: rustserver.publich.ch (VIP 111.222.333.444).
Nginx on Windows terminates HTTPS for the console and web client on port 4443.

Symptoms:

All devices show Offline (orange) in the RustDesk desktop client.

Web Console shows the same devices Online (green).

Before: connection by ID failed with "Verbindung über Rendezvous-Server ist fehlgeschlagen".

After we enabled Always Use Relay and set Relay = rustserver.publich.ch:21117, we can connect remotely. Sessions work now.

BUT devices still appear Offline (orange) in the desktop client UI, which is confusing for operators.

Network layout:

pfSense forwards only from our trusted management networks (not the whole internet).

For those trusted networks, we forward:

443/TCP → hbbs TCP 21116

443/UDP → hbbs UDP 21116

21115/TCP → hbbs 21115 (NAT test)

21116/TCP+UDP → hbbs 21116

21117/TCP → hbbr 21117 (relay)

4443/TCP → Nginx 4443 (API console + /ws/id and /ws/relay to 21118/21119)

Windows Firewall is disabled for troubleshooting.

Only our Trusted_Networks can reach these forwards.

Question:
What exact heartbeat / presence check does the RustDesk desktop client use to decide green vs orange?

Is it strictly UDP heartbeat to hbbs on the configured ID server host:port?

Does forcing "Always Use Relay" change how presence is reported?

We are able to connect now via relay, but the orange status never turns green. We'd like to know what additional public-facing info hbbs/hbbr must advertise so that clients show Online (green) in the desktop app.

Also: we attempted to email [email protected] twice, but Zoho rejected it with 554 5.7.7 Email policy violation detected, so we’re opening this here instead.

Attachments we can include:

nginx.conf

Screenshot of client list (orange)

Screenshot of server Relay Settings with "Always Use Relay" enabled

Please advise how to get correct online presence in the RustDesk desktop client in this relay-only / restricted-source setup.

Thanks in advance for your help.

rustdesk · 2025-10-27T11:11:21Z

rustdesk
Oct 27, 2025
Maintainer

You need to open tcp 21115 port for this.

1 reply

rustdesk Oct 27, 2025
Maintainer

Please test "telnet server-ip 21115" from the machine which you see orange icon.

nizo67 · 2025-10-27T13:30:10Z

nizo67
Oct 27, 2025
Author

Telnet on port 21115 is ok.
Port 21115 is open and NAT also works fine.

PS C:\Users\Administrator> netstat -ano | findstr 2111
TCP 0.0.0.0:21114 0.0.0.0:0 LISTENING 6880
TCP 0.0.0.0:21115 0.0.0.0:0 LISTENING 6880
TCP 0.0.0.0:21115 0.0.0.0:0 LISTENING 2816
TCP 0.0.0.0:21116 0.0.0.0:0 LISTENING 6880
TCP 0.0.0.0:21117 0.0.0.0:0 LISTENING 7924
TCP 0.0.0.0:21118 0.0.0.0:0 LISTENING 6880
TCP 0.0.0.0:21119 0.0.0.0:0 LISTENING 7924
TCP 1.2.3.4:21116 111.222.333.50:6367 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:9779 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:10816 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:12029 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:13437 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:15009 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:23532 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:30579 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:32443 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:34578 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:39798 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:44013 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:49477 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:50881 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:54047 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:54804 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:54891 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:58512 TIME_WAIT 0
TCP 1.2.3.4:21116 111.222.333.250:64225 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:54753 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:54754 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:54755 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:54756 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:54757 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:54758 TIME_WAIT 0

PS C:\Users\Administrator> Test-NetConnection rustserver.publich.ch -Port 21115
ComputerName : rustserver.publich.ch
RemoteAddress : 111.222.333.80
RemotePort : 21115
InterfaceAlias : Ethernet0 2
SourceAddress : 12.34.56.78
TcpTestSucceeded : True

PS C:\Users\Administrator>

0 replies

rustdesk · 2025-10-27T13:38:04Z

rustdesk
Oct 27, 2025
Maintainer

Could you paste the log of %AppData%\RustDesk\log\RustDesk_rCURRENT.log on the machine of clients showing offline (orange)

2 replies

nizo67 Oct 27, 2025
Author

I have to make a clean install and i will update here again.

nizo67 Oct 28, 2025
Author

Please check these 3 logs.

I appreciate your help in advance.

nhdiagpc_RustDesk_rCURRENT.log
vprtgrp001_diag-rustdesk_rCURRENT.log
vsftp002_Diag-Rustdesk_rCURRENT.log

nizo67 · 2025-10-28T09:57:48Z

nizo67
Oct 28, 2025
Author

Please check these 3 logs.

I appreciate your help in advance.

nhdiagpc_RustDesk_rCURRENT.log
vprtgrp001_diag-rustdesk_rCURRENT.log
vsftp002_Diag-Rustdesk_rCURRENT.log

2 replies

rustdesk Oct 28, 2025
Maintainer

You log looks quite strange, it sends online query, but no reponse message received. You seems mapping 21115 port to other port (you mentioned yersterday, but deleted then).

rustdesk Oct 28, 2025
Maintainer

Also your "telnet server-ip 21115" returns some demangled code, it seems not 21115 port, because 21115 port returns nothing with telnet.

> telnet 5.161.65.208 21115
Trying 5.161.65.208...
Connected to static.208.65.161.5.clients.your-server.de.
Escape character is '^]'.
^]
telnet> Connection closed.

~/Downloads
> telnet 5.161.65.208 21116
Trying 5.161.65.208...
Connected to static.208.65.161.5.clients.your-server.de.
Escape character is '^]'.
??b
`??yq?xP�;?9?G???(?2L?`j^?<?Q?h?QiXP????Әa
                                          ?̌???M???Q^%?e?R????Z[i?7?4
                                                                    ?*?qpr{?s%Z^C^]
telnet> Connection closed.

~/Downloads
>

nizo67 · 2025-10-28T12:34:12Z

nizo67
Oct 28, 2025
Author

Please check attached files.
nhdiagpc_RustDesk_rCURRENT.log
syslogsrv_Diag-Rustdesk_rCURRENT.log

Connection to Server is not allowed form any, just for trusted Networks.

I was using ID Server : server:443 , so i made a NAT port 442 to 21115, and NAT 443 to 21116

Relay Server : 21117

NOW:
I am using just a config for all clients are the same:
ID Server : 21116
Relay Server : 21117
NAT Rule TCP/UDP 21115 to internal Server:21115
Also NAT Rule TCP/UDP 21116 to internal Server:21116
Also NAT Rule TCP 21114 to to internal Server:21114
Also NAT Rule TCP 21117 to to internal Server:21117
Also NAT Rule TCP 21118 to to internal Server:21118
Also NAT Rule TCP 21119 to to internal Server:21119
Also NAT Rule TCP 4443 to to internal Server:4443

from my pc (nhdiagpc)
Telnet to the Server Public IP

telnet 89.28.155.80 21115 is OK

telnet 89.28.155.80 21116 is OK

On the Rustdesk Server

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS C:\Users\Administrator>
PS C:\Users\Administrator>
PS C:\Users\Administrator>
PS C:\Users\Administrator> netstat -ano | findstr 2111
TCP 0.0.0.0:21114 0.0.0.0:0 LISTENING 3324
TCP 0.0.0.0:21115 0.0.0.0:0 LISTENING 3324
TCP 0.0.0.0:21115 0.0.0.0:0 LISTENING 5428
TCP 0.0.0.0:21116 0.0.0.0:0 LISTENING 3324
TCP 0.0.0.0:21117 0.0.0.0:0 LISTENING 1160
TCP 0.0.0.0:21118 0.0.0.0:0 LISTENING 3324
TCP 0.0.0.0:21119 0.0.0.0:0 LISTENING 1160
TCP 10.230.2.80:21115 10.230.3.252:7141 TIME_WAIT 0
TCP 10.230.2.80:21115 10.230.3.252:34759 TIME_WAIT 0
TCP 10.230.2.80:21116 10.230.3.252:9221 TIME_WAIT 0
TCP 10.230.2.80:21116 10.230.3.252:9444 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:58829 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:58830 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:58831 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:58832 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:58833 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:58834 TIME_WAIT 0
TCP 127.0.0.1:21114 127.0.0.1:58835 TIME_WAIT 0
.
.
.
.
.
TCP 127.0.0.1:21115 127.0.0.1:59857 TIME_WAIT 0
TCP 127.0.0.1:21115 127.0.0.1:59858 TIME_WAIT 0
TCP [::]:21114 [::]:0 LISTENING 3324
TCP [::]:21115 [::]:0 LISTENING 3324
TCP [::]:21116 [::]:0 LISTENING 3324
TCP [::]:21117 [::]:0 LISTENING 1160
TCP [::]:21118 [::]:0 LISTENING 3324
TCP [::]:21119 [::]:0 LISTENING 1160
UDP 0.0.0.0:21116 : 3324
UDP [::]:21116 : 3324
PS C:\Users\Administrator>

From my PC (nhdiagpc)
Test-NetConnection rustserver.publich.ch -Port 21115

PS C:\Users\Nazar.Hassan> Test-NetConnection 89.28.155.80 -Port 21115

ComputerName : 89.28.155.80
RemoteAddress : 89.28.155.80
RemotePort : 21115
InterfaceAlias : Ethernet
SourceAddress : 10.0.33.65
TcpTestSucceeded : True

PS C:\Users\Nazar.Hassan>

PS C:\Users\Nazar.Hassan> Test-NetConnection 89.28.155.80 -Port 21116

ComputerName : 89.28.155.80
RemoteAddress : 89.28.155.80
RemotePort : 21116
InterfaceAlias : Ethernet
SourceAddress : 10.0.33.65
TcpTestSucceeded : True

PS C:\Users\Nazar.Hassan>

1 reply

rustdesk Oct 28, 2025
Maintainer

Could you give me the output "telnet server-ip 21115"?

nizo67 · 2025-10-28T13:07:46Z

nizo67
Oct 28, 2025
Author

I get a connected, blank session (no banner).

Telnet server-ip 21116

15 replies

nizo67 Oct 30, 2025
Author

yes, for others client outside our trusted network

rustdesk Oct 30, 2025
Maintainer

I do not suggest you use our public server, because it is not stable and no guarentee.

rustdesk Oct 30, 2025
Maintainer

BTW, when you connect to clientid@public, it has nothing to do with your Pro server, no matter it is Linux or Windows server, because it do not use your Pro.

nizo67 Oct 30, 2025
Author

Ok. But it may occur that we want to connect to a public client with our client, our client has our configuration. How we can bypass this also on Linux as Windows?

rustdesk Oct 30, 2025
Maintainer

Linux as Windows

When you connect to clientid@public, it has nothing to do with your server running on Linux or Windows. Because it does not talk to your server. As for why it worked when you used Windows server, but not work today with Linux server, it is another story, I do not have clue yet, because our public server is for demo purpose only, not meant for production use, there is no guarentee. So I can not tell why you can connect to clientid@public sometimes, but can not at another time.

RustDesk Server Pro 1.7.1 on Windows: clients show Offline (orange) but connect after enabling "Always Use Relay" #13312

Uh oh!

nizo67 Oct 27, 2025

Replies: 6 comments · 21 replies

Uh oh!

rustdesk Oct 27, 2025 Maintainer

Uh oh!

rustdesk Oct 27, 2025 Maintainer

Uh oh!

Uh oh!

nizo67 Oct 27, 2025 Author

Uh oh!

Uh oh!

rustdesk Oct 27, 2025 Maintainer

Uh oh!

Uh oh!

nizo67 Oct 27, 2025 Author

Uh oh!

nizo67 Oct 28, 2025 Author

Uh oh!

nizo67 Oct 28, 2025 Author

Uh oh!

rustdesk Oct 28, 2025 Maintainer

Uh oh!

Uh oh!

rustdesk Oct 28, 2025 Maintainer

Uh oh!

nizo67 Oct 28, 2025 Author

Uh oh!

rustdesk Oct 28, 2025 Maintainer

Uh oh!

nizo67 Oct 28, 2025 Author

Uh oh!

nizo67 Oct 30, 2025 Author

Uh oh!

Uh oh!

rustdesk Oct 30, 2025 Maintainer

Uh oh!

rustdesk Oct 30, 2025 Maintainer

Uh oh!

nizo67 Oct 30, 2025 Author

Uh oh!

Uh oh!

rustdesk Oct 30, 2025 Maintainer

nizo67
Oct 27, 2025

Replies: 6 comments 21 replies

rustdesk
Oct 27, 2025
Maintainer

rustdesk Oct 27, 2025
Maintainer

nizo67
Oct 27, 2025
Author

rustdesk
Oct 27, 2025
Maintainer

nizo67 Oct 27, 2025
Author

nizo67 Oct 28, 2025
Author

nizo67
Oct 28, 2025
Author

rustdesk Oct 28, 2025
Maintainer

rustdesk Oct 28, 2025
Maintainer

nizo67
Oct 28, 2025
Author

rustdesk Oct 28, 2025
Maintainer

nizo67
Oct 28, 2025
Author

nizo67 Oct 30, 2025
Author

rustdesk Oct 30, 2025
Maintainer

rustdesk Oct 30, 2025
Maintainer

nizo67 Oct 30, 2025
Author

rustdesk Oct 30, 2025
Maintainer