Jitsi disconnects after token auth

I had Jitsi working with token auth, albeit with some issues, and I decided to try upgrading to the latest unstable debs.

Now whenever I start a room and authenticate with a token, I get the “Unfortunately, something went wrong” message and endless reconnects.

The javascript console shows _allocateConferenceFocusError
Jicofo’s logs show me this:

Jicofo 2020-09-02 15:21:39.561 INFO: [54] org.jitsi.jicofo.xmpp.FocusComponent.handleConferenceIq().401 Focus request for room: intellectualscratchesskipdownstairs@conference.beach.mydomain.us
Jicofo 2020-09-02 15:21:39.562 INFO: [54] org.jitsi.jicofo.auth.AbstractAuthAuthority.log() Authentication session created for 6d7f18cc-ac7e-4337-95ee-df022d43cc63@beach.mydomain.us SID: 31695739-7308-4185-9f11-76e97f464c20
Jicofo 2020-09-02 15:21:39.562 INFO: [54] org.jitsi.jicofo.auth.AbstractAuthAuthority.log() Authenticated jid: 6d7f18cc-ac7e-4337-95ee-df022d43cc63@beach.mydomain.us/jiCf-dEu with session: AuthSession[ID=6d7f18cc-ac7e-4337-95ee-df022d43cc63@beach.mydomain.us, JID=6d7f18cc-ac7e-4337-95ee-df022d43cc63@beach.mydomain.us/jiCf-dEu, SID=31695739-7308-4185-9f11-76e97f464c20, MUID=426897a73c731f85f7098f12a2ec0cd3, LIFE_TM_SEC=0, R=intellectualscratchesskipdownstairs@conference.beach.mydomain.us]@1483999980
Jicofo 2020-09-02 15:21:39.562 INFO: [54] org.jitsi.jicofo.auth.AbstractAuthAuthority.log() Jid 6d7f18cc-ac7e-4337-95ee-df022d43cc63@beach.mydomain.us/jiCf-dEu authenticated as: 6d7f18cc-ac7e-4337-95ee-df022d43cc63@beach.mydomain.us
Jicofo 2020-09-02 15:21:39.563 INFO: [54] org.jitsi.jicofo.FocusManager.log() Created new focus for intellectualscratchesskipdownstairs@conference.beach.mydomain.us@auth.beach.mydomain.us. Conference count 1,options:
Jicofo 2020-09-02 15:21:39.564 INFO: [54] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Joining the room: intellectualscratchesskipdownstairs@conference.beach.mydomain.us
Jicofo 2020-09-02 15:21:39.567 INFO: [54] org.jitsi.jicofo.FocusManager.log() Disposed conference for room: intellectualscratchesskipdownstairs@conference.beach.mydomain.us conference count: 0
Jicofo 2020-09-02 15:21:39.568 INFO: [54] org.jitsi.jicofo.FocusManager.log() Exception while trying to start the conference
net.java.sip.communicator.service.protocol.OperationFailedException: Failed to join the room
  at org.jitsi.impl.protocol.xmpp.ChatRoomImpl.joinAs(ChatRoomImpl.java:298)
  at org.jitsi.impl.protocol.xmpp.ChatRoomImpl.join(ChatRoomImpl.java:209)
  at org.jitsi.jicofo.JitsiMeetConferenceImpl.joinTheRoom(JitsiMeetConferenceImpl.java:560)
  at org.jitsi.jicofo.JitsiMeetConferenceImpl.start(JitsiMeetConferenceImpl.java:386)
  at org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:413)
  at org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:362)
  at org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:337)
  at org.jitsi.jicofo.xmpp.FocusComponent.handleConferenceIq(FocusComponent.java:421)
  at org.jitsi.jicofo.xmpp.FocusComponent.handleIQSetImpl(FocusComponent.java:259)
  at org.jitsi.xmpp.component.ComponentBase.handleIQSet(ComponentBase.java:362)
  at org.xmpp.component.AbstractComponent.processIQRequest(AbstractComponent.java:515)
  at org.xmpp.component.AbstractComponent.processIQ(AbstractComponent.java:289)
  at org.xmpp.component.AbstractComponent.processQueuedPacket(AbstractComponent.java:239)
  at org.xmpp.component.AbstractComponent.access$100(AbstractComponent.java:81)
  at org.xmpp.component.AbstractComponent$PacketProcessor.run(AbstractComponent.java:1051)
  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
  at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: org.jivesoftware.smack.XMPPException$XMPPErrorException: XMPP error reply received from intellectualscratchesskipdownstairs@conference.beach.mydomain.us/focus: XMPPError: internal-server-error - wait. Generated by intellectualscratchesskipdownstairs@conference.beach.mydomain.us
  at org.jivesoftware.smack.XMPPException$XMPPErrorException.ifHasErrorThenThrow(XMPPException.java:132)
  at org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:263)
  at org.jivesoftware.smackx.muc.MultiUserChat.enter(MultiUserChat.java:355)
  at org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:498)
  at org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:444)
  at org.jitsi.impl.protocol.xmpp.ChatRoomImpl.joinAs(ChatRoomImpl.java:240)
  ... 17 more
Jicofo 2020-09-02 15:21:39.570 WARNING: [31] org.jitsi.impl.protocol.xmpp.ChatRoomImpl.log() Unable to handle packet: <presence to='focus@auth.beach.mydomain.us/focus87651315469680' from='intellectualscratchesskipdownstairs@conference.beach.mydomain.us/focus' id='JAFxr-667' type='error'><error type='wait' by='intellectualscratchesskipdownstairs@conference.beach.mydomain.us'><internal-server-error xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></presence>
Jicofo 2020-09-02 15:21:39.570 SEVERE: [54] org.jitsi.jicofo.xmpp.FocusComponent.handleIQSetImpl().324 net.java.sip.communicator.service.protocol.OperationFailedException: Failed to join the room
net.java.sip.communicator.service.protocol.OperationFailedException: Failed to join the room
  at org.jitsi.impl.protocol.xmpp.ChatRoomImpl.joinAs(ChatRoomImpl.java:298)
  at org.jitsi.impl.protocol.xmpp.ChatRoomImpl.join(ChatRoomImpl.java:209)
  at org.jitsi.jicofo.JitsiMeetConferenceImpl.joinTheRoom(JitsiMeetConferenceImpl.java:560)
  at org.jitsi.jicofo.JitsiMeetConferenceImpl.start(JitsiMeetConferenceImpl.java:386)
  at org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:413)
  at org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:362)
  at org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:337)
  at org.jitsi.jicofo.xmpp.FocusComponent.handleConferenceIq(FocusComponent.java:421)
  at org.jitsi.jicofo.xmpp.FocusComponent.handleIQSetImpl(FocusComponent.java:259)
  at org.jitsi.xmpp.component.ComponentBase.handleIQSet(ComponentBase.java:362)
  at org.xmpp.component.AbstractComponent.processIQRequest(AbstractComponent.java:515)
  at org.xmpp.component.AbstractComponent.processIQ(AbstractComponent.java:289)
  at org.xmpp.component.AbstractComponent.processQueuedPacket(AbstractComponent.java:239)
  at org.xmpp.component.AbstractComponent.access$100(AbstractComponent.java:81)
  at org.xmpp.component.AbstractComponent$PacketProcessor.run(AbstractComponent.java:1051)
  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
  at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: org.jivesoftware.smack.XMPPException$XMPPErrorException: XMPP error reply received from intellectualscratchesskipdownstairs@conference.beach.mydomain.us/focus: XMPPError: internal-server-error - wait. Generated by intellectualscratchesskipdownstairs@conference.beach.mydomain.us
  at org.jivesoftware.smack.XMPPException$XMPPErrorException.ifHasErrorThenThrow(XMPPException.java:132)
  at org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:263)
  at org.jivesoftware.smackx.muc.MultiUserChat.enter(MultiUserChat.java:355)
  at org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:498)
  at org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:444)
  at org.jitsi.impl.protocol.xmpp.ChatRoomImpl.joinAs(ChatRoomImpl.java:240)
  ... 17 more
Jicofo 2020-09-02 15:21:39.571 WARNING: [54] org.jitsi.jicofo.xmpp.FocusComponent.processIQ() (serving component 'Jitsi Meet Focus') Unexpected exception while processing IQ stanza: <iq xml:lang="en" from="6d7f18cc-ac7e-4337-95ee-df022d43cc63@beach.mydomain.us/jiCf-dEu" to="focus.beach.mydomain.us" type="set" id="47ab4522-ba0b-4acd-a7e9-a2e89efae923:sendIQ"><conference xmlns="http://jitsi.org/protocol/focus" machine-uid="426897a73c731f85f7098f12a2ec0cd3" room="intellectualscratchesskipdownstairs@conference.beach.mydomain.us"><property value="callcontrol.beach.mydomain.us" name="call_control"/><property value="-1" name="channelLastN"/><property value="false" name="disableRtx"/><property value="false" name="enableLipSync"/><property value="true" name="openSctp"/></conference></iq>
net.java.sip.communicator.service.protocol.OperationFailedException: Failed to join the room
  at org.jitsi.impl.protocol.xmpp.ChatRoomImpl.joinAs(ChatRoomImpl.java:298)
  at org.jitsi.impl.protocol.xmpp.ChatRoomImpl.join(ChatRoomImpl.java:209)
  at org.jitsi.jicofo.JitsiMeetConferenceImpl.joinTheRoom(JitsiMeetConferenceImpl.java:560)
  at org.jitsi.jicofo.JitsiMeetConferenceImpl.start(JitsiMeetConferenceImpl.java:386)
  at org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:413)
  at org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:362)
  at org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:337)
  at org.jitsi.jicofo.xmpp.FocusComponent.handleConferenceIq(FocusComponent.java:421)
  at org.jitsi.jicofo.xmpp.FocusComponent.handleIQSetImpl(FocusComponent.java:259)
  at org.jitsi.xmpp.component.ComponentBase.handleIQSet(ComponentBase.java:362)
  at org.xmpp.component.AbstractComponent.processIQRequest(AbstractComponent.java:515)
  at org.xmpp.component.AbstractComponent.processIQ(AbstractComponent.java:289)
  at org.xmpp.component.AbstractComponent.processQueuedPacket(AbstractComponent.java:239)
  at org.xmpp.component.AbstractComponent.access$100(AbstractComponent.java:81)
  at org.xmpp.component.AbstractComponent$PacketProcessor.run(AbstractComponent.java:1051)
  at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
  at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
  at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: org.jivesoftware.smack.XMPPException$XMPPErrorException: XMPP error reply received from intellectualscratchesskipdownstairs@conference.beach.mydomain.us/focus: XMPPError: internal-server-error - wait. Generated by intellectualscratchesskipdownstairs@conference.beach.mydomain.us
  at org.jivesoftware.smack.XMPPException$XMPPErrorException.ifHasErrorThenThrow(XMPPException.java:132)
  at org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:263)
  at org.jivesoftware.smackx.muc.MultiUserChat.enter(MultiUserChat.java:355)
  at org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:498)
  at org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:444)
  at org.jitsi.impl.protocol.xmpp.ChatRoomImpl.joinAs(ChatRoomImpl.java:240)
  ... 17 more

Can anyone help?

(Edit: forum was stripping the xmpp tags from the logs)

Check prosody logs, probably there is an error there

Thanks!

Found this repeating in /var/log/prosody/prosody.err:

Sep 03 15:00:41 internal.auth.beach.mydomain.us:muc  error Error restoring room jvbbrewery@internal.auth.beach.mydomain.us from storage: no data storage active
Sep 03 15:00:45 conference.beach.mydomain.us:muc error Error restoring room properfriendsfreezewhatever@conference.beach.mydomain.us from storage: no data storage active
Sep 03 15:00:46 internal.auth.beach.mydomain.us:muc  error Error restoring room jvbbrewery@internal.auth.beach.mydomain.us from storage: no data storage active

Looks like my prosody site config file had all of the instances of storage = "memory" changed into storage = "null". All of my other custom local config stuff is unchanged, as far as I can see, so I never expected that an apt install would selectively edit my config file.

Weird. Is this normal?

what is the output?

dpkg-query -f='${Version}\n' --show prosody

0.11.4-1

I’m actually using prosody-trunk, because of what it said in the docs for jitsi-meet-tokens…although that doc is apparently pretty old. Dunno the relation between release versions and trunk versions, but this is what’s installed:

prosody-trunk/now 1nightly1309-1~focal amd64 [installed,local]

Do you think it would be better to go back to the regular prosody package?

The jitsi-meet-prosody post install script changes the storage type during the installation if the installed prosody version is older than 11.0 or is prosody-trunk

Good to know, thanks.

I switched back to regular prosody deb …it shows the same version (0.11.4-1) and it didn’t change my storage types, so all seems well.

Probably the jitsi meet tokens docs should be updated to specify that it needs prosody v0.11 (or whatever)