No more 2 participant in Jitsi meet

i have setup Jitsi Meet server on MS Azur vps following the simple setup described in download section of Jitsi org, i opened port 443, 4443, udp 10000-20000 and succesfully setup Let’s encrypt certificate with the provided script
Ly issue is apparently the same as many other newbies like me ! I can’t have more than 2 users in visio conference. When a third participant is joining, it ends in a black screen/no audio for all three participants.
Looking at Jicofo log i found this Severe error at end of this post.

So i added Adding public/private address (despite i can’t see this server behind any nat ):<><>

in /etc/jitsi/videobridge/ but result is worst, one partcipant is kicking out the other when joining.

Any help would be appreciated.

Thanks !
Jicofo 2020-03-28 15:25:46.293 SEVERE: [48] org.jitsi.jicofo.AbstractChannelAllocator.log() Failed to allocate channels using bridge: jitsi-videobridge.confserv1.openm$ Failed to allocate colibri channels - bad request: <iq to='$
at org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl.maybeThrowOperationFailed(
at org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl.createColibriChannels(
at org.jitsi.protocol.xmpp.colibri.ColibriConference.createColibriChannels(
at org.jitsi.jicofo.ParticipantChannelAllocator.doAllocateChannels(
at org.jitsi.jicofo.AbstractChannelAllocator.allocateChannels(
at org.jitsi.jicofo.AbstractChannelAllocator.doRun(
at java.util.concurrent.Executors$
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
at java.util.concurrent.ScheduledThreadPoolExecutor$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
Caused by: java.lang.Exception: <iq to=‘’ from=‘’ id=‘UIE0r-26036’ type$
… 14 more
Jicofo 2020-03-28 15:25:46.299 SEVERE: [48] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() One of our bridges failed:

1 Like

How did you enter the ip address in jvb config? Was it <> or, only the second one is valid.

1 Like

Hello Damencho, indeed i removed the <> and it s all good now everything works on a small 1cpu/1024 mo Azur vps. Big thanks to you for fast support, and to all the Team for this very good project.
Michael Benarouch