mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #1162] Unable to unlock vault with Firefox extension, have to log out and then back in. #819
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#819
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 @w4rc0n on GitHub (Sep 28, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1162
Subject of the issue
Anytime my Firefox session is restarted, I am required to unlock my vault again like normal. However, master password will not unlock the vault. I get: "An Error Has Ocurred: Invalid master password"
However, if I log out, then log back in, it requests my YubiKey again, and allows me to log back in with that very same password.
Your environment
Steps to reproduce
Restart Firefox session after being signed in, attempt to unlock the vault with the masterpassword.
I start the docker instance like such:
docker run -d --name bitwarden -e SIGNUPS_ALLOWED=false -e DOMAIN=REDACTED -e YUBICO_CLIENT_ID=REDACTED -e YUBICO_SECRET_KEY=REDACTED -v /bw-data/:/data/ -p 800:80 bitwardenrs/server:latest
Expected behaviour
Should be able to unlock my vault using my master password without relogging
Actual behaviour
I am unable to unlock my vault without relogging.
Relevant logs
@ruben-kinship commented on GitHub (Sep 28, 2020):
I experience the same issue!
@santiagon610 commented on GitHub (Sep 28, 2020):
👍 I've seen this with the MacOS desktop client as well.
Environment:
@BlackDex commented on GitHub (Sep 28, 2020):
This has already been fixed in the latest
testingimage on docker.Please use that one too fix these issues.
@w4rc0n commented on GitHub (Sep 29, 2020):
Not sure I want to use a testing image for my production bitwarden. I suppose I'll wait until it's in
latest@santiagon610 commented on GitHub (Sep 30, 2020):
Thanks @BlackDex - do you happen to know which PR resolved this?
@BlackDex commented on GitHub (Sep 30, 2020):
I do, https://github.com/dani-garcia/bitwarden_rs/pull/1158 .
@briceparmentier commented on GitHub (Oct 14, 2020):
Hi, I'm facing the same issue on Firefox.
Thanks @BlackDex for fixing this.
I think I will also wait for the fix to be ported in the "latest" docker image. but I'm running the raspberry pi version of it. Will this also be updated with the fix?
My question is how would we get the fix ? Do we need to download/reinstall something, or will it pull the changes automatically? Sorry for the noob question, I'm quite new to docker and this is the first time I'm using this kind of self-hosted tool and deployment.
Will we need to update something on the client side also (firefox plugin, android app...) ?
Thanks a lot !
@mio-moto commented on GitHub (Oct 22, 2020):
Is there an ETA when this is released on
latest? Doesn't seem to be in1.17.0.@BlackDex commented on GitHub (Oct 22, 2020):
@DarkMio This has been fixed an is available in the latest 1.17.0 version.
I also read reports that some users needed to double check there extension updates for this to be fixed.
@BlackDex commented on GitHub (Oct 22, 2020):
@briceparmentier Which image are you using?
We do not update the old raspberrypi image anymore since we have all images now in bitwardenrs/server where
testingis linked to the master branch, andlatestis linked to the latest tagged version, which in this case is1.17.0@mio-moto commented on GitHub (Oct 23, 2020):
@BlackDex It currently seems to work, looks like fixed for now. If any issues come up, I'll keep you posted.
The changelog didn't mention the inclusion of that fix (or I've missed it).
@santiagon610 commented on GitHub (Oct 23, 2020):
👍 on the fix, thanks folks!
@briceparmentier commented on GitHub (Oct 28, 2020):
@BlackDex I'm using raspberrypi image since I'm running it on .... a Raspberry Pi :p
By this do you mean that I can switch to the "server" version of the docker image without any trouble on RPi, or that I can't use it on RPi anymore?
I'm a bit concerned about upgrading / changing the docker image I'm using... I'm not very comfortable with tbh, because I don't understand very well how docker behaves. If I stop my machine, change the command line to use the server one, and run it again, will I keep all the data in the previous image?
Thanks again guys!
@briceparmentier commented on GitHub (Oct 28, 2020):
Oh ok I've read the introduction on the wiki, I wasn't aware of the modification to migrate to multiarch image.
I'll walk into this :)