[How to] Why do I see "Unfortunately something went wrong"? Why does my room 'crash'?

“Unfortunately something went wrong”

:triangular_flag_on_post: This is one of the most common issues users face when installing a new self-hosted Jitsi Meet server

UDP Port 10000

This is usually related to UDP port 10000 not being accessable by the participant’s device. Access to this port is critical because it is used for all video/audio communications.

The first thing to try is Tip: how to check UDP/10000 connectivity.

More on Port 10000

The JVB port is set to 10000 by default, but may be different on your setup:

  1. Docker variable JVB_PORT

  2. sip-communicator.properties: org.jitsi.videobridge.SINGLE_PORT_HARVESTER_PORT

:information_source: The room will “crash” for the participant after about 10 to 20 seconds if the they fail to establish a session with the Jitsi Videobridge (jvb).

:bulb:Getting to the meeting page is just using port TCP 443. Getting audio and/or video flowing between 3 people/tabs is the →real test of success

Why 3 people?

Typically if only 2 people are connected then the default install uses peer-2-peer (P2P) mode, bypassing the server, leading to a false positive. Adding the 3rd person ensures you are using your Jitsi Videobridge


Port 10000 works, now what?

Now it's time to check your logs:

Videobridge: /var/log/jitsi/jvb.log
Jicofo logs: /var/log/jitsi/jicofo.log

Your /var/log/jitsi/jicofo.log should say something like this when your video bridge starts up:

Added brewery instance: jvbbrewery@internal.meet.mydomain.net/vb1
Added new videobridge: Bridge[jid=jvbbrewery@internal.meet.mydomain.net/vb1, relayId=123.1.2.3:10000, region=us-east-2, stress=0.00]
Scheduled health-check task for: jvbbrewery@internal.meet.mydomain.net/vb1

If you don’t see something similar in your logs, then your JVB is not connected. When 3 people join, your Jicofo logs will show an error, like this:

:x: Can not invite participant – no bridge available.

1 Like

Specifically, what issues do you see in your log files? It’s necessary to review the errors in the log files to troubleshoot further.

Can you attach them as files so the community can assist?

1 Like

Focus disconnected … check jicofo logs.

Jicofo 2020-08-28 22:21:40.396 SEVERE: [32] org.jitsi.xmpp.component.ComponentBase.log() Failed to send ping
java.lang.NullPointerException
        at org.xmpp.component.AbstractComponent.send(AbstractComponent.java:925)
        at org.jitsi.xmpp.component.ComponentBase.access$400(ComponentBase.java:36)
        at org.jitsi.xmpp.component.ComponentBase$PingTask.run(ComponentBase.java:577)
        at java.util.TimerThread.mainLoop(Timer.java:555)
        at java.util.TimerThread.run(Timer.java:505)
Jicofo 2020-08-28 22:21:41.086 SEVERE: [411] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.log() Failed to connect/login: SASLError using SCRAM-SHA-1: not-authorized
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
        at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java:292)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1100)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
        at java.lang.Thread.run(Thread.java:748)
Jicofo 2020-08-28 22:21:41.318 SEVERE: [33] org.jitsi.meet.ComponentMain.log() not-authorized, host:xmpp.meet.jitsi, port:5347
org.xmpp.component.ComponentException: not-authorized
        at org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:243)
        at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:242)
        at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:222)
        at org.jitsi.meet.ComponentMain.lambda$getConnectCallable$0(ComponentMain.java:285)
        at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Jicofo 2020-08-28 22:21:46.151 SEVERE: [411] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.log() Failed to connect/login: SASLError using SCRAM-SHA-1: not-authorized
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
        at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java:292)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1100)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
        at java.lang.Thread.run(Thread.java:748)
Jicofo 2020-08-28 22:21:46.321 SEVERE: [33] org.jitsi.meet.ComponentMain.log() not-authorized, host:xmpp.meet.jitsi, port:5347
org.xmpp.component.ComponentException: not-authorized
        at org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:243)
        at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:242)
        at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:222)
        at org.jitsi.meet.ComponentMain.lambda$getConnectCallable$0(ComponentMain.java:285)
        at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

This is wrong password.

This is wrong component secret.

I fixed it changing in .env

CONFIG= ~/.jitsi-meet-cfg by CONFIG= .jitsi-meet-cfg !