Jitsi crashes with "Unfortunately something went wrong" the moment any second user joins

Description

Whenever a second user tries to join a session, Jitsi crashed for both users (initial hosting and second joining) with “Unfortunately something went wrong”. This behaviour is persistent across browsers, apps and operating systems.

Current behavior

Jitsi crashes when second user joins.

Expected Behavior

Jitsi works when second user joins.

Possible Solution

Unknown

Steps to reproduce

---

Environment details

Jitsi on Debian 10, worked flawlessly until update this morning.

/var/log/jitsi/jvb.log shows

warning "2020-04-06 11:28:36.550 WARNING: [27] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#643: [MucClient id=shard hostname=localhost] error connecting
org.jivesoftware.smack.SmackException$NoResponseException: No response received within reply timeout. Timeout was 5000ms (~5s). While waiting for establishing TLS

/var/log/jitsi/jicofo.log shows

WARNING: [32] org.jitsi.jicofo.bridge.BridgeSelectionStrategy.log() Failed to select initial bridge for participantRegion=null

and

SEVERE: [32] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Can not invite participant -- no bridge available.

And finally /var/log/prosody/prosody.log shows

callcontrol.lulu.youthpolicylabs.org:component  warn    Component not connected, bouncing error for: <iq to='callcontrol.lulu.youthpolicylabs.org' id='3QU5N-39596' from='[e-mail]/focus4353663369260066' type='get'>

and

jitsi-videobridge.lulu.youthpolicylabs.org:component    warn    Component not connected, bouncing error for: <iq to='jitsi-videobridge.lulu.youthpolicylabs.org' id='3QU5N-39598' from='[e-mail]/focus4353663369260066' type='get'>

[bocasaythebert]

@youthpolicy , thanks, it works now

I was following the uninstall guide here : https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md They miss the “apt autoremove” command, with this command it works now

[nafil-gigsboard]

ow avoiding the crash with "Unfor

this solution is without jwt auth. We need to lock the meeting creator for our own host. otherwise anyone can come and create meeting