starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2025-12-11 09:13:02 +03:00
Code Issues 429 Packages Projects Releases 10 Wiki Activity

Lost access after update #1141

New Issue
Closed
opened 2025-10-09 17:05:21 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2025-10-09 17:05:21 +03:00
Owner
Copy Link

Originally created by @siperwrx on GitHub.

Subject of the issue

I updated to Version 1.25.0 yesterday and now I can't access my vault. It won't accept my master password (which I know is correct). Is it possible to downgrade and restore my passwords? I'm using Docker on Synology.

Deployment environment

  • vaultwarden version: 1.25.0

  • Install method: Docker image

  • Clients used: Brave extension, Android, web

  • Reverse proxy and version:

  • MySQL/MariaDB or PostgreSQL version:

  • Other relevant details:

Steps to reproduce

Expected behaviour

Actual behaviour

Troubleshooting data

Originally created by @siperwrx on GitHub. <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue I updated to Version 1.25.0 yesterday and now I can't access my vault. It won't accept my master password (which I know is correct). Is it possible to downgrade and restore my passwords? I'm using Docker on Synology. ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.25.0 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker image * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> Brave extension, Android, web * Reverse proxy and version: <!-- if applicable --> * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> ### Expected behaviour <!-- Tell us what you expected to happen --> ### Actual behaviour <!-- Tell us what actually happened --> ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
OVERLORD commented 2025-10-09 17:05:23 +03:00
Author
Owner
Copy Link

@siperwrx commented on GitHub:

This is the last line of the log after updating:
[2022-05-23 21:24:29.377][response][INFO] (login) POST /identity/connect/token => 400 Bad Request

For follow up attempts to login, I'm getting the same error.

@siperwrx commented on GitHub: This is the last line of the log after updating: [2022-05-23 21:24:29.377][response][INFO] (login) POST /identity/connect/token => 400 Bad Request For follow up attempts to login, I'm getting the same error.
OVERLORD commented 2025-10-09 17:05:23 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub:

Looks like a duplicate of #2493

@BlackDex commented on GitHub: Looks like a duplicate of #2493
OVERLORD commented 2025-10-09 17:05:23 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub:

Closed as a duplicate of #2493.

@BlackDex commented on GitHub: Closed as a duplicate of #2493.
OVERLORD commented 2025-10-09 17:05:24 +03:00
Author
Owner
Copy Link

@Tieneks commented on GitHub:

Could you answer the three questions mentioned here?

@Tieneks commented on GitHub: Could you answer the three questions mentioned [here](https://github.com/dani-garcia/vaultwarden/discussions/2493#discussioncomment-2814128)?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
bug
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1141
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?