Video conference crashing within 30 seconds

hey there,

I am working on a jitsi install on my own physical sever. I’m running latest version of Debian, as well as Jitsi, jicofo, prosody.

As it stands I have a functional working server, and am able to video chat WITH audio and video. The problem I run into, is similar to the crashing every 30 seconds post. We will have a valid conference up and running, but within about 30 seconds we get an screen that says:

“something went wrong, we’re trying to fix this. Reconnecting in: xx seconds”

Ive googled quite extensively and have tried to ensure i’ve done most of the common fixes, like setting the local host, ensuring ports on firewall open etc, and I did follow the advanced configuration guide. My server is set up behind NAT.

Im “OK” with linux, but am fairly inexperienced with it. I am new to jitsi too. That being said, I’m not quite sure how to interpret the log files, and/or which log files I should be examining.

Any info I can provide, ill be happy to track down, but I would appreciate any ideas you would have in troubleshooting the issue.

this usually means that the videobridge does not work.

So it usually is that the port 10000 is blocked, check with:

(server)
sudo systemctl stop jitsi-videobridge2
nc -l 10000 -u
(workstation)
echo "123" | nc -u (your public address) 10000

if you don’t see 123 appear on your console, your provider is blocking port 10000 udp.
If port 10000 works, then usually it’s a NAT issue.

 cat /etc/jitsi/videobridge/sip-communicator.properties 
(...)
org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=xx.xx.xx.xx
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=yy.yy.yy.yy

replace xx… and yy… by private and public address of server.

If port 10000 works and you don’t have NAT, I don’t know. Maybe javabridge is down ? Check logs.

Thanks for your help, Im going to check on making sure port 10000 UDP is unblocked by my ISP, and double check the router is portforwarding it.

The sip-communicator.properties file, I had already added those lines.

Do I need to manually configure a turn/stun server? as it stands, unless this is automated in the set up, similar to nginx settings, we have not done anything with a stun/turn server. This is kind of a grey area for me, if I even need one.

you can look in the jvb.log file to see if the addresses you have set are really used.

a turn server is not necessary if all the clients have port 10000/UDP working.

So I grep’d my jvb.log for my public ip address, and it was indeed using them both. I removed them for privacy here, but this was what it output

2020-07-21 10:25:23.829 INFO: [33] org.ice4j.ice.harvest.StunMappingCandidateHar vester.discover: Discovered public address xxx.xxx.xxx.xxx:56489/udp from STUN se rver 129.213.15.174:443/udp using local address xxx.xxx.xxx.xxx:0/udp
2020-07-21 10:25:23.832 INFO: [28] org.ice4j.ice.harvest.MappingCandidateHarvest ers.initialize: Using org.ice4j.ice.harvest.StunMappingCandidateHarvester, face= /xxx.xxx.xxx.xxx, mask=/xxx.xxx.xxx.xxx
2020-07-21 13:30:09.675 INFO: [38] org.ice4j.ice.harvest.StunMappingCandidateHar vester.discover: Discovered public address xxx.xxx.xxx.xxx:33597/udp from STUN se rver 129.213.15.174:443/udp using local address xxx.xxx.xxx.xxx:0/udp
2020-07-21 13:30:09.678 INFO: [29] org.ice4j.ice.harvest.MappingCandidateHarvest ers.initialize: Using org.ice4j.ice.harvest.StunMappingCandidateHarvester, face= /xxx.xxx.xxx.xxx, mask=/xxx.xxx.xxx.xxx
2020-07-21 14:00:12.034 INFO: [38] org.ice4j.ice.harvest.StunMappingCandidateHar vester.discover: Discovered public address xxx.xxx.xxx.xxx:36867/udp from STUN se rver 129.213.15.174:443/udp using local address xxx.xxx.xxx.xxx:0/udp
2020-07-21 14:00:12.037 INFO: [28] org.ice4j.ice.harvest.MappingCandidateHarvest ers.initialize: Using org.ice4j.ice.harvest.StunMappingCandidateHarvester, face= /xxx.xxx.xxx.xxx, mask=/xxx.xxx.xxx.xxx
2020-07-21 15:14:34.158 INFO: [37] org.ice4j.ice.harvest.StunMappingCandidateHar vester.discover: Discovered public address xxx.xxx.xxx.xxx:57375/udp from STUN se rver 129.213.79.123:443/udp using local address xxx.xxx.xxx.xxx:0/udp
2020-07-21 15:14:34.160 INFO: [28] org.ice4j.ice.harvest.MappingCandidateHarvest ers.initialize: Using org.ice4j.ice.harvest.StunMappingCandidateHarvester, face= /xxx.xxx.xxx.xxx, mask=/xxx.xxx.xxx.xxx
2020-07-21 22:36:33.307 INFO: [29] org.ice4j.ice.harvest.MappingCandidateHarvest ers.initialize: Using org.ice4j.ice.harvest.MappingCandidateHarvester, face=/xxx.xxx.xxx.xxx, mask=/xxx.xxx.xxx.xxx

i also have the same problem but it only happens on phone devices except on computers. every times we start the meeting it’s always disconnected or crashed within 30 seconds so it’s hard for us to keep reconnecting to the meeting.