You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Client ID, Network is set as shown below:
The client can connect to the server normally and the status is ready.
Opened the Wireshark tool and found a request to access port 21114.
Search by port number, and PID is client.
I found that port 21114 is used to communicate with the web console in the pro version. But the non-professional version should not have this feature, so is it possible to turn off initiating 21114 requests? https://rustdesk.com/docs/zh-cn/self-host/rustdesk-server-pro/console/
How to Reproduce
Build your own server
Normal communication between client and server
Monitor through Wireshark that the client makes a tcp request to the server on port 21114.
Expected Behavior
Do not initiate requests to port 21114.
Operating system(s) on local side and remote side
Windows 11 23H2 -> Linux 5.14.0-427.31.1.el9_4.x86_64
RustDesk Version(s) on local side and remote side
1.3.0 -> 1.3.0
Screenshots
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Bug Description
Deploy the server side using docker compose:
Client ID, Network is set as shown below:
The client can connect to the server normally and the status is ready.
Opened the Wireshark tool and found a request to access port 21114.
Search by port number, and PID is client.
I found that port 21114 is used to communicate with the web console in the pro version. But the non-professional version should not have this feature, so is it possible to turn off initiating 21114 requests?
https://rustdesk.com/docs/zh-cn/self-host/rustdesk-server-pro/console/
How to Reproduce
Expected Behavior
Do not initiate requests to port 21114.
Operating system(s) on local side and remote side
Windows 11 23H2 -> Linux 5.14.0-427.31.1.el9_4.x86_64
RustDesk Version(s) on local side and remote side
1.3.0 -> 1.3.0
Screenshots
Additional Context
No response
The text was updated successfully, but these errors were encountered: