mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-05-07 12:34:03 -05:00
[GH-ISSUE #6610] Logged out from every single client after last update #15270
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/vaultwarden#15270
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @xJayMorex on GitHub (Dec 28, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6610
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
v1.35.0
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx-proxy-manager v2.13.4
Host/Server Operating System
Linux
Operating System Version
Devuan 6 VM running on Proxmox VE 9.1.2
Clients
Android, Browser Extension
Client Version
Chrome extension v2025.12.0, Android v2025.12.0
Steps To Reproduce
sha256:a66735efe15d3a7ea63b5b3fe6913058756771349f6056e1be1ab7b4ef244b21)Expected Result
Not logged out.
Actual Result
Logged out.
Logs
Screenshots or Videos
No response
Additional Context
No response
@stefan0xC commented on GitHub (Dec 28, 2025):
From what version did you update? Can you login again?
@xJayMorex commented on GitHub (Dec 28, 2025):
Update was done by
nickfedor/watchtowerfrom image v1.34.384fd8a47f58dto image v1.35.0a66735efe15d(always usinglatesttag).I am able to log back in without any issues.
docker-compose.yml
@stijneikelboom commented on GitHub (Dec 28, 2025):
I have the same experience after updating from
1.34.3to1.35.0.The MacOS app and Safari extension (
2025.12.0) immediately showed a generic sync error and logged out right after. The iOS app (2025.12.0) kept working, but a sync or edit operation triggered the attached error.I have not been able to collect more diagnostics yet, but can confirm logging back in resolves all issues. Has anything been changed with respect to the
refresh_tokenin1.35.0?@bo0ohXae commented on GitHub (Dec 28, 2025):
Same thing happened to me, BUT I can not log back in anymore! Have also downgraded to 1.34.3 and that one doesn't work either. Will try restoring the db I guess.
@Greite commented on GitHub (Dec 28, 2025):
I have the same problem here. I've been able to log back on web, and chrome extension, but can't log back on the iPhone app. Just a generic error message pops up
@bo0ohXae commented on GitHub (Dec 28, 2025):
Ahh, never mind! I could log back in once I found the typo that my browser decided to auto-complete into my email address.. lol
@slanglade commented on GitHub (Dec 28, 2025):
Same here : after upgrading from v1.34.3 to 1.35.0, all token are considered as faulty
[2025-12-28 15:48:17.665][request][INFO] POST /identity/connect/token
[2025-12-28 15:48:17.665][vaultwarden::auth][ERROR] Token is invalid
[2025-12-28 15:48:17.665][vaultwarden::api::identity][ERROR] Unable to refresh login credentials: Impossible to read refresh_token: Token is invalid
This happens for every account existing on the local server.
@Greite commented on GitHub (Dec 28, 2025):
I cleared all my sessions from Settings → Account, then logged back in and it worked.
The issue with the iPhone app not logging in was caused by CrowdSec: my device had been banned after several 401 login attempts.
@LilSlippinJimmy commented on GitHub (Dec 28, 2025):
Same here, logged out of all devices for myself and other users.
@BlackDex commented on GitHub (Dec 28, 2025):
I have not experienced this my self at all.
Any logs during these logouts might help, but it will be hard to reproduce i think.
@stijneikelboom commented on GitHub (Dec 28, 2025):
@BlackDex Adding to the log lines already provided by @slanglade, I see multiple sequences of these log lines in my Vaultwarden log file:
And the nginx access logs reflect just the two calls to
/identity/connect/tokenand/api/config:Downgrading from
1.35.0to1.34.3produces similar issues, where logging out and in is needed to be able to properly sync again.@jeroenhabets commented on GitHub (Dec 28, 2025):
FWIW: My daughter had to actually logout using the menus on her iPhone 16, as just closing and restarting Bitwarden and logging in using Face-ID was not enough. Then it worked again, though.
@BlackDex commented on GitHub (Dec 28, 2025):
I wonder if something is changed in the refresh tokens which could explain this. But then still strange i haven't noticed this my self.
And i can't remember other people who where using testing mentioned this either.
@hofbi commented on GitHub (Dec 28, 2025):
I also noticed that all devices were logged out. Additionally, I noticed that all client settings on Android devices were gone and back to the default values. Browser extension settings remained unchanged. Not sure if this is related.
@pamperer562580892423 commented on GitHub (Dec 28, 2025):
@BlackDex:
It was mentioned before: https://github.com/dani-garcia/vaultwarden/issues/6561#issuecomment-3663103571
@BlackDex commented on GitHub (Dec 28, 2025):
Overlooked that, but unfortunately one report. But Maybe it helps narrow down the change.
@luisbandalap commented on GitHub (Dec 28, 2025):
I was the one mentioning it but didn't raise a ticket as i didn't know it was expected or not.
Switched from :testing to :latest and I got unable to enter to my vaults from any app (web, android, web extension) with this showing on logs:
returning from :latest to :testing allows me to log in again
@BlackDex @stefan0xC :latest and :testing should be the same at this point, shouldn't they?
@stefan0xC commented on GitHub (Dec 29, 2025):
Make sure you pull the latest image before switching and that it's image digest corresponds to the digest for your platform (e.g. on GHCR or Docker Hub).
Almost but there has been a new commit since the latest release.
@luisbandalap commented on GitHub (Dec 29, 2025):
It was my fault, docker compose used an old :latest tag. after pulling it now i can log again. thanks.
@mzy2240 commented on GitHub (Dec 29, 2025):
Im having the same issue, downgrading to 1.34.3 still face the same issue.
@ma-04 commented on GitHub (Dec 29, 2025):
Faced the same issue. For now, logging back in solved the issue.
@irfanhakim-as commented on GitHub (Dec 29, 2025):
Also facing this issue after upgrading from
1.34.3-alpineto1.35.0-alpine. All previously logged in accounts/clients need to be logged out and log back in to actually be connected/synced. The main issue I'm seeing is that, on mobile clients at least, there isn't any indication that anything is wrong and that they have to manually log out and log back in.@pamperer562580892423 commented on GitHub (Dec 29, 2025):
@mzy2240 : Does that mean you logged back in and are constantly getting logged out now?
@lxw314 commented on GitHub (Dec 29, 2025):
I'm facing the same problem after upgrading from 1.34.3 to 1.35.0. Because I have 2FA enabled, I was locked out and couldn't log back in at all. Everything is back to normal now after I redeployed and restored from a backup.
@slanglade commented on GitHub (Dec 29, 2025):
Good point, I forgot to mention that I'm using the vaultwarden/server:latest image (with watchtower only to fire notification when there is a new version available)
@slanglade commented on GitHub (Dec 29, 2025):
Also a good point : it may be worth a separate issue in their respective repositories, but I also have the feeling that Bitwarden clients (both android or desktop firefox browser extension, in my case) lacks big red notification when they are not able to sync in the background. It only shows up for a manual sync.
@mzy2240 commented on GitHub (Dec 29, 2025):
Not able to log in back in any clients. I think 2FA keeps stopping me and somehow I am no longer able to receive the 2FA verification.
@mrz commented on GitHub (Dec 29, 2025):
Adding another data point: on my Vaultwarden instance there are two accounts / vaults, mine and my partner's. We both got logged out from our devices, however I was able to log back in on both my iOS and laptop devices, whereas my partner is unable to log back in on her Android device or laptop. She gets a generic username / password is incorrect error, but we are (fairly) confident that is not the case.
@Vivic87 commented on GitHub (Dec 29, 2025):
'Failed to fetch' in the brave extension at 1.35. I was able to log out in the app, though.
@knedl1k commented on GitHub (Dec 29, 2025):
I faced the same issue coming from 1.34.3, alpine image. Clients (Firefox extension; Apple, Android apps) wouldn't sync with the server. Relogging fixed the issue.
@ckoca commented on GitHub (Dec 29, 2025):
Same thing, I have 2 different vaultwarden deployments on different sites and multiple chrome addon and mobile clients connected to them. All of them was logged out at some point in the last 24 hours.
@7Mattias commented on GitHub (Dec 29, 2025):
I hat the token problem on iOS, iPadOS and Safari Extensions. The macOS client was fine. I don't know why.
I always use :latest and I update frequently. In this case it must have been 1.34.3 -> 1.35.0.
@lukaskirner commented on GitHub (Dec 29, 2025):
Same here. Upgraded from 1.34.3 -> 1.35.0. All devices were logged out due to the following error in the logs of the server:
@7Mattias commented on GitHub (Dec 29, 2025):
Same log entries here for every device.
Slightly off topic I guess: Is there a way to "monitor" such issues in an easy effortless way? I noticed this by accident today because I tried to add a secure note and this was not working.
Thanks for some advice.
@sjansen1 commented on GitHub (Dec 29, 2025):
Updated to 1.35 and got logged out on every desktop and browser client on all my machines (Linux and Windows). Secondary accounts with official Bitwarden servers also got logged out/disappeared.
@dani-garcia commented on GitHub (Dec 29, 2025):
This should be fixed with https://github.com/dani-garcia/vaultwarden/pull/6629, which when failing to parse the refresh token as JWT, will proceed the old way.
@dani-garcia commented on GitHub (Dec 29, 2025):
This PR is merged now and this should be available in
testing. I'd appreciate if anyone can test it to check if the issue is fixed. If so, the plan is to do a1.35.1release sometime soon.@Proxymiity commented on GitHub (Dec 29, 2025):
Just updated from 1.34.3 straight to 1.35.0-3e2cef7e (testing) and everything worked (tested on: Windows, Firefox and Android, all latest versions as of writing)
@stijneikelboom commented on GitHub (Dec 30, 2025):
Updated from
1.35.0to the recenttesting(3e2cef7e), and tried on a machine with clients left untouched since running1.34.3. Can confirm that the MacOS client and Chrome extension can still sync. The Safari extension had automatically logged out, so I haven't been able to test that.@dani-garcia commented on GitHub (Dec 30, 2025):
Version
1.35.1was just released now with the fix for this, let us know if you hit any more problems@BJReplay commented on GitHub (Dec 30, 2025):
I got this (failed to fetch) when I upgraded my test instance to 1.35.0 (as well as testing builds - which I set up on a test server).
I assumed, incorrectly, that it was a failure in my backup / restore process using ttionya/vaultwarden-backup - I have my phone logged into the restore system as a watchdog to ensure that daily restores just work (they pretty much usually do).
@TheSander562 commented on GitHub (Dec 31, 2025):
Still getting this with Authelia (including the offline_access scope) with version 1.35.1.
Not sure how i can help debugging where this comes from.
@eishockey commented on GitHub (Jan 1, 2026):
I have the same problem without SSO with Verson 1.35.1 with Windows Client Version 2025.12.0:
After every App restart I have to login again - and when I hit "sync vault" the sync fails and I have to relogin. But changes are synced to the instance.
I already killed all sessions, deleted the Bitwarden directory under AppData\Roaming on my PC and reinstalled the client - no changes.
My Android clients seems to have no issues.
@Ljzd-PRO commented on GitHub (Jan 19, 2026):
1.35.2 still (PC, Browser, iOS)