mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #1256] When Vault is locked in a new browser session, you cannot login #884
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#884
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 @module0x90 on GitHub (Dec 5, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1256
Subject of the issue
I am on Arch Linux, latest and greatest and usually use only Vivaldi Browser. I have installed
the Bitwarden extension in there and it is working great.
Everytime though my machine was just started up, BW says
"Your vault is locked. Verify your master password to continue."
but when I provide the correct password, I only get
An error has occurred
Invalid Master password.
The only way to fix this is to log out, the re-login again.
I just tried Chromium and it is the same there.
Your environment
Vivaldi 3.4.2066.106 and extension version 1.47.1
Chromium 87.0.4280.66 and extension version 1.47.1
Bitwarden on Docker image using bitwardenrs/server:raspberry, currently on "bitwardenrs/server@sha256:bf5a81392a3e4390ced2a9e935b53165049ec8b2dcf1a531b8b2426d38f1ca26".
According to the webfront end Version 2.15.1.
Routed through Traefik, traefik:v2.3, v2.3.4
Steps to reproduce
Expected behaviour
It should accept the valid master password just fine. I don't mind it's locked - obviously.
Actual behaviour
Doesn't accept the valid master password.
@BlackDex commented on GitHub (Dec 5, 2020):
You have to update your bitwarden_rs version! Please search before posting a new issue and read the pinned issues.
https://github.com/dani-garcia/bitwarden_rs/issues/1180
@module0x90 commented on GitHub (Dec 7, 2020):
Hi, thanks.
I have updated now, as well as that I changed the docker tag now as well.
I can confirm that my issue above is fixed with version 1.17.0, what I am on right now.