Screensharing does not work when there are more than 2 participants

[bhuvana]

Hi,
Screen share stops working intermittently. It works for 2 participants but when the 3rd participant joins, screenshare stops working.

Also, video/audio works only for 2 people. When 3rd person joins meeting, audio/video does not work. The participant is unmuted and video is also shared. 3rd Participant can see his own video but others cannot see his video. The 3rd person cannot see moderator video as well.

Jitsi meet is hosted on our servers.
Any ideas how to troubleshoot this issue? Please help.

Thanks.

[emrah]

Seems like an UDP/10000 issue. There are many posts related in this topic.

[bhuvana]

Thanks emrah for the response.

Port 10000 is open. It is hosted in AWS and port is open in firewall settings.
Is there anything else that needs to be done?
I did look through the posts before posting the question here.
And couldn’t find steps to troubleshoot the issue.

[emrah]

Test the UDP/10000 connectivity. Checking the firewall’s rule list doesn’t show it’s working

[bhuvana]

I was checking your post here:

Coturn chronicles

Stage 0 My Coturn chronicles started when I realized that coturn has a problem with Let's Encrypt certificate on Debian Buster. After some tests this issue was solved and I shared the related info on this topic Stage 1 After a while, my friend said that some participants couldn’t connect to the conference. It seemed that these participants didn’t have permission to access to UDP/10000. but didn’t they connect through the TURN server? Stage 2 I decided to test the TURN server again. I blocke…

This file is not there in /etc/nginx/modules-enabled/
/etc/nginx/modules-enabled/60-jitsi-meet.conf

I have the latest version of jitsi.
How do I check if UDP/10000 connectivity is working fine?

[emrah]

@bhuvana

This file is not there in /etc/nginx/modules-enabled/

This file is not created in the new versions of jitsi.

@bhuvana

How do I check if UDP/10000 connectivity is working fine?

Tip: how to check UDP/10000 connectivity

On the server side Install ngrep apt-get install ngrep and start to watch the UDP/10000 traffic ngrep -q 'is accessable' udp port 10000 On the client side Install netcat apt-get install netcat and send a message to the server through UDP/10000 echo 'yes, it is accessable' | nc -u your.server.com 10000 Result If you can see the sent message on the server side, this means that there is no UDP/10000 connectivity problem between this client and the server.

[bhuvana]

nc -z -v -u meet.demo.live 10000

I ran this command in client instance and it is printing message
Connection to meet.demo.live 10000 port [udp/*] succeeded!

Anything else I can check at jitsi server end?

[emrah]

This is not the right way. Check the first post

[bhuvana]

Can you pls tell me which post should I check?
I am seeing this in jvb.log:

ConnectivityCheckClient.processSuccessResponse#648: Pair succeeded: 172.31.45.91:10000/udp/host → 103.66.80.223:6569/udp/prflx (stream-ef07ec16.RTP).
This means port 10000 is working…right?

Screensharing is not working at all…it only shows a white patch for participants when moderator starts screen share.

[emrah]

@bhuvana

Can you pls tell me which post should I check?

Tip: how to check UDP/10000 connectivity

On the server side Install ngrep apt-get install ngrep and start to watch the UDP/10000 traffic ngrep -q 'is accessable' udp port 10000 On the client side Install netcat apt-get install netcat and send a message to the server through UDP/10000 echo 'yes, it is accessable' | nc -u your.server.com 10000 Result If you can see the sent message on the server side, this means that there is no UDP/10000 connectivity problem between this client and the server.