Conference expires by JVB although the room is not empty

Hi
We use lib-jitsi-meet in our JS website to connect to our self hosted Jitsi server. .

Problem:

Sometimes we get this error in our browser console:

lib-jitsi-meet.min.js:2 WebSocket connection to ‘wss://jitsi…com/colibri-ws/default-id/2317b64e18a70e45/62ac17ea?pwd=69c1…21uhf’ failed: Error during WebSocket handshake: Unexpected response code: 403

And at the same time, JVB log shows that the conference got expired:

JVB 2022-12-15 23:08:26.163 INFO: [23] [confId=2317b64e18a70e45 conf_name=tes0@conference.jitsi…com epId=c22e3324 stats_id=Tyree-mYK] Endpoint.shouldExpire#902: Allowing to expire b
ecause of no activity in over PT1M
JVB 2022-12-15 23:08:26.164 INFO: [23] [confId=2317b64e18a70e45 conf_name=tes0@conference.jitsi…com epId=f472d23b stats_id=Charlene-VLU] Endpoint.shouldExpire#902: Allowing to expir
e because of no activity in over PT1M
JVB 2022-12-15 23:08:26.164 INFO: [685] [confId=2317b64e18a70e45 conf_name=tes0@conference.jitsi…com epId=c22e3324 stats_id=Tyree-mYK] AbstractEndpoint.expire#316: Expiring.
JVB 2022-12-15 23:08:26.164 INFO: [686] [confId=2317b64e18a70e45 conf_name=tes0@conference.jitsi…com epId=f472d23b stats_id=Charlene-VLU] AbstractEndpoint.expire#316: Expiring.
JVB 2022-12-15 23:08:26.164 INFO: [685] [confId=2317b64e18a70e45 conf_name=tes0@conference.jitsi…com epId=c22e3324 stats_id=Tyree-mYK] Endpoint.expire#1073: Spent 0 seconds oversend
ing
JVB 2022-12-15 23:08:26.166 INFO: [686] [confId=2317b64e18a70e45 conf_name=tes0@conference.jitsi…com epId=f472d23b stats_id=Charlene-VLU] Endpoint.expire#1073: Spent 0 seconds overs
ending
JVB 2022-12-15 23:08:26.176 INFO: [686] [confId=2317b64e18a70e45 conf_name=tes0@conference.jitsi…com epId=f472d23b stats_id=Charlene-VLU] Endpoint.expire#1091: Expired.
JVB 2022-12-15 23:08:26.176 INFO: [685] [confId=2317b64e18a70e45 conf_name=tes0@conference.jitsi…com epId=c22e3324 stats_id=Tyree-mYK] Endpoint.expire#1091: Expired.

JVB 2022-12-15 23:08:27.395 WARNING: [35] ColibriWebSocketServlet.createWebSocket#187: Received request for a nonexistent endpoint: c22e3324 (conference 2317b64e18a70e45)

But when I connect to the room from my browser with jitsi-meet (I type the domain name and room name in url bar), the participant is still in the room and the room is not empty.

My questions are:

1- Exactly when the room get expired? Is there any way to avoid this? for example by a certain config?
2- How can I log this error from lib-jitsi-meet in my JS code? I have listener on all events JitsiMeetJS.events.<event_type>.<event_name> and on all errors JitsiMeetJS.errors.<error_type>.<error_name> and still can’t log this specific error from my code.
3- If I could find the error from my code, what is the solution to solve it in my JS code? Reloading the page is not a possibility.

Thanks in advance.

Are you alone in the room when this happens by any chance?

It happens in both cases. I think it is about activity. But maybe it happens more often when I am alone.

When you are alone in the room the JVB connection will be eventually stopped. You’ll still be connected to the room via XMPP so when another participant joins a new media session will be created. Do you observe otherwise?