BBB iframe Chrome 401

[Jonathan]

Hi,

we randomly encountered a new Error that in Chromium Browsers only the BBB cant be loaded because it is in an infinite enter loop. Sometimes it manages to connect but often it doesn't. Weirdly enough the join URL if used in another tab without the iFrame works fine.

Our setup is like this:

BBB 2.4

Scalelite 1.3

A website running under the same domain as the BBB Server.

We get a valid Join url from our server which is embedded in the iFrame:

in the from of https://scalelite.ourDomain.com/bigbluebutton/api/join?

Then Scalelite redirects us to a BBB Server (https://bbb1.ourDomain.com/bigbluebutton/api/join?)

Then the BBB Server gives us a valid enter response (...api/enter?sessionToken=xyz)

Then it gets weird, we get a loop of

1. https://.../html5client/sockjs/598/6bwbfsff/xhr -> 200

2. https://...html5client/sockjs/598/6bwbfsff/xhr_send -> 200

Then at some point we get a 404 from this request (https://...html5client/sockjs/598/6bwbfsff/xhr_send)

And it repeats itself.

In the console we get a

Uncaught (in promise)

1. {error: 401, description: 'Authentication failed due to missing credentials'}
   1. description: "Authentication failed due to missing credentials"
   2. error: 401

and

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'map')
    at I (d13d9965f0d30ea95c841b5e157517ca9def8c8d.js?meteor_js_resource=true:375:809557)

Any ideas whats happening?

[Anton Georgiev]

Hi!

> Our setup is like this:
> BBB 2.4

Could you please confirm which 2.4 version you are using? There was a report of something similar on 2.4.1-2.4.2 but it seemed fixed on 2.4.4 (the latest stable release).

Could we rule out someone kicking / ejecting users from that meeting, i.e. can you reproduce if alone in a meeting?

-Anton

[Jonathan]

Thx for the reply!

It is the latest version BigBlueButton Server 2.4.4 (2961).

Yes we can reproduce it in a meeting of just one person.

Do you have the links to the similar issues of previous version?

[Pedro Beschorner Marin]

> Weirdly enough the join URL if used in another tab without the iFrame works fine.

It's because you have to set BBB's JSESSIONID cookie SameSite policy to fit your iframe environment. By default BBB uses "Lax" and for iframes you should use "None".

[Jonathan]

Yeah, we thought the same but we checked and Chrome is not blocking the cookie from being sent.

Yesterday we could reproduce the behavior pretty clearly and it seems to be an issue with another WebSocket connection that is failing.

So to our setup, we have a web app that is trying to connect via websocket to our main server. That failed and was constantly retrying. That other websocket connection that has nothing to do with our bbb sever was somehow interfering with a successful connection to the bbb server. That's also why it worked in another tab because there of course was not that constantly failing other websocket connections.

I know it sounds super strange but we got the same error twice now and that's the only connection between those two. I will file a bug report in the bbb repo. But maybe you can try to reproduce the behaviour. If you need more info regarding our setup please let me know

[Pedro Beschorner Marin]

So you are already using SameSite=None and still getting 401s inside the iframe?