CentOS7, EC2, Docker setup: "There are no operational briges"

JonoSax · March 22, 2023, 3:29am

Hi all,

I have setup Jitsi Meet from the docker image on an EC2 instance. I can connect to the GUI and start a meeting on the public url I have specified, but once someone joins the connection fails with:

The WARNING log:

BridgeSelectir.selectBridge#179: There are no operational bridges.

The SEVERE log:

ParticipantInviteRunnable.doRun#218: Can not invite participant, no bridge available

From what I can tell the problem is pretty obvious, no video bridge so the streams cant be joined together. I assume something wrong with JVB? However Im confused because this is from the Jitsi Meet docker so I thought it would be alg to go?

Anyone have advice or experience solving this problem?

Thanks

saghul · March 22, 2023, 7:42am

Check the JVB logs, is it connected to Prosody?

JonoSax · March 26, 2023, 10:59pm

I can see in the Prosody logs:

warn A module has been configured that triggers external events
warn Implement this lib to trigger external events.

Im not sure what this actually means in the context of connecting prosody to jvb?

damencho · March 27, 2023, 4:02am

This is an old hook used for customizations to send speakestats to external service

github.com

jitsi/jitsi-meet/blob/1c04a41081269a2a043b1b7b391a6cfda4391c23/resources/prosody-plugins/ext_events.lib.lua#L44


      
          -- Event that speaker stats for a conference are available
          -- this is a table where key is the jid and the value is a table:
          --{
          --  totalDominantSpeakerTime
          --  nick
          --  displayName
          --}
          -- This trigger is left unimplemented. The implementation is expected
          -- to be specific to the deployment.
          local function speaker_stats(room, speakerStats)
              module:log(
                  "warn",
                  "A module has been configured that triggers external events."
              )
              module:log("warn", "Implement this lib to trigger external events.")
          end
          
          
local ext_events = {
              missed = missed,
              invite = invite,
              cancel = cancel,

bernerh · May 24, 2023, 2:59pm

Hi, I get the same problem after upgrading to docker-jitsi-meet-stable-8615 from docker-jitsi-meet-stable-8319.

saghul · May 25, 2023, 8:23am

Check the logs in the JVB container.

bernerh · May 30, 2023, 10:07am

Looks like the JVB Container has a problem with finding the default TURN Server.
We are in a “corporate network” therefore the firewall blocks the access to the default servers.
The old JVB Version worked. It looks like it works after setting JVB_DISABLE_STUN=true but first I have to test it with more than myself in a video conference