“Unfortunately something went wrong”
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:
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).
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:
/var/log/jitsi/jicofo.log should say something like this when your video bridge starts up:
Added brewery instance: firstname.lastname@example.org/vb1 Added new videobridge: Bridge[email@example.com/vb1, relayId=184.108.40.206:10000, region=us-east-2, stress=0.00] Scheduled health-check task for: firstname.lastname@example.org/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:
Can not invite participant – no bridge available.