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

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

the port forwarding are ok, I remarked the problem happens when I shared phone internet with my laptop.
it’s strange!

Which address are you using to connect to the jitsi server?
Is there only one address or do you switch it according to the situation?

there is one address, public IP address.

my server behind reverse proxy and the proxy behind nat.
router (NAT) > reverse proxy (nginx) > Jitsi Instance

Did you add the port forwarding rule for UDP/10000 to your router?
seems missing or wrong…

thanks emrah for your reaction. it’s forwarding corretly.

the problem happens only for the moment when I use my mobile internet. my pc uses htspots of my phone

Could you check the UDP/10000 connectivity while using the hotspot. Use the following method

Tip: how to check UDP/10000 connectivity

1 Like