mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #5227] new entries not saved due to invalid Refresh token #2098
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2098
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @JRehkemper on GitHub (Nov 24, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/5227
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Vaultwarden Build Version
1.32.5
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Traefik 3.2.1
Host/Server Operating System
Linux
Operating System Version
AlmaLinux 9.4
Clients
Web Vault, Desktop, Android, iOS
Client Version
Brave 1.73.91
Steps To Reproduce
Expected Result
When you get the green "saved"-popup it should be saved to your vault.
Actual Result
You get a green "saved"-popup but the entry is not present if I resync the vault, check on a different device or log back in again.
Logs
Screenshots or Videos
Additional Context
Hello,
I get sporadic errors with invalid refresh token on multiple devices. The frustrating thing is, sometimes you can open the app and everything looks fine and if you create a new entry, it will tell you everything is ok. You only notice the invalid refresh token if you want to login again. Usually this can be fixed by completely logging out and in again, but the newly created password isn't saved anywhere because of the invalid refresh token.
I tried the webinterface and clients for Android, IOS, WIndows and Linux and all have the same problem.
I suspected an database corruption and created a new instance of vaultwarden. But after a reimport of the reimport of the vault the problem persists.
Any ideas how to troubleshoot this issue is appreciated.
@BlackDex commented on GitHub (Nov 24, 2024):
Do you have since kind of HA setup running for Vaultwarden?
An invalid claim doesn't come by it self. Something must be invalid, like date/time different or modified private key used to create those tokens.
@JRehkemper commented on GitHub (Nov 24, 2024):
There is no high availability in place. Just a single Docker server.
The time is synced. Clients and Docker-server are in CET and the container is running in UTC but they are the expect hour apart.
I did not change any keys.
@BlackDex commented on GitHub (Nov 24, 2024):
Does the server restart? What is the date/time of the
rsa_key.pemfile in your data directory?Is there any WAF, ModSecurity or something like CloudFlare or CloudFront i front of it?
Something must mangle the token.
You can also try to delete the
rsa_key.pem, restart Vaultwarden and see if that solves it. But it think you kinda did that already, unless you copied that exact same file over. Doing that will invalidate all tokens and invites though.