Get_session_id_error

Hey,

I tried to password protect creation of rooms on my jitsi installation today following secure-domain guide.

After opening a new room and entering my host credentials jitsi tells me “we couldn’t connect to the conference: connection.GET_SESSION_ID_ERROR”

It is exactly the same error message described here.

Here is an excerpt from the prosody.log (I put a space between example and .com so it does not appear as a link in this post)

Apr 07 14:47:51 conference.jitsi.example. com:muc_domain_mapper warn Session filters applied
Apr 07 14:47:51 mod_bosh info New BOSH session, assigned it sid ‘a793aaca-6863-4289-8740-33675eb1762b’
Apr 07 14:47:51 bosha793aaca-6863-4289-8740-33675eb1762b info Authenticated as af397d9b-ed08-4a09-ade9-6c9861682806@guest.jitsi.example. com
Apr 07 14:48:54 conference.jitsi.example. com:muc_domain_mapper warn Session filters applied
Apr 07 14:48:54 mod_bosh info New BOSH session, assigned it sid ‘84b2313d-437f-4573-a59e-7f72c4a3961f’
Apr 07 14:48:54 bosh84b2313d-437f-4573-a59e-7f72c4a3961f info Authenticated as myaccount@jitsi.example. com
Apr 07 14:48:55 bosh84b2313d-437f-4573-a59e-7f72c4a3961f info BOSH client disconnected
Apr 07 14:49:03 bosha793aaca-6863-4289-8740-33675eb1762b info BOSH client disconnected

I think the last lines are intersting. Authentification seems to work, however after authentification I get the error message and it tells me BOSH client disconnected. So I guess the problem is not with prosody?

The Jicofo.log only gives lines of the form

Jicofo 2020-04-07 15:10:14.924 INFO: [150] org.jitsi.jicofo.xmpp.FocusComponent.handleConferenceIq().401 Focus request for room: test5@conference.jitsi.example.com

I don’t really see any errors in those two documents.

However prosody.err contains errors of the form

Apr 07 14:42:27 portmanager     error   Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

I’m not sure if this is related. Can anyone give me some pointers how to debug the problem?

Many thanks in advance

Turns out everything works, when I use a clean Image of Ubuntu 18.04 with only nginx and jitsi-meet. I guess I made a mistake in one of the configuration files, when I tried this the first time.

1 Like

I’m having this exact same issue after trying to change the domain of my installation.
I eventually did a purge and reinstall, but still having the same problems

While I’m sure a clean install of Ubuntu and Jitsi will solve the problem I’d like to understand what the problem is with my configuration.

The only error I can see if in the prosody.err
May 20 04:53:04 guest.jitsi-example.com:tls error Error creating context for c2s: No key present in SSL/TLS configuration for guest.jitsi-example.com
May 20 04:53:04 guest.jitsi-example. com:tls error Error creating contexts for s2sin: No key present in SSL/TLS configuration for guest.jitsi-example. com
May 20 04:53:04 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
May 20 04:53:04 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

Spent more hours trying to solve this on my own without any luck
@damencho, any suggestions?