Dear Prosody Team, I belive to have an similar but different Issue to https://issues.prosody.im/1773 we are running jitsi version stable-8252 from docker hub and experience the following error when trying to create internal prosody users. We also reported this problem to the Jitsi team, it apears however to be an issue on the prosody side of the codebase. ```text root@b0b30bcfd82a:/# prosodyctl --config /config/prosody.cfg.lua adduser test@meet.jitsi modulemanager error Error initializing module 'auth_cyrus' on 'meet.jitsi': /prosody-plugins/mod_auth_cyrus.lua:20: attempt to call a nil value (field 'unlock_globals') stack traceback: /prosody-plugins/mod_auth_cyrus.lua:20: in main chunk [C]: in function 'util.xpcall.xpcall' /usr/share/lua/5.4/prosody/core/modulemanager.lua:270: in upvalue 'do_load_module' /usr/share/lua/5.4/prosody/core/modulemanager.lua:353: in function 'core.modulemanager.load' /usr/share/lua/5.4/prosody/core/usermanager.lua:97: in function 'core.usermanager.initialize_host' /usr/share/lua/5.4/prosody/util/prosodyctl.lua:97: in function 'util.prosodyctl.user_exists' /usr/bin/prosodyctl:156: in field '?' /usr/bin/prosodyctl:751: in upvalue 'func' /usr/share/lua/5.4/prosody/util/async.lua:144: in function </usr/share/lua/5.4/prosody/util/async.lua:142> Enter new password: Retype new password: modulemanager error Error initializing module 'auth_cyrus' on 'meet.jitsi': /prosody-plugins/mod_auth_cyrus.lua:20: attempt to call a nil value (field 'unlock_globals') stack traceback: /prosody-plugins/mod_auth_cyrus.lua:20: in main chunk [C]: in function 'util.xpcall.xpcall' /usr/share/lua/5.4/prosody/core/modulemanager.lua:270: in upvalue 'do_load_module' /usr/share/lua/5.4/prosody/core/modulemanager.lua:353: in function 'core.modulemanager.load' /usr/share/lua/5.4/prosody/core/usermanager.lua:97: in function 'core.usermanager.initialize_host' /usr/share/lua/5.4/prosody/util/prosodyctl.lua:81: in function 'util.prosodyctl.adduser' /usr/bin/prosodyctl:164: in field '?' /usr/bin/prosodyctl:751: in upvalue 'func' /usr/share/lua/5.4/prosody/util/async.lua:144: in function </usr/share/lua/5.4/prosody/util/async.lua:142> Error: Method not implemented ``` The user is apparently not created because we are unable to use it afterwards and the error of course suggests some malfunction. We did already try to use prosodyctl register instead but end up with the same error. ```text root@b0b30bcfd82a:/# prosodyctl register test meet.jitsi TestPassword modulemanager error Error initializing module 'auth_cyrus' on 'meet.jitsi': /prosody-plugins/mod_auth_cyrus.lua:20: attempt to call a nil value (field 'unlock_globals') stack traceback: /prosody-plugins/mod_auth_cyrus.lua:20: in main chunk [C]: in function 'util.xpcall.xpcall' /usr/share/lua/5.4/prosody/core/modulemanager.lua:270: in upvalue 'do_load_module' /usr/share/lua/5.4/prosody/core/modulemanager.lua:353: in function 'core.modulemanager.load' /usr/share/lua/5.4/prosody/core/usermanager.lua:97: in function 'core.usermanager.initialize_host' /usr/share/lua/5.4/prosody/util/prosodyctl.lua:81: in function 'util.prosodyctl.adduser' /usr/bin/prosodyctl:599: in field '?' /usr/bin/prosodyctl:751: in upvalue 'func' /usr/share/lua/5.4/prosody/util/async.lua:144: in function </usr/share/lua/5.4/prosody/util/async.lua:142> Error: Method not implemented ``` We did also try the latest dev version of prosody without any change. The line mentioned in the error message also seams to indicate that the code might be subject to change at the moment, so i am unsure if this is a bug or some misconfiguration on our side. This is the line at /prosody-plugins/mod_auth_cyrus.lua:20 mentioned above ```text prosody.unlock_globals(); --FIXME: Figure out why this is needed and -- why cyrussasl isn't caught by the sandbox ``` Should you have further insight into this, please do share it and thanks for your awesome work of course!

Hello Prosody team, I was able to resolve my issue, although i dont really understand why my actions changed much. Since i was unable to use cyrus authentication i tried to connect prosody to ldap for a while but did reset eventually to start over and it just started working again with cyrus auth. although i dont grasp what changed in detail it works now. You can close this issue. Many thanks