starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

Login Fail after Vault Lock (Windows 10 app) #795

New Issue
Closed
opened 2026-02-04 22:42:47 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 22:42:47 +03:00
Owner
Copy Link

Originally created by @robobio on GitHub (Sep 8, 2020).

Bug Description

I am hosting BW on the Docker on a Synology NAS and I have never experienced the issue I am about to describe. I have installed the BW app in a fresh Windows 10 installation and the first login to my vault was successful. After locking the vault, though, I was unable to reenter it. A message kept appearing stating that my Master Password is wrong, although it was clearly not. However, I am only able to login to my vault after clicking the log-out button and then re-entiring the Master Password for the new login. For now, I have managed to bypass the problem by using the setting which logs me out after timeout instead of locking the vault. The BW app on my phone works pretty fine as usual. I lock the vault and then unlock it with my Master Password and everything is as it is supposed to be. Same holds true for the BW app in a Windows 10 laptop that I have; all works fine. It seems to be a problem with the fresh windows 10 installation. I have posted this issue at the official BW github but I was forwarded here.

Steps To Reproduce

  1. Open the BW app on Windows 10
  2. Login to your BW account
  3. Close BW, or lock the vault
  4. Try to reenter your vault by entering the Master Password

Expected Result

The expected outcome of the above steps would be to simply reenter the vault.

Actual Result

What actually happens is that an error appears stating that the Master Password is incorrect.

Screenshot

BW_error

Environment

  • Operating system: Windows 10
  • Build Version: 1.20.1
Originally created by @robobio on GitHub (Sep 8, 2020). ## Bug Description I am hosting BW on the Docker on a Synology NAS and I have never experienced the issue I am about to describe. I have installed the BW app in a fresh Windows 10 installation and the first login to my vault was successful. After locking the vault, though, I was unable to reenter it. A message kept appearing stating that my Master Password is wrong, although it was clearly not. However, I am only able to login to my vault after clicking the log-out button and then re-entiring the Master Password for the new login. For now, I have managed to bypass the problem by using the setting which logs me out after timeout instead of locking the vault. The BW app on my phone works pretty fine as usual. I lock the vault and then unlock it with my Master Password and everything is as it is supposed to be. Same holds true for the BW app in a Windows 10 laptop that I have; all works fine. It seems to be a problem with the fresh windows 10 installation. I have posted this issue at the official BW github but I was forwarded here. ## Steps To Reproduce 1. Open the BW app on Windows 10 2. Login to your BW account 3. Close BW, or lock the vault 4. Try to reenter your vault by entering the Master Password ## Expected Result The expected outcome of the above steps would be to simply reenter the vault. ## Actual Result What actually happens is that an error appears stating that the Master Password is incorrect. ## Screenshot ![BW_error](https://user-images.githubusercontent.com/70844077/92324918-70426d80-f046-11ea-9b8d-c0d1edf663f0.jpg) ## Environment - Operating system: Windows 10 - Build Version: 1.20.1
OVERLORD commented 2026-02-04 22:42:54 +03:00
Author
Owner
Copy Link

@lakenen commented on GitHub (Sep 9, 2020):

I am seeing the same issue on the OS X client.

@lakenen commented on GitHub (Sep 9, 2020): I am seeing the same issue on the OS X client.
OVERLORD commented 2026-02-04 22:42:56 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub (Sep 9, 2020):

I think this is fixed in server version 1.16.2, unless this is a separate issue.

What server versions are you running?

@dani-garcia commented on GitHub (Sep 9, 2020): I think this is fixed in server version 1.16.2, unless this is a separate issue. What server versions are you running?
OVERLORD commented 2026-02-04 22:43:01 +03:00
Author
Owner
Copy Link

@lakenen commented on GitHub (Sep 9, 2020):

Ah, yep, just updated my image to 1.16.3 and that fixed it for me.

@lakenen commented on GitHub (Sep 9, 2020): Ah, yep, just updated my image to 1.16.3 and that fixed it for me.
OVERLORD commented 2026-02-04 22:43:03 +03:00
Author
Owner
Copy Link

@robobio commented on GitHub (Sep 9, 2020):

I thought I had updated it, but was wrong. I've updated the image and now all works pretty fine! Thank you very much for the help!

@robobio commented on GitHub (Sep 9, 2020): I thought I had updated it, but was wrong. I've updated the image and now all works pretty fine! Thank you very much for the help!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear 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
Mirrored from GitHub Pull Request
 question
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#795
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?