Connecties worden er uitgegooid. Dwz je kan connecten, maar als iemand anders joined worden beide uit de ruimte gegooid

[berkes]

P2P mode is enabled:

p2p: {
    // Enables peer to peer mode. When enabled the system will try to
    // establish a direct connection when there are exactly 2 participants
    // in the room. If that succeeds the conference will stop sending data
    // through the JVB and use the peer to peer connection instead. When a
    // 3rd participant joins the conference will be moved back to the JVB
    // connection.
    enabled: true,

This is the best candidate to investigate. Check:

• [x] is it the switching from one to another that provides problems?
• [x] is JVB working now.
• [x] had JVB crashed
• [x] are there JVB errors in the logs

[berkes]

So, it is a known issue, with proper solution:

Error in logs: Can not invite participant -- no bridge available.

• https://community.jitsi.org/t/users-cant-connect-jicofo-needs-to-be-restarted/20696/3

The culprit seems to be: Jicofo 2020-03-21 17:10:09.880 SEVERE: [47] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() One of our bridges failed: jitsi-videobridge.beeldbellen.vc4all.nl

And right before that, JVB: JVB 2020-03-21 17:09:58.981 SEVERE: [18321] org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to remove.

[berkes]

In our case, the issue seems to have started right at boot:

15:53:13.742 SEVERE: [22] org.jitsi.meet.ComponentMain.log() java.net.ConnectException: Connection refused (Connection refused), host:localhost, port:5347

This error continues up to when the group startuppubquiz had it's 3rd participant join and crash with Can not invite participant -- no bridge available.

Port 5347 is prosody, which indeed, was not booted at intial setup:

Mar 21 15:54:26 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

This is probably caused by a certbot/setup error that, indeed, dit occur on inital rollout, due to the certbot ssl cert failing (cause by a dumb f*ckup of me, using domain asp4all.nl and not vc4all.nl).

Conclusion

It is an issue caused at boot time: the server never properly booted fully.

What next:

On reboot of the entire server:

• doublecheck in the logs if connection errors on port 5347 persist.
• Doublecheck that prosody is booted correctly.
• then check if a third participant can join a room successfully.