Jitsi Meet not connecting on the meet.jit.si infra

Hi, I use on my application (a game) the lib jitsi for a custom interface using the meet.jit.si infrastructure, some hours ago we started to receive, when connecting with to the socket, this message:

failed: Error during WebSocket handshake: Unexpected response code: 403

Was we banned from the usage of the meet.jit.si infrastructure? If so, sorry for this.

1 Like

Sorry for that, but not using the iframeAPI contradicts the terms and conditions on meet.jit.si

Hey @sekiro , sorry to hear about your disruption. You may want to try https://jaas.8x8.vc though. We can probably help you achieve the same thing there.

With this service will we able to use the same code that I use today with the lib-jitsi-meet (of course paying)?

Other than this, would be possible to use the Jitsi infrastructure with a logo of Jitsi on it (our app already have a link to Jitsi), this logo would be even more visible than when using the Iframe integration.

Yes I, I think we can make this work.

Drop me a note on emcho @ jitsi . org

Ok, I will.

I know this is your service, and you are free to put any rule and I truly respect this, but I have a genuine question: what is the specific violation of using a custom UI on the service terms? Is it because of not presenting the Jitsi branding?

That is stated in the terms of service, it is the branding and the adds at the end of the call.

@damencho Will you also restrict the BOSH api at some point? Currently it’s still possible to use it with lib-jitsi-meet.