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 firstname.lastname@example.org. 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 email@example.com. 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:  org.jitsi.jicofo.xmpp.FocusComponent.handleConferenceIq().401 Focus request for room: firstname.lastname@example.org
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