Adding new JVB to already installed Jitsi-server bundle

I have already installed Jitsi-Server, which have it’s own JVB.
Now I am trying to add new JVB vm, I am trying MUC approach.

Info I’ve got from forum so far is, Jitsi-server’s Jicofo (sip-communicator.prop) needs this line,

(New JVB VM doesn’t have SSL cert or domain name)
Now newly installed JVB’s config(/etc/jitsi/videobridge/config)




newly installed JVB’s config/etc/jitsi/videobridge/*


JVB 2019-08-22 11:53:54.366 SEVERE: [34] org.jitsi.xmpp.mucclient.MucClientManager.log() Failed to initialize and start a MucClient:
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$
JVB 2019-08-22 11:53:58.972 SEVERE: [37] conflict,, port:5347
org.xmpp.component.ComponentException: conflict
at org.jivesoftware.whack.ExternalComponent.connect(
at org.jivesoftware.whack.ExternalComponentManager.addComponent(
at org.jivesoftware.whack.ExternalComponentManager.addComponent(
at org.jitsi.retry.RetryStrategy$
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$
JVB 2019-08-22 11:54:03.977 SEVERE: [37] conflict,, port:5347

What am I missing?


The bridge has two different ways to connect to an XMPP server – as a component and as a user. To use multiple bridges with one jicofo, you need the MUC functionality, which in turn requires the XMPP user connection.

The errors you see are from the XMPP component connection, which fails because another component (the other bridge) is already connected. You can ignore the errors, or disable the XMPP component mode by removing the “xmpp” api from /etc/jitsi/videobridge/config.

The configuration of the XMPP user connection is in the properties file (the “xmpp” api in “config” is unrelated). As far as I can see your configuration is correct. You should see something like this:
JVB 2019-08-22 08:10:35.482 INFO: [45] org.jitsi.xmpp.mucclient.MucClient.log() [MucClient id=jvb2] connected
JVB 2019-08-22 08:10:35.550 INFO: [45] org.jitsi.xmpp.mucclient.MucClient.log() Joined MUC:

Hope this helps,


Hi @Boris_Grozev , now JVB is connected to MUC, but now only thing remained is that org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized error,
I checked in prosody,
Aug 23 06:18:05 warn Component not connected, bouncing error for:
I think JVB is not being authenticated. The username/password we have provided in config, do we have to update them in prosody somewhere?

I checked Can not invite participant -- no bridge available, also have same problem, but it’s last question is unanswered, I will update both threads once issue solves.

Thanks in advance.


You need to create an account on prosody for the second bridge. You
can do so with prosodyctl register USER DOMAIN PASSWORD.


Yes I did create user recently,
Both JVB able to join room,
I did face one problem though when both JVB are conneced to brewery room, jicofo was not able to, it was trying to create brewery room and failing with error forbidden auth.
But I stopped both JVB and then restarted jicofo, now jicofo is able to join room, I again started JVBs.

But still jicofo is throwing error and user’s not able to join conference
Jicofo 2019-08-23 11:48:59.583 SEVERE: [37] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Can not invite participant – no bridge available.
Jicofo 2019-08-23 11:48:59.583 SEVERE: [37] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Can not invite participant – no bridge available.