Issue with Lobby feature

Hi fellows,

Im using Docker Jitsi in the latest version and i´m facing a significant issue with Lobby feature.

A user start a room and some participants are in (so far so well). When the moderator activate the lobby, all other participants are dropped. Just one participant remain.
In the logs, nothing significant. In prosody log, just this error:

mod_bosh error Traceback[bosh]: /prosody-plugins/mod_muc_lobby_rooms.lua:134: attempt to index local ‘room’ (a nil value)

In Jicofo log, in the moment that moderator activated lobby, the room just terminate:

Jicofo 2020-09-30 10:54:50.313 INFO: [31] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberLeft sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@67dc483 member=ChatMember[testelobby@muc.meet.jitsi/5f9bd1c2, jid: c46lnvacmugbtsao@guest.meet.jitsi/JBAQfVxI]@1688897470]
Jicofo 2020-09-30 10:54:50.313 INFO: [31] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member testelobby@muc.meet.jitsi/5f9bd1c2 is leaving
Jicofo 2020-09-30 10:54:50.313 INFO: [31] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Terminating Participant[testelobby@muc.meet.jitsi/5f9bd1c2]@470825854, reason: gone, send st: false
Jicofo 2020-09-30 10:54:50.313 INFO: [31] org.jitsi.protocol.xmpp.AbstractOperationSetJingle.log() Terminate session: testelobby@muc.meet.jitsi/5f9bd1c2, reason: gone, send terminate: false

I use secure domain and my prosody config is:

admins = {
"focus@auth.meet.jitsi",
"jvb@auth.meet.jitsi"
}

plugin_paths = { "/prosody-plugins/", "/prosody-plugins-custom" }
http_default_host = "meet.jitsi"

VirtualHost "meet.jitsi"


authentication = "cyrus"
cyrus_application_name = "xmpp"
allow_unencrypted_plain_auth = true


ssl = {
    key = "/config/certs/meet.jitsi.key";
    certificate = "/config/certs/meet.jitsi.crt";
}
modules_enabled = {
    "bosh";
    "pubsub";
    "ping";
    "speakerstats";
    "conference_duration";
    "auth_cyrus";

}

speakerstats_component = "speakerstats.meet.jitsi"
conference_duration_component = "conferenceduration.meet.jitsi"

c2s_require_encryption = false


VirtualHost "guest.meet.jitsi"
authentication = "anonymous"
c2s_require_encryption = false

modules_enabled = {
    "muc_lobby_rooms"
}

main_muc = "muc.meet.jitsi"
lobby_muc = "lobby.meet.jitsi"



VirtualHost "auth.meet.jitsi"
ssl = {
    key = "/config/certs/auth.meet.jitsi.key";
    certificate = "/config/certs/auth.meet.jitsi.crt";
}
authentication = "internal_hashed"


VirtualHost "recorder.meet.jitsi"
modules_enabled = {
  "ping";
}
authentication = "internal_hashed"


Component "internal-muc.meet.jitsi" "muc"
storage = "memory"
modules_enabled = {
    "ping";

}
muc_room_locking = false
muc_room_default_public_jids = true

Component "muc.meet.jitsi" "muc"
storage = "memory"
modules_enabled = {
    "muc_meeting_id";


}
muc_room_cache_size = 1000
muc_room_locking = false
muc_room_default_public_jids = true

Component "focus.meet.jitsi"
component_secret = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

Component "speakerstats.meet.jitsi" "speakerstats_component"
muc_component = "muc.meet.jitsi"

Component "conferenceduration.meet.jitsi" "conference_duration_component"
muc_component = "muc.meet.jitsi"


Component "lobby.meet.jitsi" "muc"
storage = "memory"
restrict_room_creation = true
muc_room_locking = false
muc_room_default_public_jids = true

Anyone have some ideia whats happening?

There was a problem like that in lib-jitsi-meet while ago, but it was fixed, are you using latest?

This was the fix: https://github.com/jitsi/lib-jitsi-meet/commit/15dcc57424cc937290e1963b8eb402c1fcf48ccb

I think so. This are my versions:

JVB:
INFO: VersionService registered: JVB 2.1.273-g072dd44b

Jicofo:
Jicofo 2020-09-24 14:24:59.875 INFO: [12] org.jitsi.version.AbstractVersionActivator.log() VersionService registered: JiCoFo 1.0.612

Prosody:
startup info Hello and welcome to Prosody version 0.11.5

This is a version from July where the fix is from Aug in jitsi-meet, so I suppose and your jitsi-meet is as older as jicofo.

I’ll update my Jitsi Docker Images as soon as possible and gave you a feedback.

Thank you very much! I appreciate all the work you guys doing here, it’s fantastic!

I updated to stable-5076: release and the issue was solved. Thanks a lot !