Authentication failed, JWT Token no more working since May 2020

Hi, I encountered with Login box when entered the room using valid token when I upgraded the Jitsi. I just checked the April 2020 installation and JWT authentication working fine there with same token. What Token changes have been made after April 2020? Why the old valid token is not authenticating? Probably the date I checked in the logs were 04-04-2020 where tokens were working perfectly. @damencho

Check in the networks tab about the error returned. Can you see it, what it is?

Nope

aaah…i tried finding issues in logs as well…I am not getting any hint…
Once there was an issue “failed to connect/login: the following addresses failed: ‘localhost:5222’ failed because: localhost/127.0.0.1 exception: java.net.connectexception: connection refused (connection refused)” got resolved i believe restarting prosody jicofo jvb2.

You need to check Network tab and see the xmpp response message for the authentication failure.

token required
token does not reach prosody
Check prosody logs, is your nginx settings ok?

using Apache…all well with it.

Preformatted textSep 04 00:44:58 jcp5602d9fc3630 info Incoming Jabber component connection
Sep 04 00:44:58 focus.teleconf.yogdiagnostics.com:component info External component successfully authenticated
Sep 04 00:58:26 mod_bosh info New BOSH session, assigned it sid ‘7ef43ca1-c191-4631-8a1b-823d1a08fffb’
Sep 04 00:58:26 general warn Error verifying token err:not-allowed, reason:token required
Sep 04 00:58:59 bosh7ef43ca1-c191-4631-8a1b-823d1a08fffb info BOSH client disconnected
Sep 04 00:59:16 mod_bosh info New BOSH session, assigned it sid ‘52e034eb-9787-473c-8c99-c454520941f6’
Sep 04 00:59:17 general warn Error verifying token err:not-allowed, reason:token required
Sep 04 00:59:21 bosh52e034eb-9787-473c-8c99-c454520941f6 info BOSH client disconnected
Sep 04 01:12:42 mod_bosh info New BOSH session, assigned it sid ‘28ad8ed5-39d2-4edf-9ee0-bf27b40364b4’
Sep 04 01:12:43 general warn Error verifying token err:not-allowed, reason:token required
Sep 04 01:24:11 mod_bosh info New BOSH session, assigned it sid ‘7162c964-21fa-4472-af6c-c15a5cc1f49e’
Sep 04 01:24:12 general warn Error verifying token err:not-allowed, reason:token required
Sep 04 01:24:37 bosh7162c964-21fa-4472-af6c-c15a5cc1f49e info BOSH client disconnected
Sep 04 01:25:40 mod_bosh info Client tried to use sid ‘28ad8ed5-39d2-4edf-9ee0-bf27b40364b4’ which we don’t know about

Maybe your apache is not passing the jwt param when proxing the http-bind requests, check that I have 0 experience with apache.

Ok. There’s an image in a repository of month April,2020…I am upgrading all except Apache Server and modules & common files. Let me check if Apache is really a root cause for it.

Ok. The problem is not with apache because apache is not upgraded in image of April 2020. Now again on upgrading the jitsi getting same issue
log saying:

Logs attached.
jicofo.log (104.1 KB) prosody.log (22.2 KB)

Check logs for dated 4th Sept 2020 02:00 AM onwards @damencho