-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection Establish Error #4
Comments
this problem is not because of your changes. i had this problem too with beta.meet.jit.si , i changed server to meet.jit.si it was okey for few days but now i get same error from it too. i had tried to run my own using docker-jitsi-meet but i get 403 from it too!!!! |
@andrewtbennett Sorry, I moved on to another project a while back so my jitsi knowledge is not up to date. 403 is security so I think you are on the right track about passing a token. |
Did you find a solution to this? |
I found that replacing the server with alpha.jitsi.net works. |
Hi there,
I am working on a video conference project and I am using your project as a jumping off point for foundational parts of the Jitsi connection. It has been working perfectly so far but recently I have run into a couple issues when trying to connect. At first, it appeared to be a similar issue to the other issue in this repository, but looking further into the issue, I don't believe it to be the same after all. The errors that I have gotten are as follows:
WebSocket connection to 'wss://beta.meet.jit.si/xmpp-websocket?room=franktest' failed: Error during WebSocket handshake: Unexpected response code: 403
and
connect @ strophe.umd.js:5463
<Object../modules/xmpp/strophe.util.js.webpack_exports.default.strophe_js__WEBPACK_IMPORTED_MODULE_1_.Strophe.log>: Strophe: Websocket error [object Event]
I have tried reverting back to your version of the application and I am getting the same error as well, so I'm not sure if it's something out of our control.
Any suggestions on how to get a successful connection with the websocket? I am not super familiar with a lot of this backend stuff, and through some digging it looks like it may have to do with passing a token in the JitsiConnection function, but I am unsure at this point.
The text was updated successfully, but these errors were encountered: