Error verifying token err:not-allowed, reason:Invalid signature

when I tried to write the link of jwt and work on it, I get a massage that’s the authentication failed with error in prosody logs However, the app_id and app_Secret are the same as I wrote in the installation

Dec 21 20:40:36 c2s558f8fc2a680 info Client disconnected: connection closed
Dec 21 20:40:41 c2s558f8fc23880 info Client connected
Dec 21 20:40:41 c2s558f8fc23880 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Dec 21 20:40:41 c2s558f8fc23880 info Client disconnected: connection closed
Dec 21 20:40:46 mod_bosh info New BOSH session, assigned it sid ‘12d6f65d-8794-4740-a686-0c0b04719c37’
Dec 21 20:40:46 general warn Error verifying token err:not-allowed, reason:Invalid signature
Dec 21 20:40:46 c2s558f8f8e27d0 info Client connected
Dec 21 20:40:46 c2s558f8f8e27d0 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Dec 21 20:40:46 c2s558f8f8e27d0 info Client disconnected: connection closed
Dec 21 20:40:51 c2s558f8fb601a0 info Client connected
Dec 21 20:40:51 c2s558f8fb601a0 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)

please, help

The error is written in the console: invalid nbf and exp values from the provided token. Make sure those are numbers.

But jwt.io gave it to me as a valid signature

It gives me the same error even if the link has no _ or -

It validates the signature not the content of it.

You may try to create the Jitsi token in jitok

1 Like

Thank you so much Emrah this link make it right and it worked now :slight_smile:

1 Like