Custom websocket port

[MAbbott842]

I have a scenario where port 443 is already used for another service on the network and we are successfully using a different port for API traffic through Nginx to secure it for SSL. I can test the connection using the new port through Nginx and I get a response, however, the web socket settings in the client log only ever use the standard https URL without the custom port causing it to fail when enabled.

If it is not already available, would it be possible to add a request for the custom client builder to allow for a specific port to be selectable for this use?

[rustdesk]

I would recommend using Nginx as a reverse proxy on port 443, with path-based routing for RustDesk WebSocket connections, rather than introducing a separate WSS port.

If the existing service on port 443 can also be placed behind Nginx, both services can share the same HTTPS port:

• https://example.com/ → Existing HTTPS service
• wss://example.com/ws/id → http://127.0.0.1:21118
• wss://example.com/ws/relay → http://127.0.0.1:21119

Nginx handles TLS termination and WebSocket upgrades, so RustDesk clients can continue using the standard WSS port (443) without requiring any modifications to the custom client builder.

RustDesk already documents this approach:
https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/faq/

One caveat: If port 443 is occupied by a service that cannot be moved behind Nginx or shared through a reverse proxy, this workaround would not apply. In that case, supporting a configurable WSS port in the custom client builder would still be a useful feature.

[rustdesk]

YES, we can also add an option of custom client for your case.

[MAbbott842]

Adding this as a client option would be brilliant. Unfortunately the 443 port is being used outside Nginx on a separate Windows server so I cannot use the work around in this case.

[rustdesk]

@21pages rustdesk/rustdesk#16658