Participants getting disconnected frequently, connection lost

Install & Config
#1

Hi Community,
On my server the participants suffer from getting disconnected frequently during the conference. And their 3 bar Icon status shows connection lost. there were between 6 and 10 peoples on the meeting and we use only audio and one screen sharing.
the participants use ADSL, 4G or fiber as the internet connection and always we meet same behavior
this behavior is increased when I update my jitsi instance to 2.0.5142-1. It’s terrible each time the participant need reconnect again.
Could anyone help me please to solve this issue?

Here the version:
jitsi-meet/stable,now 2.0.5142-1 all
jitsi-meet-prosody/stable,now 1.0.4466-1 all
jitsi-meet-turnserver/stable,now 1.0.4466-1 all
jitsi-meet-web/stable,now 1.0.4466-1 all ]
jitsi-meet-web-config/stable,now 1.0.4466-1 all
jitsi-videobridge2/stable,now 2.1-376-g9f12bfe2-1 all

On JVB logs, I see this error:

ConnectivityCheckClient.processTimeout#860: timeout for pair: 79.109.118.70.60:20000/udp/srflx 197.75.143.222:49732/udp/prflx (stream-53318ad3.RTP), failing.
Conference.dominantSpeakerChanged#420: ds_change ds_id=20524f5b
Conference.dominantSpeakerChanged#420: ds_change ds_id=7fa17088
Conference.dominantSpeakerChanged#420: ds_change ds_id=20524f5b

ce.meet.mydomain.com ufrag=3ni2p1euu2qnav epId=b19252da local_ufrag=3ni2p1euu2qnav] ConnectivityCheckClient.processTimeout#860: timeout for pair: 79.109.118.70.60:20000/udp/srflx -> 100.66.7.100:45467/udp/prflx (stream-b19252da.RTP), failing.
2021-02-19 23:08:52.309 INFO: [329] [confId=e3f5192a95be3d7b gid=348771 stats_id=Maximo-UXd conf_name=dailymeeting@conference.meet.mydomain.com ufrag=3ni2p1euu2qnav epId=b19252da local_ufrag=3ni2p1euu2qnav] ConnectivityCheckClient.processTimeout#860: timeout for pair: 79.109.118.70.60:20000/udp/srflx -> 100.66.7.100:45467/udp/prflx (stream-b19252da.RTP), failing.
2021-02-19 23:08:55.271 WARNING: [72] [confId=e3f5192a95be3d7b epId=b19252da gid=348771 stats_id=Maximo-UXd conf_name=dailymeeting@conference.meet.mydomain.com] EndpointConnectionStats.processReportBlock#147: Suspiciously high rtt value: 8858.743774999999 ms, remote processing delay was PT0.978256225S (64111), srSentTime was 2021-02-19T22:08:45.434Z, received time was 2021-02-19T22:08:55.271Z
2021-02-19 23:08:55.274 WARNING: [70] [confId=e3f5192a95be3d7b epId=b19252da gid=348771 stats_id=Maximo-UXd conf_name=dailymeeting@conference.meet.mydomain.com] EndpointConnectionStats.processReportBlock#147: Suspiciously high rtt value: 8119.968262 ms, remote processing delay was PT1.720031738S (112724), srSentTime was 2021-02-19T22:08:45.434Z, received time was 2021-02-19T22:08:55.274Z
2021-02-19 23:08:55.310 INFO: [329] [confId=e3f5192a95be3d7b gid=348771 stats_id=Maximo-UXd conf_name=dailymeeting@conference.meet.mydomain.com ufrag=3ni2p1euu2qnav epId=b19252da local_ufrag=3ni2p1euu2qnav] ConnectivityCheckClient.processTimeout#860: timeout for pair: 79.109.118.70.60:20000/udp/srflx -> 100.66.7.100:45467/udp/prflx (stream-b19252da.RTP), failing.
2021-02-19 23:08:56.564 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:08:58.385 INFO: [474] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=7fa17088
2021-02-19 23:09:06.564 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:09:16.563 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:09:26.563 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:09:33.830 INFO: [474] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=20524f5b
2021-02-19 23:09:35.634 INFO: [457] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=7fa17088
2021-02-19 23:09:36.563 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:09:36.588 INFO: [22] VideobridgeExpireThread.expire#140: Running expire()
2021-02-19 23:09:41.642 INFO: [470] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=20524f5b
2021-02-19 23:09:43.442 INFO: [468] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=7fa17088
2021-02-19 23:09:44.644 INFO: [470] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=20524f5b
2021-02-19 23:09:46.563 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:09:54.856 INFO: [470] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=7fa17088
2021-02-19 23:09:55.758 INFO: [470] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=20524f5b
2021-02-19 23:09:56.563 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:10:06.563 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:10:13.588 INFO: [329] [confId=e3f5192a95be3d7b gid=348771 stats_id=Janie-LVa conf_name=dailymeeting@conference.meet.mydomain.com ufrag=5cg8n1euu4s94m epId=53318ad3 local_ufrag=5cg8n1euu4s94m] ConnectivityCheckClient.processTimeout#860: timeout for pair: 79.109.118.70.60:20000/udp/srflx -> 197.75.143.222:49732/udp/prflx (stream-53318ad3.RTP), failing.
2021-02-19 23:10:16.563 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:10:26.563 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:10:28.496 INFO: [491] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=7fa17088
2021-02-19 23:10:29.698 INFO: [459] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=20524f5b
2021-02-19 23:10:36.564 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:10:36.589 INFO: [22] VideobridgeExpireThread.expire#140: Running expire()
2021-02-19 23:10:42.313 INFO: [470] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=7fa17088
2021-02-19 23:10:46.563 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:10:56.564 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:11:06.563 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:11:13.855 INFO: [459] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=20524f5b
2021-02-19 23:11:16.564 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:11:19.599 INFO: [329] [confId=e3f5192a95be3d7b gid=348771 stats_id=Janie-LVa conf_name=dailymeeting@conference.meet.mydomain.com ufrag=5cg8n1euu4s94m epId=53318ad3 local_ufrag=5cg8n1euu4s94m] ConnectivityCheckClient.processTimeout#860: timeout for pair: 79.109.118.70.60:20000/udp/srflx -> 197.75.143.222:49732/udp/prflx (stream-53318ad3.RTP), failing.
2021-02-19 23:11:22.599 INFO: [329] [confId=e3f5192a95be3d7b gid=348771 stats_id=Janie-LVa conf_name=dailymeeting@conference.meet.mydomain.com ufrag=5cg8n1euu4s94m epId=53318ad3 local_ufrag=5cg8n1euu4s94m] ConnectivityCheckClient.processTimeout#860: timeout for pair: 79.109.118.70.60:20000/udp/srflx -> 197.75.143.222:49732/udp/prflx (stream-53318ad3.RTP), failing.
2021-02-19 23:11:25.600 INFO: [329] [confId=e3f5192a95be3d7b gid=348771 stats_id=Janie-LVa conf_name=dailymeeting@conference.meet.mydomain.com ufrag=5cg8n1euu4s94m epId=53318ad3 local_ufrag=5cg8n1euu4s94m] ConnectivityCheckClient.processTimeout#860: timeout for pair: 79.109.118.70.60:20000/udp/srflx -> 197.75.143.222:49732/udp/prflx (stream-53318ad3.RTP), failing.
2021-02-19 23:11:26.564 INFO: [23] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-02-19 23:11:27.976 INFO: [470] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=7fa17088
2021-02-19 23:11:28.599 INFO: [329] [confId=e3f5192a95be3d7b gid=348771 stats_id=Janie-LVa conf_name=dailymeeting@conference.meet.mydomain.com ufrag=5cg8n1euu4s94m epId=53318ad3 local_ufrag=5cg8n1euu4s94m] ConnectivityCheckClient.processTimeout#860: timeout for pair: 79.109.118.70.60:20000/udp/srflx -> 197.75.143.222:49732/udp/prflx (stream-53318ad3.RTP), failing.
2021-02-19 23:11:31.603 INFO: [329] [confId=e3f5192a95be3d7b gid=348771 stats_id=Janie-LVa conf_name=dailymeeting@conference.meet.mydomain.com ufrag=5cg8n1euu4s94m epId=53318ad3 local_ufrag=5cg8n1euu4s94m] ConnectivityCheckClient.processTimeout#860: timeout for pair: 79.109.118.70.60:20000/udp/srflx -> 197.75.143.222:49732/udp/prflx (stream-53318ad3.RTP), failing.
2021-02-19 23:11:32.179 INFO: [457] [confId=e3f5192a95be3d7b gid=348771 conf_name=dailymeeting@conference.meet.mydomain.com] Conference.dominantSpeakerChanged#420: ds_change ds_id=20524f5b
2021-02-19 23:11:34.601 INFO: [329] [confId=e3f5192a95be3d7b gid=348771 stats_id=Janie-LVa conf_name=dailymeeting@conference.meet.mydomain.com ufrag=5cg8n1euu4s94m epId=53318ad3 local_ufrag=5cg8n1euu4s94m] ConnectivityCheckClient.processTimeout#860: timeout for pair: 79.109.118.70.60:20000/udp/srflx -> 197.75.143.222:49732/udp/prflx (stream-53318ad3.RTP), failing.
2021-02-19 2
3:11:34.631 INFO: [36] [confId=e3f5192a95be3d7b epId=53318ad3 gid=348771 stats_id=Janie-LVa conf_name=dailymeeting@conference.meet.mydomain.com] AbstractEndpoint.expire#246: Expiring.
#2

Did you change the default videobridge port (whic is UDP/10000)?
What about your resources (cpu, ram)?

#3

yes, UDP port is 20000.
I have 6 cores and 8G ram.
thanks for your replay.

#4

there is anyone has met the same problem? I’m not able to identify the root cause.

your help guys will be appreciated!

#5

here a test I did with one participate who was using androi jitsi app, always He had connection lost all the time. this is the same behavior when there is more peoples.

image
image1918×913 60.9 KB

#6

Was the connection actually lost? We had fixed such an issue in the bridge where it was just stuck in the UI as a connection lost Fix scenario where endpoint connection status can get stuck on 'inact… · jitsi/jitsi-videobridge@a0bc3d1 · GitHub

#7

it wasn’t lost, we were able to communicate only the UI shows it as lost. when JVB update will be available to solve this issue?

other issue I have mentioned here also is that participants getting disconnected frequently, the logs JVB are above. if you could have a look too. Thanks for your help.

#8

That is already in the latest unstable packages.

#9

@damencho I have installed the last unstable version, but the same issue. I rollbacked the stable version.

I don’t know way this new version it’s different than old one, because also some participance get stuck on loading the 1st page my Jitsi. I reviewed all my config and ports on the routers…I didn’t figure out what the issue. I used fresh instance.

example of participant get stuck on loading 1st paste, when He tried to the open meeting link via chrome android.

image
image720×1280 24.3 KB

#10

here jvb log for another test I did with another participant(outside of my network):
there is any help to figure out the issue? thanks in advance for your help
I made filter on his ip:

main error:
timeout for pair: 192.168.0.79:10000/udp/host → x.x.209.228:56393/udp/prflx (stream-af4c2ae5.RTP), failing.
RemoteCandidate=candidate:10000 1 udp 1853824767 x.x.209.228 64949 typ prflx

 RemoteCandidate=candidate:10000 1 udp 1853824767 x.x.209.228 56393 typ prflx
    2021-02-24 21:51:25.593 INFO: [627] [confId=29986f0da0a3dd54 gid=25198 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=5u5n21evb0clgh epId=af4c2ae5 local_ufrag=5u5n21evb0clgh] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:56393/udp/prflx (stream-af4c2ae5.RTP), failing.
            RemoteCandidate=candidate:10000 1 udp 1853824767 x.x.209.228 64949 typ prflx
    2021-02-24 21:51:41.076 INFO: [627] [confId=29986f0da0a3dd54 gid=25198 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=53pb01evb0d7k6 epId=af4c2ae5 local_ufrag=53pb01evb0d7k6] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:64949/udp/prflx (stream-af4c2ae5.RTP), failing.
            RemoteCandidate=candidate:10000 1 udp 1853824767 x.x.209.228 54090 typ prflx
    2021-02-24 21:51:59.013 INFO: [627] [confId=29986f0da0a3dd54 gid=25198 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=2e3m91evb0dp44 epId=af4c2ae5 local_ufrag=2e3m91evb0dp44] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:54090/udp/prflx (stream-af4c2ae5.RTP), failing.
    2021-02-24 21:51:59.013 INFO: [633] [confId=29986f0da0a3dd54 gid=25198 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=2e3m91evb0dp44 epId=af4c2ae5 local_ufrag=2e3m91evb0dp44] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:54090/udp/prflx (stream-af4c2ae5.RTP), failing.
            RemoteCandidate=candidate:10000 1 udp 1853824767 x.x.209.228 50393 typ prflx
    2021-02-24 21:52:16.959 INFO: [633] [confId=29986f0da0a3dd54 gid=25198 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=6ctr61evb0eaju epId=af4c2ae5 local_ufrag=6ctr61evb0eaju] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:50393/udp/prflx (stream-af4c2ae5.RTP), failing.
            RemoteCandidate=candidate:10000 1 udp 1853824767 x.x.209.228 49495 typ prflx
    2021-02-24 22:16:14.543 INFO: [687] [confId=989cc5411fde9e2c gid=11557 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=c42sb1evb1q5ip epId=4829a5ee local_ufrag=c42sb1evb1q5ip] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:49495/udp/prflx (stream-4829a5ee.RTP), failing.
    2021-02-24 22:16:14.543 INFO: [688] [confId=989cc5411fde9e2c gid=11557 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=c42sb1evb1q5ip epId=4829a5ee local_ufrag=c42sb1evb1q5ip] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:49495/udp/prflx (stream-4829a5ee.RTP), failing.
            RemoteCandidate=candidate:10000 1 udp 1853824767 x.x.209.228 52071 typ prflx
    2021-02-24 22:16:32.561 INFO: [687] [confId=989cc5411fde9e2c gid=11557 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=4kfo41evb1qnum epId=4829a5ee local_ufrag=4kfo41evb1qnum] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:52071/udp/prflx (stream-4829a5ee.RTP), failing.
    2021-02-24 22:16:32.561 INFO: [688] [confId=989cc5411fde9e2c gid=11557 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=4kfo41evb1qnum epId=4829a5ee local_ufrag=4kfo41evb1qnum] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:52071/udp/prflx (stream-4829a5ee.RTP), failing.
            RemoteCandidate=candidate:10000 1 udp 1853824767 x.x.209.228 52081 typ prflx
    2021-02-24 22:16:50.807 INFO: [688] [confId=989cc5411fde9e2c gid=11557 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=6n1md1evb1r9nh epId=4829a5ee local_ufrag=6n1md1evb1r9nh] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:52081/udp/prflx (stream-4829a5ee.RTP), failing.
    2021-02-24 22:16:50.807 INFO: [687] [confId=989cc5411fde9e2c gid=11557 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=6n1md1evb1r9nh epId=4829a5ee local_ufrag=6n1md1evb1r9nh] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:52081/udp/prflx (stream-4829a5ee.RTP), failing.
            RemoteCandidate=candidate:10000 1 udp 1853824767 x.x.209.228 51492 typ prflx
    2021-02-24 22:17:09.922 INFO: [688] [confId=989cc5411fde9e2c gid=11557 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=c974j1evb1rs6l epId=4829a5ee local_ufrag=c974j1evb1rs6l] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:51492/udp/prflx (stream-4829a5ee.RTP), failing.
    2021-02-24 22:17:09.922 INFO: [687] [confId=989cc5411fde9e2c gid=11557 stats_id=Lambert-ndA conf_name=jitsideepdive@conference.meet.mydomain.net ufrag=c974j1evb1rs6l epId=4829a5ee local_ufrag=c974j1evb1rs6l] ConnectivityCheckClient.processTimeout#860: timeout for pair: 192.168.0.79:10000/udp/host -> x.x.209.228:51492/udp/prflx (stream-4829a5ee.RTP), failing.
#11

is there any gentleman can help ?

#12

Are participants still getting a blank page when they try to join a meeting?

#13

they see themself as connected(normal) and others as connection lost with camera and mic muted.

image
image1280×720 48.7 KB

#14

@Yassine but you still hear them or not?

New server install doesn't show video/audio
#15

No, I didn’t hear them, only I see them as connected.