YouTrack Docker installation cannot authenticate with Hub after upgrade – "Token signature is invalid"
Hello,
After upgrading our YouTrack instance (Docker-based), we are completely locked out of the system.
On startup, YouTrack logs show this error:
Got invalid Hub token: Bearer [token]. Error: Token signature is malformed: Token signature is invalid
We are receiving a 401 Unauthorized error when trying to access YouTrack’s web interface. It appears that YouTrack cannot authenticate with Hub anymore.
Here is our setup:
- YouTrack is deployed via Docker (
jetbrains/youtrack:<version>) - We mounted volumes for
/dataand/conf - Everything worked fine before the upgrade
We have tried restarting both YouTrack and Hub containers
Nothing helped so far — the "Token signature is invalid" error remains, and we are completely locked out of YouTrack.
Can you please advise how to recover access to YouTrack or properly reestablish the connection to Hub?
Thank you,
Please sign in to leave a comment.
If you are facing a 401 error after an upgrade (it may also appear as “s: 401”, or “a: 401”, or "o: 401"), clearing the cookies and browser storage is likely to help.
If you've found this topic after facing 401 errors in YouTrack unrelated to the upgrade, please share your experience in and subscribe to JT-67169 by voting.
Hi Alan,
As we discussed in the support ticket, the error alone doesn't indicate an upgrade problem and might be resolved by clearing browser data. However, if it persists, please get back to the ticket with the requested info.
Currently facing this issue and have to revert because I don't know how many of our customers will have this issue. Can't really tell them all to delete their browser data for youtrack.
Julia Bernikova was there a solution found for this besides clearing browser data?
I ended up setting all timeouts in Auth Module → Common Settings to 5 min. and since it's night no one will use it for a while, making them login again. This worked for me at least.
Hi Jeroen, if you are also using Hub as a separate container, we recommend migrating to the built-in Hub service. As a result, you'll have only one container running, and the user management and authentication will be handled by YouTrack. This should help to avoid similar connection problems. If any problems persist, feel free to file a support ticket.
Hi Stanislav
We are using the built-in hub:
“A preconfigured Hub instance that is built into YouTrack and works immediately upon installation. This mode is currently enabled.”
We have had the same issue when upgrading to youtrack:2025.2.97298
The issue only appeared for admin users and a 401 error page appeared for them:
The stderr files did not have any errors, only the stdout file:
“Got invalid Hub token: Bearer ……..***. Error: Token signature is malformed: Token signature is invalid”
Clearning the cookies did not help, but clearing either the local storage/or session storage on Chrome fixed the issue.
At least for us, regular users were unaffected.