Hi,
We are currently using Jitsi 2.0.5142-1 on Ubuntu 20.04 with ldap2 integration using instructions from https://github.com/jitsi/jitsi-meet/wiki/LDAP-Authentication#ldap-authentication-for-jitsi-meet-via-ldap2 .
Authentication and anonymous access are working fine.
Now we started to evaluate the new lobby feature which is unfortunately not working as expected.
After reading multiple forum threads we have adjusted our configuration but nothing worked so far.
The moderator is able to activate a lobby via UI but afterwards new users are not able to join until the moderator disables the lobby feature again. It looks like new users are waiting for acknowledgement of the moderator, who never receives an info though. Disabling lobby feature allows everyone to join again.
Maybe someone has an advice on how to process. Debugging prosody log did not return any valuable information.
Enabling the lobby feature shows following log in developer console:
[JitsiConferenceEventManager.js] <a.>: Ignored XMPPEvents.JSON_MESSAGE_RECEIVED for not existing participant: 1@conference.meet.example.com/3a6ee0ef {type: “lobby-notify”, value: true, event: “LOBBY-ENABLED”}
Following configuration has been setup so far:
/etc/prosody/conf.avail/meet.example.com.cfg.lua
VirtualHost "meet.example.com"
authentication = "ldap2"
ssl = {
key = "/etc/prosody/certs/meet.example.com.key";
certificate = "/etc/prosody/certs/meet.example.com.crt";
}
speakerstats_component = "speakerstats.meet.example.com"
conference_duration_component = "conferenceduration.meet.example.com"
modules_enabled = {
"bosh";
"pubsub";
"ping";
"speakerstats";
"turncredentials";
"conference_duration";
}
c2s_require_encryption = false
VirtualHost "guest.meet.example.com"
authentication = "anonymous"
modules_enabled = {
"muc_lobby_rooms";
}
lobby_muc = "lobby.meet.example.com"
main_muc = "conference.meet.example.com"
c2s_require_encryption = false
Component "conference.meet.example.com" "muc"
storage = "memory"
modules_enabled = {
"muc_meeting_id";
"muc_domain_mapper";
}
admins = { "focus@auth.meet.example.com" }
muc_room_locking = false
muc_room_default_public_jids = true
Component "internal.auth.meet.example.com" "muc"
storage = "memory"
modules_enabled = {
"ping";
}
admins = { "focus@auth.meet.example.com", "jvb@auth.meet.example.com" }
muc_room_locking = false
muc_room_default_public_jids = true
VirtualHost "auth.meet.example.com"
ssl = {
key = "/etc/prosody/certs/auth.meet.example.com.key";
certificate = "/etc/prosody/certs/auth.meet.example.com.crt";
}
authentication = "internal_plain"
Component "focus.meet.example.com"
component_secret = "xxx"
Component "speakerstats.meet.example.com" "speakerstats_component"
muc_component = "conference.meet.example.com"
Component "conferenceduration.meet.example.com" "conference_duration_component"
muc_component = "conference.meet.example.com"
Component "lobby.meet.example.com" "muc"
storage = "memory"
restrict_room_creation = true
muc_room_locking = false
muc_room_default_public_jids = true
Looking forward for any advice.
Best regards
Kevin