mistake websocket

[aka0kuro]

Hello, I have the following problem when accessing the server from the internet.

user connection fail error="websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header"

[sergystepanov]

Hey,

And what did you change since that time it worked? The message says that there is something wrong with your browser or a web app which you are using for openeing the site.

[aka0kuro]

No, I couldn't solve it, I'll tell you more. The problem is when I enter the website from localhost it works fine, the problem is when I enter from Apache and the reverse proxy fails and gives me that error, it does not load the games in the list.

[sergystepanov]

It is not just an HTTP app, it uses Websockets and WebRTC, so you need to forward websocket traffic also. (I assume, it cuts UPGRADE headers from the request/response). These questions aren't app issues, tbh.

[sergystepanov]

Basically, in the coordinator, you have one HTTP(S) address for HTTP/WebSocket connections from external sources (e.g., a browser; by default, this is :8000). You need to configure this correctly for both HTTP and WebSocket (WS) protocols in your reverse proxy. Additionally, there is the /wso endpoint in the coordinator, which is used for WebSocket connections from workers. This endpoint must be accessible from the worker machines.

Then there’s the WebRTC component, which establishes a direct peer-to-peer (P2P) connection between your browser (where you play) and the workers. For performance reasons, you don’t want this connection to be proxied (e.g., via TURN or anything).

Here’s how it works: when you open the site, the coordinator establishes a WebSocket connection to your browser. Through this WebSocket, it sends all the necessary information for making a direct WebRTC connection with a selected worker, along with its list of games. If the WebRTC connection fails, the list of games won’t be displayed on the page, as well as when you fail to establish the initial WebSocket connection (you have to check it in the Chrome DevTools on the Network tab).