Host-unknown for videobridge [SOLVED]



I have a problem with videobridge that posts these logs.
Is it supposed to connect to the xmpp server in ssl ? Otherwise I don’t understand why it complains

export JVB_HOME=/usr/local/jitsi-videobridge
mvn compile exec:exec -Dexec.executable=java -Dexec.args="-cp %classpath org.jitsi.videobridge.Main –domain=“” --host=“” --port=“5347” --secret=“YOURSECRET1” -Djava.library.path=$JVB_HOME/lib/native/linux-64 -Djava.util.logging.config.file=$JVB_HOME/lib/"

Nov 04, 2018 3:19:56 PM error
SEVERE: host-unknown,, port:5347
org.xmpp.component.ComponentException: host-unknown
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$

However I’m able to join it

telnet 5347
Connected to
Escape character is ‘^]’.
telnet> quit
Connection closed.

But it doesn’t handle ssl

openssl s_client -connect
4420539820704:error:1400410B:SSL routines:CONNECT_CR_SRVR_HELLO:wrong version number:/usr/src/lib/libssl/ssl_pkt.c:386:

no peer certificate available

No client certificate CA names sent

SSL handshake has read 5 bytes and written 0 bytes

New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Protocol : TLSv1.2
Cipher : 0000
Start Time: 1541341371
Timeout : 7200 (sec)
Verify return code: 0 (ok)

I followed the prosody configuration

VirtualHost “
authentication = “anonymous”
ssl = {
key = “/etc/prosody/certs/”;
certificate = “/etc/prosody/certs/xmpp.mydomain.org_chained.crt”;
cafile = “/etc/ssl/certs/CA_Root_Lets_Encrypt.crt”;
modules_enabled = {
c2s_require_encryption = false

VirtualHost “
ssl = {
key = “/etc/prosody/certs/”;
certificate = “/etc/prosody/certs/xmpp.mydomain.org_chained.crt”;
cafile = “/etc/ssl/certs/CA_Root_Lets_Encrypt.crt”;
authentication = “internal_plain”

Component “” “muc”
Component “
component_secret = “YOURSECRET1”
Component “
component_secret = “YOURSECRET2”


This means, jvb connects to the server, but the server replies that the hostname that jvb tries to use is not configured/unknown. The domain is passed with param --domain.


I checked the logs in prosody and indeed it looks like there is a problem

Nov 05 00:50:42 jcp6f99d04db80 info Incoming Jabber component connection
Nov 05 00:50:42 mod_component info Disconnecting component, stream:error is: stream:errorjitsi-videobridge does not match any configured external components</stream:error>
Nov 05 00:50:42 jcp6f99d04db80 info component disconnected: nil (false)
Nov 05 00:50:42 socket debug server.lua: closed client handler and removed socket from list

I don’t know where it found the string “jitsi-videobridge” because it’s nowhere in my configuration, it’s missing the domain part.

Also I read one of the message you participated

Shoud I create the file /etc/jitsi/videobridge/config
How should it look like ?

Thank You


This file is created during installation, and is used by the init.d script. I suppose you are running from source, so you don’t need that.
You are passing --domain=“” to jvb, this means you need to have configured in prosody:

Component ""
    component_secret = "----"

Have you configured this in prosody?


Thank you for your answer damencho.
Yes I run it from source.

I did configure this stanza in my prosody.cfg.lua, I had posted it in my first message and rechecked right now

Component “
component_secret = “YOURSECRET1”

But the message found in prosody.debug

jitsi-videobridge does not match any configured external components

Do you know if I can run a basic test to validate or invalidate the prosody part ?

Do you also know how does it decides to connect to, what if I wanted the name to be” ?
Because I don’t feel it’s in the mvn compile command.


There is a param subdomain which controls that part.

Check whether your config is included in prosody config. The versions of prosody coming from the ubuntu repo include all files from conf.d folder, but if you use prosody coming from prosody’s repo, their default config do not use that scheme.


So I finally found the root cause of this issue !
In my command line I had -domain instead of --domain (two dashes), hence the domain wasn’t taken into account.

Maybe it would be nice to have an error message for people who have their head in the clouds.

Thank you for your patience