Hello beautiful Jitsi community! Big trouble here.
I’m using Jitsi for 2 years now, on my own deployments, one dev server, one prod server
My use case is 100% one to one, so P2P connection working nearly all the time is crucial. For 2 years, it has been perfect. 1 every 100 connections would fail, the JVB was a fallback then, fine. My bandwidth was safe. Had an upgrade one year before on both deployments, experienced no problem.
With infamous Plan-B dropping from Chrome happening, things began to break last week: an upgrade to last stable was no more an option.
I kept my old Jitsi deployment on one server, and upgraded to the new Jitsi on another one.
Both on Ubuntu 18.04
jitsi-meet-turnserver 1.0. 4466-1
jitsi-meet-web 1.0. 4466-1
jitsi-meet-web-config 1.0. 4466-1
jitsi-meet-tokens 1.0. 5415-1
jitsi-meet-turnserver 1.0. 5415-1
jitsi-meet-web 1.0. 5415-1
jitsi-meet-web-config 1.0. 5415-1
After few hours struggling the regular way on my dev server, everything was working.
In fact, seemed to be working.
I soon discovered monitoring my bandwidth that P2P connection was now ALWAYS failing. After further tests (And tinkering around STUN and TURN settings), I noticed that it was even weirder: if I disconnected one participant and rejoined the room, then P2P was working ALL THE TIME. The nload screenshots from old and new versions shows it well:
Old version (expected behavior):
1b no traffic before conference
2b then a short burst of outgoing traffic, and a tiny rise of incoming traffic upon connection
6b then the conference is running, (almost) no traffic again because it’s P2P
New version (problematic behavior):
1a nothing before conference
2a then a short burst of outgoing traffic, and a tiny rise of incoming traffic upon connection
3a then the conference is running, and all traffic is relayed by the server: P2P failed, that’s my very problem
4a then I disconnect one participant few seconds: back to no traffic
5a this disconnected participant rejoin - short burst of traffic like 2a or 2b
6a the conference is running again, and P2P works this time: almost no traffic (expected behavior)
From here, if I disconnect and reconnect many times, P2P works with EVERY reconnection.
I observed this behavior on EACH of my 50+ tests so far, with clients on same local network, separate networks, behind NAT or not…
It shows that it’s perfectly doable for new Jitsi version to enable a P2P connection, but never on first shot.
Here I am, kind of lost. Why is that happening? What is Jitsi doing a different way on first vs subsequent connections?
Any help would be more than appreciated.