Strophe: BOSH-Connection failed: host-unknown


#1

Hi,
I’m setting up Jitsi on Ubuntu Server 18.04 LTS. I followed secure domain guide with additional LDAP authentication.
Now I’m unable to create the conference, as every time i try to do it, jitsi asks for login and password. I enter correct credentials for AD user, and get “Oops! Something went wrong and we couldn’t connect to the conference: connection.otherError” popup (it does authenticate against the domain, if i put wrong password it just says wrong username or password). There are also somewhat more informative messages in browser console:>

[JitsiMeetJS.js] <getGlobalOnErrorHandler>: UnhandledError: null Script: null Line: null Column: null StackTrace: Error: "Strophe: BOSH-Connection failed: host-unknown"

    * log strophe.util.js:89
    * error strophe.js:2083
    * _connect_cb strophe.js:5291
    * _connect_cb strophe.js:3910
    * _onRequestStateChange strophe.js:5559

    [Logger.js:124:12](webpack://JitsiMeetJS/jitsi-meet-logger/lib/Logger.js)

    * i Logger.js:124
    * getGlobalOnErrorHandler JitsiMeetJS.js:547
    * onerror middleware.js:100
    * callErrorHandler GlobalOnErrorHandler.js:61
    * log strophe.util.js:89
    * error strophe.js:2083
    * _connect_cb strophe.js:5291
    * _connect_cb strophe.js:3910
    * _onRequestStateChange strophe.js:5559

followed by multiple

[conference.js] <value>: CONFERENCE FAILED: conference.authenticationRequired [Logger.js:124](webpack://node_modules/jitsi-meet-logger/lib/Logger.js

  • o Logger.js:124
  • value conference.js:331
  • emit events.js:81
  • emit events.js:78
  • _allocateConferenceFocusError moderator.js:440
  • allocateConferenceFocus moderator.js:375
  • s strophe.js:3388
  • run strophe.js:2556
  • _dataRecv strophe.js:3822
  • forEachChild strophe.js:1522
  • _dataRecv strophe.js:3810
  • _onRequestStateChange strophe.js:5559

and some warnings.
I checked log files and syslog for information, but there was nothing i could use - a few warnings, which you can see below:
from /etc/var/log/prosody/prosody.log

Incoming Jabber component connection
Mar 07 16:04:40 focus.mydomain .com:component info External component successfully authenticated
Mar 07 16:04:41 some_text info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Mar 07 16:04:41 some_text info Authenticated as focus@auth.mydomain .com
Mar 07 16:04:41 jitsi-videobridge.mydomain .com:component warn Component not connected, bouncing error for:
Mar 07 16:04:43 some_text info Incoming Jabber component connection
Mar 07 16:04:43 jitsi-videobridge.mydomain .com:component info External component successfully authenticated
Mar 07 16:04:48 mod_bosh info New BOSH session, assigned it sid ‘some_text’
Mar 07 16:04:48 some_text info Authenticated as some_text@guest.mydomain .com
Mar 07 16:20:23 somet_text info BOSH client disconnected

from /etc/var/log/jitsi/jicofo.log

Jicofo 2019-03-07 16:03:50.716 WARNING: [28] org.jitsi.jicofo.JitsiMeetServices.nodeNoLongerAvailable().245 MUC component went offline: conference.mydomain .com
Jicofo 2019-03-07 16:04:26.096 WARNING: [42] org.jitsi.jicofo.BridgeSelector.addJvbAddress().227 No pub-sub node mapped for jitsi-videobridge.mydomain .com
Jicofo 2019-03-07 16:04:36.200 WARNING: [28] org.jivesoftware.smack.AbstractXMPPConnection.callConnectionClosedOnErrorListener() Connection XMPPTCPConnection[focus@auth.mydomain.com/focus23165667807781] (0) closed with error
Jicofo 2019-03-07 16:04:36.209 WARNING: [28] org.jitsi.jicofo.JitsiMeetServices.nodeNoLongerAvailable().245 MUC component went offline: conference.mydomain .com
Jicofo 2019-03-07 16:04:49.243 WARNING: [46] org.jitsi.xmpp.component.ComponentBase.verifyProcessingTime().540 PROCESSING TIME LIMIT EXCEEDED - it took 291ms to process:
Jicofo 2019-03-07 16:05:12.045 WARNING: [42] org.jitsi.jicofo.BridgeSelector.addJvbAddress().227 No pub-sub node mapped for jitsi-videobridge.mydomain .com

from /etc/var/log/jitsi/jvb.log

JVB 2019-03-07 16:03:57.510 WARNING: [16] org.jitsi.videobridge.IceUdpTransportManager.log() Failed to initialize TCP harvester on port 443: java.net.BindException: Address already in use. Retrying on port 4443.
JVB 2019-03-07 16:04:43.062 WARNING: [13] org.jitsi.videobridge.EndpointMessageTransport.log() SCTP connection with some_text not ready yet.
JVB 2019-03-07 16:04:43.063 WARNING: [13] org.jitsi.videobridge.EndpointMessageTransport.log() No available transport channel, can’t send a message
JVB 2019-03-07 16:04:43.194 WARNING: [16] org.jitsi.videobridge.IceUdpTransportManager.log() Failed to initialize TCP harvester on port 443: java.net.BindException: Address already in use. Retrying on port 4443.
JVB 2019-03-07 16:04:53.539 WARNING: [13] org.jitsi.videobridge.EndpointMessageTransport.log() SCTP connection with some_text not ready yet.
JVB 2019-03-07 16:04:53.540 WARNING: [13] org.jitsi.videobridge.EndpointMessageTransport.log() No available transport channel, can’t send a message

the last two entries of this one were repeating until i closed the page.

I honestly have no idea what is wrong, I spent last four hours trying to fix this.
I installed jitsi using the recommended approach - from repository, then i did what is written in tutorials I linked ( I installed prosody modules from repositories instead of pulling them from googlecode)
I’m still using self-signed certs, since this is a test/pre-preoduction enviroment i don’t want to put on the internet.

Has anyone ever had similar issue or does anyone know how to handle it?

P.S. i had to put spaces before .com in a few places since the editor was interpreting parts of logs as links


#2

This one is strange and is the first time I see it. Which version of prosody are you using? Did you check are there any errors in prosody.err?

If you are using prosody0.11 there is a small change to be made to the config:
storage = "null" change to storage = "none" and restart prosody.


#3

There are no errors in prosody.err. I’ll chck prosody version when i’ll be able to - today i don’t have access to that server, but i think it was 0.10.


#4

I’m using prosody version 0.10
I’ve double checked posody.err, too. Last error logged is

Mar 07 13:51:04 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

But i have already fixed that with

consider_bosh_secure = true
bosh_ports = {
{
port=5280;
path=“http-bind”;
},
{
port=5281;
path=“http-bind”;
ssl={
key = “/etc/prosody/certs/mydomain.com.key”;
certificate = “/etc/prosody/certs/mydomain.com.crt”;
}
}
}

So it should be fine - this error got logged two hours before I encountered the error described in the first post.