[How to] How do I use the new Lobby Feature?

Want to get started using the new Lobby feature? Want to learn how it works or see an example of what it should look like? This post will hopefully help you get started!

Great work, Jitsi developers! :clap: The new lobby feature works perfectly!

First and foremost, the lobby feature has been released and works out of the box. Previously, it was under development and you had to install from unstable to get it working. That is a thing of the past. If you read other threads about the lobby feature, check the date first. If it’s before (approx.) 2020-07-21T04:00:00Z, the information may be dated. Keep that in mind. This was posted 2020-08-01T04:00:00Z.

Version Details

I just installed Jitsi Meet on a Ubuntu 18.04.4 LTS lxc container with zero issues. Before installing Jitsi Meet, first install Prosody 0.11.5.

dpkg -l | grep jitsi
ii  jitsi-meet                     2.0.4857-1
ii  jitsi-meet-prosody             1.0.4289-1
ii  jitsi-meet-turnserver          1.0.4289-1
ii  jitsi-meet-web                 1.0.4289-1
ii  jitsi-meet-web-config          1.0.4289-1
ii  jitsi-videobridge2             2.1-273-g072dd44b-1

See it in action

The lobby feature is right there under the shield icon, image, easy to find and use:

Once enabled, when a guest tries to enter they are presented with a new page before they can join:

If “Jackson” clicks on “Ask to Join”, the meeting moderator will see a prompt to “Allow” or “Reject”
image


Configuration Details

The requirements for the lobby feature seem straightforward.

:information_source: To enable the lobby feature you must be sure the proper configuration is present in your server’s Prosody cfg file, typically located under /etc/prosody/conf.d/meet.example.com.cfg.lua.

Anonymous Domain (no user logins/default)

VirtualHost "meet.example.com"
...
        modules_enabled = {
            ...
            "conference_duration";
            "muc_lobby_rooms";
        }
        c2s_require_encryption = false
        lobby_muc = "lobby.meet.example.com"
        main_muc = "conference.meet.example.com"
        -- muc_lobby_whitelist = { "recorder.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
...

Secure Domain (user logins • learn more)

For a secure domain, you need to add the lobby configuration under the guest VirtualHost (as opposed to the main VirtualHost & not both)

:bulb:Make sure you do not have multiple lobby configurations under different VirtualHost sections. This will prevent the lobby from working properly.

...
VirtualHost "guest.test.example.com"
    authentication = "anonymous"
    c2s_require_encryption = false
    modules_enabled = {
            "muc_lobby_rooms";
        }

    lobby_muc = "lobby.test.example.com"
    main_muc = "conference.meet.example.com"
   ...

Component "lobby.test.example.com" "muc"
    storage = "memory"
    restrict_room_creation = true
    muc_room_locking = false
    muc_room_default_public_jids = true

Hope this helps!

5 Likes

Corby, thanks so much for posting all this! I got it to work :smiley:

@grantr, Thats great news! Welcome to the community!

I’ve just signed up here to say thanks.

By the way, do you know where I can post feature requests/suggestions?

I notice that a guest can keep asking to join the meeting after their previous request is rejected, which could allow an uninvited guest to continually disrupt the meeting with multiple requests. I think rejecting a request to join should prevent further requests from that requester.

Also, I notice that as soon as the moderator enters the room, any guests waiting for the moderator to arrive are let into the room too. This could allow a flood of participants (some uninvited) to enter the room before the moderator has had a chance to enable the lobby. To prevent this, I think it would be good if the lobby feature was enabled by default rather than manually switched on by the moderator.

Product ideas and suggestions go here:

https://community.jitsi.org/c/ideas/10

Ok, thanks. I’ll post them both in there now.

@corby Perfect. This worked for my docker-jitsi-meet instance. One small question, I just want the host ( registered in prosody) to allow, reject the guests from the lobby. In the current scenario, the guests approved by the hosts can also accept the knocking requests. How do I do it ?