WebSocket connection to xmpp-websocket failed
See original GitHub issueI have a standard Jitsi Meet Docker stable-6433 setup. I have problem with WebSocket connection. I do not have error in Jist web container.
I’d greatly appreciate any pointers to help fix the issue.
Jitsi Web Logs:
"GET /xmpp-websocket?room=test HTTP/1.1" 403 284 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36"
Chrome screenshot
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Jitsi Meet in Docker Container: Websocket error
WebSocket connection to 'wss://jitsi.example.com/xmpp-websocket?room=strangeshopsincorporateagain' failed: Error during WebSocket handshake: ...
Read more >Websocket - Error detected; session - Openfire
I changed the BOSH protocol to websocket and the error below is frequently occurring ... XmppWebSocket@3983bad6],behavior=SERVER,connection= ...
Read more >ejabberd connection failed with webclient(websocket.js)
This was just problem with web-socket client, it was using old web-socket protocol version, that was available before xmpp over web-socket ...
Read more >RFC 7395: An Extensible Messaging and Presence Protocol ...
RFC 7395 XMPP over WebSocket October 2014 If a client receives a handshake ... Sec-WebSocket-Protocol: xmpp [WebSocket connection established] C: <open ...
Read more >Jitsi Meet in Docker Container: Websocket error - Server Fault
WebSocket connection to 'wss://jitsi.example.com/xmpp-websocket?room=strangeshopsincorporateagain' failed: Error during WebSocket handshake: ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Right. This setup is designed to work by default, as is, in a single host compose setup. Anything that deviates from that may require tweaking. I don’t think there is a way to have a default configuration that works for every possible environment.
Hi @saghul ! It was the nginx container that were responding with 403.
I’ve solved this but I’m not sure why. The cluster was on GCP when this happened, so there could be something with the network there, or it might just be some variable I’ve missed before. I’ve moved to AWS and things worked without much change. Also, the colibri websocket was a challenge: I was having issues with low quality streams and it turns out the
colibri-ws
is essential for the negotiation of those stream qualities, so my mistake was the JVB_WS_SERVER_ID, that needed to be a hostname / ip internally accessible of the JVB.Thanks for your pointers!