Unable to connect users - bad argument #1 to 'lower'

Description:

After updating to the latest unstable users are no longer able to connect in meetings. The host opens the room with the JWT and the users are able to join but the video and audio feeds never connect. I will be happy to supply more verbose logs privately. Using BOSH for xmpp and websockets for videobridge. The error I am getting in prosody seems to be related to token/util.lib.lua

Steps to reproduce:

1. Open Browser and start a meeting using JWT
2. Open incognito tab and join the meeting as a “guest”
3. Both users will be in the same meeting but will not connect to one another
4. The same is true when adding more users

Expected behavior:

Users should connect to share audio and video

Actual behavior:

Users all appear to be in the same room but no one else is present.

Server information:

• Jitsi Meet version: 2.0.5947-1
• Operating System: Ubuntu 18

Client information:

• Chrome, Firefox
• Operating System: Windows 10, Mac 11.2.3

Additional information:

prosody.err:

Jun 02 09:32:05 mod_bosh        error   Traceback[bosh]: /usr/share/jitsi-meet/prosody-plugins/token/util.lib.lua:343: bad argument #1 to 'lower' (string expected, got nil)
stack traceback:
        [C]: in function 'lower'
        /usr/share/jitsi-meet/prosody-plugins/token/util.lib.lua:343: in function 'verify_room'
        ...re/jitsi-meet/prosody-plugins/mod_token_verification.lua:62: in function 'verify_user'
        ...re/jitsi-meet/prosody-plugins/mod_token_verification.lua:86: in function '?'
        /usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
        (...tail calls...)
        /usr/lib/prosody/modules/muc/muc.lib.lua:561: in function '_handle_normal_presence'
        ...hare/jitsi-meet/prosody-plugins/mod_token_moderation.lua:24: in function <...hare/jitsi-meet/prosody-plugins/mod_token_moderation.lua:23>
        (...tail calls...)
        /usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
        (...tail calls...)
        /usr/lib/prosody/core/stanza_router.lua:180: in function 'core_post_stanza'
        /usr/lib/prosody/core/stanza_router.lua:127: in function 'dispatch_stanza'
        /usr/lib/prosody/modules/mod_bosh.lua:323: in function 'func'
        /usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125>
stack traceback:
        /usr/lib/prosody/util/async.lua:211: in function 'run'
        /usr/lib/prosody/modules/mod_bosh.lua:465: in function 'cb_handlestanza'
        /usr/lib/prosody/util/xmppstream.lua:182: in function </usr/lib/prosody/util/xmppstream.lua:162>
        [C]: in function 'parse'
        /usr/lib/prosody/util/xmppstream.lua:285: in function 'feed'
        /usr/lib/prosody/modules/mod_bosh.lua:134: in function '?'
        /usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
        (...tail calls...)
        /usr/lib/prosody/net/http/server.lua:229: in function </usr/lib/prosody/net/http/server.lua:176>
        [C]: in function 'xpcall'
        /usr/lib/prosody/net/http/server.lua:108: in function 'process_next'
        /usr/lib/prosody/net/http/server.lua:124: in function 'success_cb'
        /usr/lib/prosody/net/http/parser.lua:177: in function 'feed'
        /usr/lib/prosody/net/http/server.lua:155: in function </usr/lib/prosody/net/http/server.lua:154>
        (...tail calls...)
        /usr/lib/prosody/net/server_select.lua:924: in function </usr/lib/prosody/net/server_select.lua:908>
        [C]: in function 'xpcall'
        /usr/bin/prosody:76: in function 'loop'
        /usr/bin/prosody:86: in main chunk
        [C]: in ?

Prosody log:

Jun 02 09:33:29 bosh453d8670-ec07-4a2e-b650-86cae68cb015        debug   Received[c2s]: <presence to='[e-mail]/1cd6b951'>
Jun 02 09:33:29 conference.meet.myserver.com:muc        debug   no occupant found for [e-mail]/1cd6b951; creating new occupant object for [e-mail]/jpXQuHg7
Jun 02 09:33:29 general info    --------------> user 1cd6b951-35e6-4848-b5d1-4d1dc7b2355d domain guest.meet.myserver.com res jpXQuHg7 pass nil
Jun 02 09:33:29 conference.meet.myserver.com:token_verification debug   pre join: MUC room ([e-mail]) <presence from='[e-mail]/jpXQuHg7' to='[e-mail]/1cd6b951'><x xmlns='http://jabber.org/protocol/muc'/><stats-id>Gayle-J7R</stats-id><region id='us-east-1' xmlns='http://jitsi.org/jitsi-meet'/><c ver='GFN9rIHAX0oGpTKtxSr6D7qvTiM=' node='http://jitsi.org/jitsimeet' xmlns='http://jabber.org/protocol/caps' hash='sha-1'/><jitsi_participant_region>us-east-1</jitsi_participant_region><jitsi_participant_codecType>vp8</jitsi_participant_codecType><email>[e-mail]</email><nick xmlns='http://jabber.org/protocol/nick'>Sumner Robinson</nick><audiomuted>false</audiomuted><videomuted>false</videomuted></presence>
Jun 02 09:33:29 conference.meet.myserver.com:token_verification debug   Session token: nil, session room: nil
Jun 02 09:33:29 conference.meet.myserver.com:token_verification debug   Will verify token for user: [e-mail]/jpXQuHg7, room: [e-mail]/1cd6b951
Jun 02 09:33:29 runnerQRfaQpzL  debug   changed state from ready to error (ready)
Jun 02 09:33:29 mod_bosh        error   Traceback[bosh]: /usr/share/jitsi-meet/prosody-plugins/token/util.lib.lua:343: bad argument #1 to 'lower' (string expected, got nil)
stack traceback:
        [C]: in function 'lower'
        /usr/share/jitsi-meet/prosody-plugins/token/util.lib.lua:343: in function 'verify_room'
        ...re/jitsi-meet/prosody-plugins/mod_token_verification.lua:62: in function 'verify_user'
        ...re/jitsi-meet/prosody-plugins/mod_token_verification.lua:86: in function '?'
        /usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
        (...tail calls...)
        /usr/lib/prosody/modules/muc/muc.lib.lua:561: in function '_handle_normal_presence'
        ...hare/jitsi-meet/prosody-plugins/mod_token_moderation.lua:24: in function <...hare/jitsi-meet/prosody-plugins/mod_token_moderation.lua:23>
        (...tail calls...)
        /usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
        (...tail calls...)
        /usr/lib/prosody/core/stanza_router.lua:180: in function 'core_post_stanza'
        /usr/lib/prosody/core/stanza_router.lua:127: in function 'dispatch_stanza'
        /usr/lib/prosody/modules/mod_bosh.lua:323: in function 'func'
        /usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125>
stack traceback:
        /usr/lib/prosody/util/async.lua:211: in function 'run'
        /usr/lib/prosody/modules/mod_bosh.lua:465: in function 'cb_handlestanza'
        /usr/lib/prosody/util/xmppstream.lua:182: in function </usr/lib/prosody/util/xmppstream.lua:162>
        [C]: in function 'parse'
        /usr/lib/prosody/util/xmppstream.lua:285: in function 'feed'
        /usr/lib/prosody/modules/mod_bosh.lua:134: in function '?'
        /usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
        (...tail calls...)
        /usr/lib/prosody/net/http/server.lua:229: in function </usr/lib/prosody/net/http/server.lua:176>
        [C]: in function 'xpcall'
        /usr/lib/prosody/net/http/server.lua:108: in function 'process_next'
        /usr/lib/prosody/net/http/server.lua:124: in function 'success_cb'
        /usr/lib/prosody/net/http/parser.lua:177: in function 'feed'
        /usr/lib/prosody/net/http/server.lua:155: in function </usr/lib/prosody/net/http/server.lua:154>
        (...tail calls...)
        /usr/lib/prosody/net/server_select.lua:924: in function </usr/lib/prosody/net/server_select.lua:908>
        [C]: in function 'xpcall'
        /usr/bin/prosody:76: in function 'loop'
        /usr/bin/prosody:86: in main chunk
        [C]: in ?
Jun 02 09:33:29 mod_bosh        debug   Session 453d8670-ec07-4a2e-b650-86cae68cb015 has 1 out of 1 requests open
Jun 02 09:33:29 mod_bosh        debug   and there are 0 things in the send_buffer:
Jun 02 09:33:29 mod_bosh        debug   Have nothing to say, so leaving request unanswered for now

[damencho]

Thanks for testing and reporting it.

[damencho]

In general we haven’t designed tokens to work with guest domain, so the fact it worked is a coincidence now looking at the code. But there is some issue for sure … I will take a look.