In Every breakout room with connected user is showing 1 fake user

[JosefPadua]

What happened?

After update to newest version, in every room is also fake user, after connecting to room, fake user go out. "Dativerak" is default name in my settings for users without name.

Platform

• Chrome (or Chromium based)
• Firefox
• Safari
• Other desktop browser
• Android browser
• iOS browser
• Electron app
• Android mobile app
• iOS mobile app
• Custom app using a mobile SDK

Browser / app / sdk version

stable/jitsi-meet_10888

Relevant log output

Reproducibility

• The problem is reproducible on meet.jit.si

More details?

No response

[damencho]

Can you reproduce this on meet.jit.si or alpha.jitsi.net?

Share js console logs from the browser, prosody logs and your prosody config.

[JosefPadua]

sudo cat /var/log/prosody/prosody.err Apr 04 03:03:11 modulemanager error Error initializing module 'speakerstats_component' on 'speakerstats.meet.dativery.com': /usr/lib/prosody/util/startup.lua:203: module 'prosody.util.queue' not found: no field package.preload['prosody.util.queue'] no file '/usr/lib/prosody/prosody/util/queue.lua' no file '/usr/local/share/lua/5.4/prosody/util/queue.lua' no file '/usr/local/share/lua/5.4/prosody/util/queue/init.lua' no file '/usr/local/lib/lua/5.4/prosody/util/queue.lua' no file '/usr/local/lib/lua/5.4/prosody/util/queue/init.lua' no file '/usr/share/lua/5.4/prosody/util/queue.lua' no file '/usr/share/lua/5.4/prosody/util/queue/init.lua' no file '' no file '/var/lib/prosody/custom_plugins/share/lua/5.4/prosody/util/queue.lua' no file '/var/lib/prosody/custom_plugins/share/lua/5.4/prosody/util/queue/init.lua' no file '/usr/lib/prosody/prosody/util/queue.so' no file '/usr/local/lib/lua/5.4/prosody/util/queue.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.4/prosody/util/queue.so' no file '/usr/lib/lua/5.4/prosody/util/queue.so' no file '/usr/local/lib/lua/5.4/loadall.so' no file '' no file '/usr/lib/prosody/prosody.so' no file '/usr/local/lib/lua/5.4/prosody.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.4/prosody.so' no file '/usr/lib/lua/5.4/prosody.so' no file '/usr/local/lib/lua/5.4/loadall.so' no file '' stack traceback: [C]: in upvalue '_real_require' /usr/lib/prosody/util/startup.lua:203: in function 'require' ...itsi-meet/prosody-plugins/mod_speakerstats_component.lua:14: in main chunk [C]: in function 'util.xpcall.xpcall' /usr/lib/prosody/core/modulemanager.lua:270: in upvalue 'do_load_module' /usr/lib/prosody/core/modulemanager.lua:353: in function 'core.modulemanager.load' /usr/lib/prosody/core/modulemanager.lua:128: in function 'core.modulemanager.load_modules_for_host' /usr/lib/prosody/util/events.lua:81: in function </usr/lib/prosody/util/events.lua:77> (...tail calls...) /usr/lib/prosody/core/hostmanager.lua:108: in function 'core.hostmanager.activate' /usr/lib/prosody/core/hostmanager.lua:58: in field '?' /usr/lib/prosody/util/events.lua:81: in function </usr/lib/prosody/util/events.lua:77> (...tail calls...) /usr/lib/prosody/util/startup.lua:428: in function 'util.startup.prepare_to_start' /usr/lib/prosody/util/startup.lua:707: in function 'util.startup.prosody' /usr/lib/prosody/util/async.lua:156: in upvalue 'func' /usr/lib/prosody/util/async.lua:144: in function </usr/lib/prosody/util/async.lua:142> Apr 11 03:00:55 modulemanager error Error initializing module 'speakerstats_component' on 'speakerstats.meet.dativery.com': /usr/lib/prosody/util/startup.lua:203: module 'prosody.util.queue' not found: no field package.preload['prosody.util.queue'] no file '/usr/lib/prosody/prosody/util/queue.lua' no file '/usr/local/share/lua/5.4/prosody/util/queue.lua' no file '/usr/local/share/lua/5.4/prosody/util/queue/init.lua' no file '/usr/local/lib/lua/5.4/prosody/util/queue.lua' no file '/usr/local/lib/lua/5.4/prosody/util/queue/init.lua' no file '/usr/share/lua/5.4/prosody/util/queue.lua' no file '/usr/share/lua/5.4/prosody/util/queue/init.lua' no file '' no file '/var/lib/prosody/custom_plugins/share/lua/5.4/prosody/util/queue.lua' no file '/var/lib/prosody/custom_plugins/share/lua/5.4/prosody/util/queue/init.lua' no file '/usr/lib/prosody/prosody/util/queue.so' no file '/usr/local/lib/lua/5.4/prosody/util/queue.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.4/prosody/util/queue.so' no file '/usr/lib/lua/5.4/prosody/util/queue.so' no file '/usr/local/lib/lua/5.4/loadall.so' no file '' no file '/usr/lib/prosody/prosody.so' no file '/usr/local/lib/lua/5.4/prosody.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.4/prosody.so' no file '/usr/lib/lua/5.4/prosody.so' no file '/usr/local/lib/lua/5.4/loadall.so' no file '' stack traceback: [C]: in upvalue '_real_require' /usr/lib/prosody/util/startup.lua:203: in function 'require' ...itsi-meet/prosody-plugins/mod_speakerstats_component.lua:14: in main chunk [C]: in function 'util.xpcall.xpcall' /usr/lib/prosody/core/modulemanager.lua:270: in upvalue 'do_load_module' /usr/lib/prosody/core/modulemanager.lua:353: in function 'core.modulemanager.load' /usr/lib/prosody/core/modulemanager.lua:128: in function 'core.modulemanager.load_modules_for_host' /usr/lib/prosody/util/events.lua:81: in function </usr/lib/prosody/util/events.lua:77> (...tail calls...) /usr/lib/prosody/core/hostmanager.lua:108: in function 'core.hostmanager.activate' /usr/lib/prosody/core/hostmanager.lua:58: in field '?' /usr/lib/prosody/util/events.lua:81: in function </usr/lib/prosody/util/events.lua:77> (...tail calls...) /usr/lib/prosody/util/startup.lua:428: in function 'util.startup.prepare_to_start' /usr/lib/prosody/util/startup.lua:707: in function 'util.startup.prosody' /usr/lib/prosody/util/async.lua:156: in upvalue 'func' /usr/lib/prosody/util/async.lua:144: in function </usr/lib/prosody/util/async.lua:142>

I found this error, is it possible its connected with my issue? Thanks for check it for me :)

[damencho]

Which prosody version do you have?

[JosefPadua]

I was able to resolve this issue. The root cause is that the admins setting was missing on the main VirtualHost.

The problem:

The mod_muc_breakout_rooms module runs under the main VirtualHost (e.g. meet.example.com). When it broadcasts the participant list for breakout rooms, it calls get_participants(), which filters out the focus user via is_admin(occupant.bare_jid).

The is_admin() function in util.lib.lua loads the admin list from the context of its host module:

Lua
local config_admin_jids = module:get_option_inherited_set('admins', {}) / jid.prep;
In the default Jitsi Meet installation, admins is defined on the MUC components (conference., breakout., etc.) but not on the main VirtualHost. Since the breakout rooms module runs under the VirtualHost, is_admin() returns false for the focus user, and it leaks through as a visible participant with the default display name.

The fix:

Add admins to the main VirtualHost in the Prosody config:

VirtualHost "meet.example.com"
    authentication = "jitsi-anonymous"
    admins = { "focus@auth.meet.example.com" }