JVB Failed to login. Disconnecting to trigger a re-connect

Hi,

On a new installation I’m experiencing disconnections only when more than one user connects to a room.

What should I make of the following JVB log messages?

INFO: [16] [hostname=localhost id=shard] MucClient$1.connected#259: Connected.
INFO: [16] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#594: Logging in.
WARNING: [16] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#608: Failed to login. Disconnecting to trigger a re-connect.
INFO: [16] [hostname=localhost id=shard] MucClient$1.connectionClosed#271: Closed.
WARNING: [27] [hostname=localhost id=shard] MucClient.setPresenceExtensions#420: Cannot set presence extension: not connected.
INFO: [16] [hostname=localhost id=shard] MucClient$1.connected#259: Connected.
INFO: [16] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#594: Logging in.
WARNING: [16] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#608: Failed to login. Disconnecting to trigger a re-connect.

I followed the standard Debian instructions so I guess something went wrong there. If it’s just a login failure, which config parameters should I be looking for?

I have:

videobridge/sip-communicator.properties:org.jitsi.videobridge.xmpp.user.shard.MUC_JIDS=JvbBrewery@internal.auth.meet.mydomain.org

videobridge/sip-communicator.properties:org.jitsi.videobridge.xmpp.user.shard.USERNAME=jvb

videobridge/sip-communicator.properties:org.jitsi.videobridge.xmpp.user.shard.PASSWORD=oCQzstQq

And this is part of my prosody file:

Component "conference.meet.mydomain.org" "muc"
    storage = "memory"
    modules_enabled = {
        "muc_meeting_id";
        "muc_domain_mapper";
        --"token_verification";
    }
    admins = { "focus@auth.meet.mydomain.org" }
    muc_room_locking = false
    muc_room_default_public_jids = true

-- internal muc component
Component "internal.auth.meet.mydomain.org" "muc"
    storage = "memory"
    modules_enabled = {
        "ping";
    }
    admins = { "focus@auth.meet.mydomain.org", "jvb@auth.meet.mydomain.org" }
    muc_room_locking = false
    muc_room_default_public_jids = true

I also have this:
/var/lib/prosody/auth%2emeet%2emydomain%2eorg/accounts# cat jvb.dat
return {
[“server_key”] = “9d297db470d91babff229760f154e056527309da”;
[“stored_key”] = “2d80a9b8df798e162bed9cecaddbf12bfbec7542”;
[“salt”] = “500e09c8-461e-4b93-8c97-783ebfd9e240”;
[“iteration_count”] = 4096;
};

What can I try?

[EDIT] It seems that uninstalling prosody, re-installing it and re-configuring Jitsi Meet solves the issue. However, it would be better to just be able to fix what seems to be related to prosody users/logins.

2 Likes

I’ve done this for countless times but still same results.