Lobby/Waiting Room

I have trouble parsing this sentence, what are you talking about ? on meet.jit.si, anyone joining a non existing room becomes the moderator, so room is joined. On secure domain, before having the opportunity to asking to join a non existing room, the user is asked for authentication; if password is given, room is joined, if not there is no lobby. In all cases there is no lobby for a non existing room.

hello, thanks for the answer. Do you have an estimation? are we talking about days, weeks…? thanks

@hirnschmalz We pushed today new stable release which has lobby in it, if you are updating old deployment you need to manually enable the prosody modules: https://github.com/jitsi/jitsi-meet/blob/master/resources/prosody-plugins/mod_muc_lobby_rooms.lua#L1
New deployments should have this enabled by default.

Hi @damencho, thank you for the information. I updated prosody to 0.11.5 Since we use secure domains with LDAP authentication I followed https://github.com/jitsi/jitsi-meet/wiki/LDAP-Authentication .

Sadly there is no lobby feature after clicking the security icon.

The prosody.log looks fine (at least for me).

Jul 21 06:52:20 startup info    Hello and welcome to Prosody version 0.11.5
Jul 21 06:52:20 startup info    Prosody is using the select backend for connection handling
Jul 21 06:52:20 general info    Starting conference duration timer for conference.jitsi.mydomain.com
Jul 21 06:52:20 conferenceduration.jitsi.mydomain.com:conference_duration_component     info    No muc component found, will listen for it: conference.jitsi.mydomain.com
Jul 21 06:52:20 portmanager     info    Activated service 's2s' on [::]:5269, [*]:5269
Jul 21 06:52:20 general info    Starting speakerstats for conference.jitsi.mydomain.com
Jul 21 06:52:20 speakerstats.jitsi.mydomain.com:speakerstats_component  info    No muc component found, will listen for it: conference.jitsi.mydomain.com
Jul 21 06:52:20 speakerstats.jitsi.mydomain.com:speakerstats_component  info    Hook to muc events on conference.jitsi.mydomain.com
Jul 21 06:52:20 conference.jitsi.mydomain.com:muc_domain_mapper info    Loading mod_muc_domain_mapper for host conferenceduration.jitsi.mydomain.com!
Jul 21 06:52:20 conference.jitsi.mydomain.com:muc_domain_mapper info    Loading mod_muc_domain_mapper for host internal.auth.jitsi.mydomain.com!
Jul 21 06:52:20 conference.jitsi.mydomain.com:muc_domain_mapper info    Loading mod_muc_domain_mapper for host speakerstats.jitsi.mydomain.com!
Jul 21 06:52:20 conference.jitsi.mydomain.com:muc_domain_mapper info    Loading mod_muc_domain_mapper for host conference.jitsi.mydomain.com!
Jul 21 06:52:20 conferenceduration.jitsi.mydomain.com:conference_duration_component     info    Hook to muc events on conference.jitsi.mydomain.com
Jul 21 06:52:20 conference.jitsi.mydomain.com:muc_domain_mapper info    Loading mod_muc_domain_mapper for host auth.jitsi.mydomain.com!
Jul 21 06:52:20 portmanager     info    Activated service 'c2s' on [::]:5222, [*]:5222
Jul 21 06:52:20 portmanager     info    Activated service 'legacy_ssl' on no ports
Jul 21 06:52:20 conference.jitsi.mydomain.com:muc_domain_mapper info    Loading mod_muc_domain_mapper for host lobby.jitsi.mydomain.com!
Jul 21 06:52:20 conference.jitsi.mydomain.com:muc_domain_mapper info    Loading mod_muc_domain_mapper for host guest.jitsi.mydomain.com!
Jul 21 06:52:20 conference.jitsi.mydomain.com:muc_domain_mapper info    Loading mod_muc_domain_mapper for host localhost!
Jul 21 06:52:20 conference.jitsi.mydomain.com:muc_domain_mapper info    Loading mod_muc_domain_mapper for host focus.jitsi.mydomain.com!
Jul 21 06:52:20 portmanager     info    Activated service 'component' on [::1]:5347, [127.0.0.1]:5347
Jul 21 06:52:20 conference.jitsi.mydomain.com:muc_domain_mapper info    Loading mod_muc_domain_mapper for host jitsi.mydomain.com!
Jul 21 06:52:20 jitsi.mydomain.com:muc_lobby_rooms      info    Lobby component loaded lobby.jitsi.mydomain.com
Jul 21 06:52:20 portmanager     info    Activated service 'http' on [::]:5280, [*]:5280
Jul 21 06:52:20 portmanager     error   Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
Jul 21 06:52:20 portmanager     error   Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
Jul 21 06:52:20 portmanager     info    Activated service 'https' on no ports
Jul 21 06:52:21 jcp55bb7cb40a50 info    Incoming Jabber component connection
Jul 21 06:52:21 focus.jitsi.mydomain.com:component      info    External component successfully authenticated
Jul 21 06:52:26 conference.jitsi.mydomain.com:muc_domain_mapper warn    Session filters applied
Jul 21 06:52:26 c2s55bb7cb4b3c0 info    Client connected
Jul 21 06:52:26 c2s55bb7cb4b3c0 info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Jul 21 06:52:26 c2s55bb7cb4b3c0 info    Authenticated as focus@auth.jitsi.mydomain.com
Jul 21 06:52:28 conference.jitsi.mydomain.com:muc_domain_mapper warn    Session filters applied
Jul 21 06:52:28 c2s55bb7cbba040 info    Client connected
Jul 21 06:52:28 c2s55bb7cbba040 info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Jul 21 06:52:28 c2s55bb7cbba040 info    Authenticated as jvb@auth.jitsi.mydomain.com
Jul 21 06:52:29 conference.jitsi.mydomain.com:muc_domain_mapper warn    Session filters applied
Jul 21 06:52:29 c2s55bb7cc8af40 info    Client connected
Jul 21 06:52:29 c2s55bb7cc8af40 info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Jul 21 06:52:29 c2s55bb7cc8af40 info    Authenticated as jvb@auth.jitsi.mydomain.com

Hello @damasceno,

This weekend I did a clean install of jitsi from testing (jitsi-meet_2.0.4857-1_all.deb), which became stable today, on Debian Buster. I use authentication, and unfortunately lobby did not work out of the box.
Then I configured /etc/prosody/conf.avail/my.domain.tld.cfg.lua according to https://github.com/jitsi/jitsi-meet/pull/6621/commits/273f357131fa629bb11e9b2e429fb118ae9f3af2 and it still didn’t work for me. Did I forget something, are the instructions incomplete, or is the lobby incompatible with authentication?

Thanks for making Jitsi!

did you follow the unofficial documentation ?

Yes, @gpatel-fr was right, the lobby must be in the guest domain with authentication. Thanks!

It does work with Chrome on a PC, not with the Jitsi app on Android (for me). That took me some time :frowning:

Hi @damencho, I have installed jitsi-meet on my Ubuntu 18.04 LTS box using

deb https://download.jitsi.org stable/

I do not see the lobby waiting feature on the UI. Do I need to install from any other source?

@ahmed_reza

Configure /etc/prosody/conf.avail/my.domain.tld.cfg.lua according to https://github.com/jitsi/jitsi-meet/pull/6621/commits/273f357131fa629bb11e9b2e429fb118ae9f3af2

(add 8 lines)

Moving the required lines form the auth domain to the guest domain as mentioned by @gpatel-fr did the trick. Thx a lot!

@fvw, shouldn’t the new deployments have this enabled by default as of today?

New deployments should have it enabled by default if you install prosody 0.11 in advance.

Hello, I installed a version of jitsi on my server 4 months ago, what steps should I follow to activate the lobby function?
And if someone already implemented it, could they show it how it looks? Thank you very much, we were waiting for this !!

What i did to get it working was a fresh Install of the server files.

Hope this helps someone.

1 Like

Does it necessarily have to be a new jitsi installation?
Can’t update the one already installed on the server?

You have to update prosody 11 and the /etc/prosody/conf.d/file here needs to be updated…so I don’t know if you can update that file without uninstalling and reinstalling.

It only took me an hour tops to reinstall and setup the security… shouldn’t take you much time at all. I’m still in school and this is my co-op so I’m not a pro or anything.

is that if I install jitsi again I will lose the changes made in the interface, that’s why I just want to update to get that new functionality

I’m not really able to answer that question as i hadn’t taken that path. Perhaps @gpatel-fr or @damencho can assist?

Can you not make note of the changes you made and apply on a fresh install?

it depends on what changes you did…if you compiled a new js code, there is no way you can upgrade and keep it. Same thing with css. Config files, not much problem though.

Hi, great support and info sharing …
Today, my last FRESH Installation (on Ubuntu Server 18.04 ) is working like a charm. many thanks !

I’m working with a fresh Install (on Ubuntu server 18.04) and w/ Last release of jitsi.
This works like a charm !

I followed steps summarized from @jmerinchuk
(while upgrading PROSODY because the installation was already working by a couple of days).

Now:
Without activating “Lobby room”, apparently, it is correctly working with 2 or more devices.

Using JitsyMeet 2.3.0 app for Moderator … I can see and activate the Lobby Room option.

Using FF (as Guest) the Lobby Room procedure works fine.

Using JitsiMeet app 20.3.1 in iOS … it works too.

Compliments.
Tnx a lot !