2 users works fine , 3rd user come in and audio/video stop

Same problem here on a Jitsi installation using the latest stable. Our server are not behind NAT and we’re experiencing Pair failed messages in the jvb.log file as soon as a third user join the room. I tried a lot of solutions found on the forum without success. We actually run on old snapshot (JVBv1) and it works great. I hope that we could use JVBv2 soon.

Even with these problems with the latest version, I would like to thank the Jitsi team for his extraordinary work in this particular context. Jitsi Meet is experiencing an extraordinary boom in use and it’s impressive to see all the team on the forum trying to answer all these posts and also working on the code in the same time. We all owe you a pint of your favorite beer!

1 Like

Hello,

I am having also the same issue. I have installed a clean setup on a Debian 10 VPS with a public IP address and Let’s Encrypt certificate.

Initially I had problems only with some clients connecting from corporate network but the problem can be reproduced to all clients by blocking the udp/10000 on the server firewall. Turnserver does not seem to kick in.

Anyone got this solved?

@tuo.mas By any chance you have secure domain configured? And the problem appear for the guests?

For this test instance I wanted to make completely clean fresh install without any customisations. No authentication, just everything from quick start guide plus udp/10000 block in the firewall. End result is that when 3rd joins, the audio and video is not working.

We are on the same boat. Tried with last stable today and same Pair failed error. It seems to be the only problematic message in the jvb.log. I tried all kinds of solutions in the forum but without success. It must be an insignificant detail but I can’t find it.

We run an old version of Jitsi here (JVBv1) and everything works well.

Hi good people, anyone found a solution to “ConnectivityCheckClient $PaceMaker.run#919: Pair failed:” which leads to 3rd+ video calls loosing audio and video?
I’ve setup secure domain and my server is directly on the internet so I find it strange this behavior.
Kindly advise.

@damencho Yes I have secure domain configured. The problem appears for guest and the one moderator in the room.

i configured secure domain
host is LDAP user
2nd user is guest
3rd user is guest

host and 1 guest- ok
host + 2 guests - all 3 losing AV

Hi all,
I’m here the 1st time
installed on a German Strato VServer
used the actual “Quick Install Guide” from Github
after some trouble with the hostname (hxxxxxxx.stratoserver.net is bad for LetsEncrypt, changing hostname of server is officially impossible) it workes - but only with 2 users.
Reason is this text in the quick install guide:

Open ports in your firewall
Open the following ports in your firewall, to allow traffic to the machine running jitsi:
80 TCP
443 TCP
10000 UDP

here, the port 4443 is missing !!!
adding it, reboot, and it works with 3 users, too…
kind regards, keep healthy
Michael

1 Like

This worked for me. Thanks @MBU

This solution didn’t work for me…

EDIT: Sorry, I looked the advanced configuration of install, I put the ports correctly and work like a charm.

Worked for me

Hello All,

I have the same issue but I didn’t figure out the problem.
It was working fine before I upgrade the jitsi.
Could please advice and help me?
once the 3rd guest join, audio and video are stopped.
@damencho, any suggestion, Thank you!

Check out the advanced section of https://jitsi.org/qi

thanks for your answer,

I applied this setting but didn’t solve the issue. any suggestion

org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=<Local.IP.Address> org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=<Public.IP.Address>

Check your port forwarding.

the port fowarding are correct. only when the 3rd guest join I have the problem after He left, the situation becomes normal.

it’s normal, to see the local ip of my pc 192.168.1.39, the 192.168.178.80 is the ip server of my jitsi instance behind NAT and reverse proxy 192.168.178.40.

JVB log:

=cgm4q1em7mvtv2] Agent.setState#923: ICE state changed from Waiting to Running.
2020-11-03 18:48:04.259 INFO: [35] [confId=26f5bd9687c2d0e epId=3dd194de local_ufrag=cgm4q1em7mvtv2 gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com] IceTransport.iceStateChanged#321: ICE state changed old=Waiting new=Running
2020-11-03 18:48:04.259 INFO: [35] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] Agent.startConnectivityEstablishment#735: Trigger checks for pairs that were received before running state
2020-11-03 18:48:04.259 INFO: [35] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] Agent.triggerCheck#1714: Add peer CandidatePair with new reflexive address to checkList: CandidatePair (State=Frozen Priority=7962116751041232895):
LocalCandidate=candidate:1 1 udp 2130706431 192.168.178.80 10000 typ host
RemoteCandidate=candidate:10000 1 udp 1853824767 105.159.35.74 64306 typ prflx
2020-11-03 18:48:04.259 INFO: [35] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] ConnectivityCheckClient.startChecks#142: Start connectivity checks.
2020-11-03 18:48:04.261 INFO: [35] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG componentId=1 conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 name=stream-3dd194de epId=3dd194de local_ufrag=cgm4q1em7mvtv2] Component.addUpdateRemoteCandidates#347: Update remote candidate for stream-3dd194de.RTP: 192.168.1.39:64306/udp
2020-11-03 18:48:04.261 INFO: [35] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG componentId=1 conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 name=stream-3dd194de epId=3dd194de local_ufrag=cgm4q1em7mvtv2] Component.updateRemoteCandidates#481: new Pair added: 192.168.178.80:10000/udp/host -> 192.168.1.39:64306/udp/host (stream-3dd194de.RTP).
2020-11-03 18:48:04.301 INFO: [377] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] ConnectivityCheckClient$PaceMaker.run#922: Pair failed: 192.168.178.80:10000/udp/host -> 192.168.1.39:64306/udp/host (stream-3dd194de.RTP)
2020-11-03 18:48:04.301 INFO: [371] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] ConnectivityCheckClient$PaceMaker.run#922: Pair failed: 192.168.178.80:10000/udp/host -> 192.168.1.39:64306/udp/host (stream-3dd194de.RTP)
2020-11-03 18:48:06.434 INFO: [24] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2020-11-03 18:48:10.584 INFO: [374] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.178.80:10000/udp/host -> 105.159.35.74:64306/udp/prflx (stream-3dd194de.RTP), failing.
2020-11-03 18:48:10.585 INFO: [375] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.178.80:10000/udp/host -> 105.159.35.74:64306/udp/prflx (stream-3dd194de.RTP), failing.
2020-11-03 18:48:10.585 INFO: [375] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] ConnectivityCheckClient.updateCheckListAndTimerStates#442: CheckList will failed in a few seconds if no succeeded checks come
2020-11-03 18:48:10.585 INFO: [374] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] ConnectivityCheckClient.updateCheckListAndTimerStates#442: CheckList will failed in a few seconds if no succeeded checks come
2020-11-03 18:48:15.586 INFO: [370] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] ConnectivityCheckClient$1.run#452: CheckList for stream stream-3dd194de FAILED
2020-11-03 18:48:15.586 INFO: [370] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] Agent.checkListStatesUpdated#1898: Suspicious ICE connectivity failure. Checks failed but the remote end was able to reach us.
2020-11-03 18:48:15.586 INFO: [370] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] Agent.checkListStatesUpdated#1902: ICE state is FAILED
2020-11-03 18:48:15.586 INFO: [370] [confId=26f5bd9687c2d0e gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com ufrag=cgm4q1em7mvtv2 epId=3dd194de local_ufrag=cgm4q1em7mvtv2] Agent.setState#923: ICE state changed from Running to Failed.
2020-11-03 18:48:15.586 INFO: [370] [confId=26f5bd9687c2d0e epId=3dd194de local_ufrag=cgm4q1em7mvtv2 gid=8722 stats_id=Amiya-7PG conf_name=test@conference.meet.mydomaine.com] IceTransport.iceStateChanged#321: ICE state changed old=Running new=Failed
2020-11-03 18:48:16.434 INFO: [24] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false

that is because clients cannot reach your bridge for some reason. When you are back to two you are using p2p and does not go through the bridge.

Check that port forwarding works, check there is no firewall blocking udp 10000, check jvb log in the beginning after the restart - do you see the public address it has - whether it is correctly discovered.

the first step, after restaring jvb, it got the the right ip public, it discovered correctly .

2020-11-03 20:08:21.901 INFO: [12] org.ice4j.ice.harvest.StunMappingCandidateHarvester.discover: Discovered public address 94.105.107.xx:50311/udp from STUN server 193.123.38.83:443/udp using local address 192.168.178.80:0/udp
2020-11-03 20:08:21.902 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Using org.ice4j.ice.harvest.StunMappingCandidateHarvester, face=/192.168.178.80, mask=/94.105.107.xx

I’ll double check the prot forwarding and the firewall. Thanks for your help