Muc_max_occupants is not working even it is set in prosody config

I enabled muc_max_occupants in /etc/prosody/conf.d/m01.mydomain.com.cfg.lua as below but still we can join with 5 clients. What am I missing here to limit each session to 3 people?

Component "conference.m01.mydomain.com" "muc"
    storage = "none"
    muc_max_occupants = 3
    modules_enabled = {
        "muc_meeting_id";
        "muc_domain_mapper";
        "muc_max_occupants";
        -- "token_verification";
    }
    admins = { "focus@auth.m01.mydomain.com" }
    muc_room_locking = false
    muc_room_default_public_jids = true

I already have /usr/share/jitsi-meet/prosody-plugins/mod_muc_max_occupants.lua in place.

Hi!

I have the same problem. Anybody who knows how to solve it?

Thanks!

Is the second line of the prosody configuration file “plugin_paths” commented out?

Hi @danillo
Yes, is uncommented. I already check prosody logs and there is no errors. Just one, something about a port.

“portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281”

The site has Letscript certificate, and i followed the quick installation guide.

Help please :smiley: !

I am facing the same issue myself. Can someone help.

Component “conference.meet.runsimple.cloud” “muc”
storage = “none”
muc_max_occupants = 1
modules_enabled = {
“muc_meeting_id”;
“muc_domain_mapper”;
“muc_max_occupants”;
– “token_verification”;
}
admins = { “focus@auth.meet.runsimple.cloud” }
muc_room_locking = false
muc_room_default_public_jids = true

And I am facing the same problem.
Edited etc/prosody/conf.d/webrtc.levenoporde.nl.cfg.lua:
Component “conference.webrtc.levenoporde.nl” “muc”
storage = “none”
modules_enabled = {
“muc_meeting_id”;
“muc_domain_mapper”;
– “muc_max_occupants”; (doesn’t work when uncommented)
– “token_verification”;
}
admins = { “focus@auth.webrtc.levenoporde.nl” }
muc_room_locking = false
muc_room_default_public_jids = true
– muc_max_occupants = 3 (doesn’t work when uncommented)

In my case the whole service wouldn’t run, or wouldn’t allow connection(s).

I am also interested in some training/handouts to the logging of things…

Hi, did you ever figure this out? I’m in the same boat.
SSF

Its working for me , not sure what i did … but one thing iam sure was that i moved to prosody-trunk since i wanted to use tokens.

Very cool, would you please post your config, it might be instructive. Damencho said the muc_max_occupants should be 3 to limit to 2, since jicofo counts as 1 of the session participants.
SSF

Dont forget to use muc_access_whitelist (It created a lot of problem without that…) and yes, i have set muc_max_components to 51 , to allow 50 participants.

cross_domain_bosh = false;
consider_bosh_secure = true;
muc_max_occupants = 51
muc_access_whitelist = { “recorder.meet.runsimple.cloud” }
c2s_require_encryption = false

Component “conference.meet.runsimple.cloud” “muc”
storage = “memory”
modules_enabled = {
“muc_meeting_id”;
“muc_domain_mapper”;
“muc_max_occupants”;
“token_verification”;
}
admins = { “focus@auth.meet.runsimple.cloud” }
muc_room_locking = false
muc_room_default_public_jids = true

Thanks, still not wokring for me. Maybe prosody_trunk handles the prejoin event better?
SSF

Which version of prosody you working ?

Prosody version 0.9.12

I will just verify everything on a fresh install. Let me get back to you after i do that

Tested everything on a fresh install and its working …

Fresh Install of Ubuntu 18.04

sudo apt-get update
sudo apt-get upgrade

sudo su -

echo deb http://packages.prosody.im/debian $(lsb_release -sc) main | tee -a /etc/apt/sources.list

wget https://prosody.im/files/prosody-debian-packages.key -O- | apt-key add -

sudo apt-get update
sudo apt-get -y install prosody-trunk

echo “Include “conf.d/*.cfg.lua”” >> /etc/prosody/prosody.cfg.lua

echo “meet.websabha.in” > /etc/hostname

/etc/hosts -> Add meet.websabha.in to 127.0.0.1

reboot

echo ‘deb https://download.jitsi.org stable/’ >> /etc/apt/sources.list.d/jitsi-stable.list
wget -qO - https://download.jitsi.org/jitsi-key.gpg.key | sudo apt-key add -

apt-get install apt-transport-https

apt-get update

apt-get -y install jitsi-meet

Change storage=“memory” from storage=“null” in Component “conference.meet.websabha.in” “muc” , Component “internal.auth.meet.websabha.in” “muc”

cd /etc/prosody/certs

chmod 644 localhost.key

apt-get install lua5.2

systemctl restart prosody

reboot

Add muc_max_occupants in Component “conference.meet.websabha.in” “muc”

muc_max_occupants = 3
muc_access_whitelist = { “recorder.meet.websabha.in” }

Component “conference.meet.websabha.in” “muc”
storage = “memory”
modules_enabled = {
“muc_meeting_id”;
“muc_domain_mapper”;
“muc_max_occupants”;
– “token_verification”;
}

Awesome! I’ll give it a whirl.
SSF

Well, I couldn’t do a fresh install since I’ve got Jitsi running on a server with other apps, but I found prosody-trunk doesn’t play well with Jitsi Meet’s most recent Debian 9 build, wouldn’t display any video oddly enough. I’ll keep at it, maybe try it in a container based on Ubuntu 18.04. Thanks for your help, stay healthy!
SSF

I think the problem is with lua5.2 . Please install lua5.2 and check . I had issues till i installed lua5.2 for prosody…

muc_access_whitelist = { “recorder.webrtc.levenoporde.nl” }

must be inside of
Component “conference.webrtc.levenoporde.nl” “muc”
It cannot be empty. At least that what helped me.

Component “conference.webrtc.levenoporde.nl” “muc”
storage = “none”
modules_enabled = {
“muc_meeting_id”;
“muc_domain_mapper”;
– “muc_max_occupants”; (doesn’t work when uncommented)
– “token_verification”;
}
muc_access_whitelist = { “recorder.webrtc.levenoporde.nl” }
admins = { “focus@auth.webrtc.levenoporde.nl” }

Has anyone gotten this to work?