Conference only working P2P. JVB does not

Hi

I’m having problems getting conferences with more than 2 participants to work.
I already read some of the other posts here but I just can’t find the issue as everything is looking good for me.

Server:

  • No NAT, Public IP is directly set

Ports which are open:

  • 80 / 443
  • 4443 - tcp / 10000 - udp (Tested with and without TCP as fallback but both settings won’t work)

What works:

  • Accessing Jitsi Meet
  • Joining a conference with 2 participants (P2P) with mic and cam

What does not work:

  • Joining a conference with more than 2 participants (Switch to JVB). Everything just turns blank but all participants can see each other. So in principal it is working. Just no media.

I guess the problem is somewhere in the communication between Jicofo and the JVB.

If you need specific logs, url for testing or anything just ping. I will happily provide all the information you need.

Update:

jvb_1      | java.lang.Exception: Address discovery through STUN failed
jvb_1      |    at org.jitsi.videobridge.health.Health.doCheck(Health.java:217)
jvb_1      |    at org.jitsi.videobridge.health.Health.doRun(Health.java:495)
jvb_1      |    at org.jitsi.utils.concurrent.PeriodicRunnableWithObject.run(PeriodicRunnableWithObject.java:87)
jvb_1      |    at org.jitsi.utils.concurrent.RecurringRunnableExecutor.run(RecurringRunnableExecutor.java:216)
jvb_1      |    at org.jitsi.utils.concurrent.RecurringRunnableExecutor.runInThread(RecurringRunnableExecutor.java:292)
jvb_1      |    at org.jitsi.utils.concurrent.RecurringRunnableExecutor.access$000(RecurringRunnableExecutor.java:36)

Seems that somehow the address discovery via the Google STUN servers is not working.

Thanks in advance :slight_smile:

Can you try this one: https://github.com/jitsi/jitsi-videobridge/blob/master/debian/postinst#L102

Hi

Tried it from my local machine – Works
Tried it from our server – Does not work

I guess we have some firewall bogus in between.
5 minutes ago I tested the same installation configuration wise on a random cloud host and it worked instantly.

This is the test from our server. Response is timing out.

Resolved meet-jit-si-turnrelay.jitsi.net to 52.28.143.184:0
config.fBehaviorTest = false
config.fFilteringTest = false
config.timeoutSeconds = 0
config.uMaxAttempts = 0
config.addrServer = 52.28.143.184:443
socketconfig.addrLocal = 0.0.0.0:0
Sending message to 52.28.143.184:443
Continuing to wait for response...
Continuing to wait for response...
Continuing to wait for response...
Continuing to wait for response...
Continuing to wait for response...
Sending message to 52.28.143.184:443
Continuing to wait for response...
Continuing to wait for response...
Continuing to wait for response...
Continuing to wait for response...
Continuing to wait for response...
Binding test: fail

Thanks @damencho

It works now (with Google STUN and your STUN server).
As stated in the last post:
It was just firewall bogus on our side which denied communication between STUN servers and our side.