Participants connects in separate rooms

Hi, this is an weird behaviour. This instance was working just fine. A couple of days ago when a participant tryied to connect jitsis crashed. So, updated all to latest packages available and now everyone has a room just for his own.

=== jicofo.log

Jicofo 2022-03-16 14:39:15.926 INFORMACIÓN: [418] ConferenceIqHandler.handleConferenceIq#63: Focus request for room: variascosillas@conference.meetings.DOMAIN.COM
Jicofo 2022-03-16 14:39:15.927 INFORMACIÓN: [418] [room=variascosillas@conference.meetings.DOMAIN.COM] JitsiMeetConferenceImpl.<init>#280: Created new conference.
Jicofo 2022-03-16 14:39:15.927 INFORMACIÓN: [418] [room=variascosillas@conference.meetings.DOMAIN.COM] JitsiMeetConferenceImpl.joinTheRoom#465: Joining variascosillas@conference.meetings.DOMAIN.COM
Jicofo 2022-03-16 14:39:16.096 INFORMACIÓN: [414] [room=variascosillas@conference.meetings.DOMAIN.COM meeting_id=7ed97d97-9b91-40b9-b91f-f1987c91ba27] JitsiMeetConferenceImpl.onMemberJoined#615: Member joined:aa8c76f3
Jicofo 2022-03-16 14:39:16.096 INFORMACIÓN: [414] AutoOwnerRoleManager.electNewOwner#106: Electing new owner: ChatMember[variascosillas@conference.meetings.DOMAIN.COM/aa8c76f3, jid: null]@274741898
Jicofo 2022-03-16 14:39:44.130 INFORMACIÓN: [417] [room=variascosillas@conference.meetings.DOMAIN.COM meeting_id=7ed97d97-9b91-40b9-b91f-f1987c91ba27] JitsiMeetConferenceImpl.onMemberLeft#801: Member left:aa8c76f3
Jicofo 2022-03-16 14:39:44.130 ADVERTENCIA: [417] [room=variascosillas@conference.meetings.DOMAIN.COM meeting_id=7ed97d97-9b91-40b9-b91f-f1987c91ba27] JitsiMeetConferenceImpl.onMemberLeft#816: Participant not found for aa8c76f3. Terminated already or never started?
Jicofo 2022-03-16 14:39:44.131 INFORMACIÓN: [417] [room=variascosillas@conference.meetings.DOMAIN.COM meeting_id=7ed97d97-9b91-40b9-b91f-f1987c91ba27] JitsiMeetConferenceImpl.stop#442: Stopped.

=== jvb.log

JVB 2022-03-16 14:56:54.575 INFORMACIÓN: [37] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-03-16 14:56:54.603 INFORMACIÓN: [38] HealthChecker.run#171: Performed a successful health check in PT0.000000167S. Sticky failure: false
JVB 2022-03-16 14:57:04.603 INFORMACIÓN: [38] HealthChecker.run#171: Performed a successful health check in PT0.000000167S. Sticky failure: false
JVB 2022-03-16 14:57:14.603 INFORMACIÓN: [38] HealthChecker.run#171: Performed a successful health check in PT0.000000222S. Sticky failure: false
JVB 2022-03-16 14:57:24.604 INFORMACIÓN: [38] HealthChecker.run#171: Performed a successful health check in PT0.000000423S. Sticky failure: false
JVB 2022-03-16 14:57:34.603 INFORMACIÓN: [38] HealthChecker.run#171: Performed a successful health check in PT0.000000216S. Sticky failure: false
JVB 2022-03-16 14:57:44.603 INFORMACIÓN: [38] HealthChecker.run#171: Performed a successful health check in PT0.000000571S. Sticky failure: false
JVB 2022-03-16 14:57:54.575 INFORMACIÓN: [37] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-03-16 14:57:54.603 INFORMACIÓN: [38] HealthChecker.run#171: Performed a successful health check in PT0.000000169S. Sticky failure: false
JVB 2022-03-16 14:58:04.603 INFORMACIÓN: [38] HealthChecker.run#171: Performed a successful health check in PT0.000000227S. Sticky failure: false
JVB 2022-03-16 14:58:14.604 INFORMACIÓN: [38] HealthChecker.run#171: Performed a successful health check in PT0.000000471S. Sticky failure: false
JVB 2022-03-16 14:58:24.604 INFORMACIÓN: [38] HealthChecker.run#171: Performed a successful health check in PT0.000000347S. Sticky failure: false

Really don’t figure out where to go at this point.

it’s a common problem for instances that have not been updated for a long time to not work anymore when updated, because the updates script can do only so much and are not tested for weird upgrade cases (usually at best they are tested against the previous stable…).

Give more information about the old and new packages versions (including Prosody - you did not update Prosody to 0.12 right ? you did not do an OS upgrade too ?).
Try to add a browser console log and a Prosody log as well.

Didn’t pass a long time at all, just a month ago did a fresh install based on Debian Bullseye

Current versions are

prosody               0.11.9-2+deb11u2 amd64
jitsi-meet            2.0.7001-1
jitsi-meet-web        1.0.5913-1
jitsi-videobridge2    2.1-634-gff8609ad-1

=== prosody.log. Just an extract, but the same pattern repeats itself

Mar 17 08:54:00 c2s55bf36d25950    info    Client connected
Mar 17 08:54:00 c2s55bf36d25950    info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Mar 17 08:54:00 c2s55bf36d25950    info    Client disconnected: connection closed
Mar 17 08:54:05 c2s55bf36ddb070    info    Client connected
Mar 17 08:54:05 c2s55bf36ddb070    info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Mar 17 08:54:05 c2s55bf36ddb070    info    Client disconnected: connection closed
Mar 17 08:54:10 c2s55bf36f1d170    info    Client connected
Mar 17 08:54:10 c2s55bf36f1d170    info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Mar 17 08:54:10 c2s55bf36f1d170    info    Client disconnected: connection closed
Mar 17 08:54:15 c2s55bf36deb5d0    info    Client connected
Mar 17 08:54:15 c2s55bf36deb5d0    info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Mar 17 08:54:15 c2s55bf36deb5d0    info    Client disconnected: connection closed
Mar 17 08:54:20 c2s55bf36cf7ee0    info    Client connected
Mar 17 08:54:20 c2s55bf36cf7ee0    info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Mar 17 08:54:20 c2s55bf36cf7ee0    info    Client disconnected: connection closed
Mar 17 08:54:25 c2s55bf36966e40    info    Client connected
Mar 17 08:54:25 c2s55bf36966e40    info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Mar 17 08:54:25 c2s55bf36966e40    info    Client disconnected: connection closed
Mar 17 08:54:30 c2s55bf36ed5440    info    Client connected
Mar 17 08:54:30 c2s55bf36ed5440    info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Mar 17 08:54:30 c2s55bf36ed5440    info    Client disconnected: connection closed
Mar 17 08:54:35 c2s55bf36f6bd10    info    Client connected
Mar 17 08:54:35 c2s55bf36f6bd10    info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Mar 17 08:54:35 c2s55bf36f6bd10    info    Client disconnected: connection closed
Mar 17 08:54:40 c2s55bf36e9eae0    info    Client connected
Mar 17 08:54:40 c2s55bf36e9eae0    info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Mar 17 08:54:40 c2s55bf36e9eae0    info    Client disconnected: connection closed
Mar 17 08:54:45 c2s55bf36e8b550    info    Client connected
Mar 17 08:54:45 c2s55bf36e8b550    info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Mar 17 08:54:45 c2s55bf36e8b550    info    Client disconnected: connection closed
Mar 17 08:54:50 c2s55bf36eb4700    info    Client connected
Mar 17 08:54:50 c2s55bf36eb4700    info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Mar 17 08:54:50 c2s55bf36eb4700    info    Client disconnected: connection closed

From browser console just this warnings, no errors at all

Logger.js:154 2022-03-17T12:07:02.720Z [modules/xmpp/XmppConnection.js] <Os._maybeEnableStreamResume>:  Stream resume enabled, but WebSockets are not enabled
TrackVADEmitter.js:112 [Deprecation] The ScriptProcessorNode is deprecated. Use AudioWorkletNode instead. (https://bit.ly/audio-worklet)

What’s the output of this command:

dpkg -s prosody | grep Version

This is the output

Version: 0.11.9-2+deb11u2

Your logs don’t say much (did I ask for an extract BTW ?). From the little you have shown it’s not possible to have really an idea of what is happening. When in your logs there are lines about ‘Member left’, is there an explicit action of your users such as clicking the hangup button, or is there a disconnect message appearing on its own ?

Send the extract as the entire log was the same, so to avoid a huge
amount of nothing send just a part of it.

I found nothing like a message and pretty sure no user triggered the
hangup button.

However everything is working just fine right now. Without made any
change at all.