Cannot login to jitsi-meet - "Strophe: Server did not offer a supported authentication mechanism"


#1

Hi all,
My jitsi server worked fine and after an update I can no longer login. I cannot pnpoint which update as we don’t use the service every day and updates are done regularly but it stopped working at some point.

When I login now to jjtsi-meet which requires the host to authenticate to start a conference, I get an immediate :Oops something went wrong" error message with the non-nondescript message “connection:otherError”.

On the javascript console I see the following "“Strophe: Server did not offer a supported authentication mechanism”.

I have looked at the log files and there are no error message which appear in jicofo.log, jvb.log, prosody.log nor nginx error.log. I have disabled IPV6 n case that was a problem, and updated my ssl certs used by prosody but no luck.

Any ideas where to look?

thanks


#2

Check whether you have c2s_require_encryption = false(as in here https://github.com/jitsi/jitsi-meet/blob/master/doc/debian/jitsi-meet-prosody/prosody.cfg.lua-jvb.example#L26) for the virtual hosts you are using, if adding those does not help you can try adding consider_bosh_secure = true; to the general prosody config.


#3

The entry “c2s_require_encryption = false” was already there. I added
“consider_bosh_secure = true”

I now get a different error “conference:connection.GET_SESSION_ID_ERROR”. Still nothing, as far as I can tell in the server logs. On the browser console I get

[modules/UI/authentication/AuthHandler.js] <i/</n</<>: authenticateAndUpgradeRole failed
authenticationError: “not-authorized”
​message: “not authorized user domain”

So I guess its got something to do with authentication, the original problem as well but not sure why. I can login with the userid via a xmpp client.

thanks for the help. I am completely out of ideas (


#4

Which version are you running? We discovered these days a problem with authentication which was fixed today. https://github.com/jitsi/jitsi-meet/commit/675eea7b99095b9971a24bc403d48521b58bca6e
This update is available in latest unstable packages.
You have this in your jicofo config: org.jitsi.jicofo.auth.URL=XMPP:jitsi-meet.example.com?
And when authenticating you are using user@jitsi-meet.example.com as username?


#5

I am on Ubuntu 16.04. According to apt I have the following versions installed.

jicofo/stable 1.0-417-1 i386
JItsi Meet COnference FOcus

jigasi/stable 1.0-175 i386
Jitsi Gateway for SIP

jitsi/stable 2.10.5550-1 amd64
VoIP and Instant Messaging client

I tried addin the line " org.jitsi.jicofo.auth.URL=XMPP:myserver.com" to /etc/jitsi/jicofo/config but it didn’t seem to have an effect.
I am logging in as user@domain.com -> I can login fine with an xmpp client. I cannot find the middleware.js file to edit as per the github page.


#6

So you are on stable. The value “org.jitsi.jicofo.auth.URL=XMPP:myserver.com” should go in /etc/jitsi/jicofo/sip-communicator.properties as described here: https://github.com/jitsi/jicofo#secure-domain
“If you have Jicofo installed from the Debian package this should go directly to /etc/jitsi/jicofo/sip-communicator.properties file:”

I don’t understand this, what do you want to edit there?


#7

Ah ok - thanks. The entry is already in the file. The only cusstom entry I made to try and solve this problem, i.e. to the config files that had been working before, was to add "component_interface = “127.0.0.1"” to the prosody config file.

In an attempt to fix the problem I disabled IPv6 as the log files showed services attempting to connect to the local ipv6 address. Disabling IPv6 in sysctl.conf cause prosody not to start as it tired to connect to the ::1 ipv6 localhost interface which now no longer exists. Not sure if this is relevant. I have removed the entry and it still give the same error.

The middleware.js file as per the github link https://github.com/jitsi/jitsi-meet/commit/675eea7b99095b9971a24bc403d48521b58bca6e


#8

This is the source code, you need to checkout source and compile it. Those files are not available in the binary debian package.


#9

Ok I have reinstalled everything using stable on Ubuntu 18.04 and before enabling secure domains everything works. Once secure domains are enabled I get prompted for the host username and password but on login I just get kicked back to the “Waiting for host” dialog.

I assume the unstable patch fixes this?


#10

Exactly, this is the fix.


#11

I have a question, when is the fix going to available in the Debian/Ubuntu stable package?

I was brought to the project by this tutorial : https://www.howtoforge.com/tutorial/how-to-create-your-own-video-conference-using-jitsi-meet-on-ubuntu-1804/ , which makes it very easy to install, but I am getting nowhere with the secure domain configuration from https://github.com/jitsi/jicofo#secure-domain

I am on Ubuntu 18.04.


#12

I just updated it. The fix is now in stable.