mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-03-01 11:19:52 +03:00
Can't configure Yubikey #216
Reference in New Issue
Block a user
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 @zachary-russell on GitHub (Jan 29, 2019).
I am having an issue where I can't configure my Yubikey to work with bitwarden_rs. I can get FIDO to work, however. This is not ideal because for some reason U2F is not working in the Firefox extension login (though it is in the FF web vault login).
I am getting this error in the browser when entering my master password:
POST https://bitwarden.protechig.com/api/two-factor/get-yubikey 404I am using my host's nginx to proxy to the docker container. I have HTTPS enabled with LetsEncrypt and websockets are working.
Note: This same exact error happens with Duo set up, and the FIDO keys also don't show names. I have no idea if it's related.
@dani-garcia commented on GitHub (Jan 29, 2019):
I don't think you should be getting a 404 there, did you set up the environment variables mentioned in the wiki? Do you get any errors on the logs?
Duo is not implemented, so the 404 error there makes sense. About U2F, at the moment we only support one key, so the multiple keys and names are not supported either.
@zachary-russell commented on GitHub (Jan 29, 2019):
Thanks for the super swift response @dani-garcia!
Here is my config file:
Oddly enough, I can't even find the log files. I tried destroying and recreating the containers and removing the entire
bw-datadirectory.@dani-garcia commented on GitHub (Jan 29, 2019):
The config seems OK to me. Are you using a recent version of the image? You can try to update it with
docker compose pullwith the services stopped.@zachary-russell commented on GitHub (Jan 30, 2019):
I have no idea what is going wrong. I pulled the image today. It's showing all sorts of odd things (like asking for billing information). I ended up just stopping this project and am running it in K8s now.