Most of your comment incorrectly assumes that you need a separate server for WebSocket but you don't. That HTTP request to upgrade the connection to WebSocket c

Most of your comment incorrectly assumes that you need a separate server for WebSocket but you don't. That HTTP request to upgrade the connection to WebSocket can go to your webserver which likely already has support built in to handle it. > The starting sequence of a web socket is an HTTP request header to an upgrade the connection. Correctly configured DPI firewalls block these upgrade headers so for all you know the connection has been made but the renderer fails silently. Slack and many other applications use WebSockets. IIRC there were proxy issues with WebSocket when it was new but that was 15 years ago. Also you will absolutely be able to detect the connection not succeeding.