mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
After updating security keys, cannot login, "No U2F devices registered" #1167
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 @ivan on GitHub (Dec 8, 2021).
Subject of the issue
I am unable to log in to my web vaultwarden after adding a second security key and re-adding the first security key. I am pretty sure I did this right, or at least the UI made it look that way, but I was not recording my screen :(
Now, after entering the correct password on login, I see a "No U2F devices registered" error, and there is no UI to prompt for my backup TOTP or backup code.
vaultwarden was working fine when I had just one security key, and I think it broke after I added a second one with this procedure:
The first security key was a YubiKey 5 NFC, the second was a Security Key NFC by Yubico, and I did all of this in Chrome 96 on Windows 10 21H2.
Deployment environment
Install method: the vaultwarden service on NixOS 21.11. I connect it through an nginx with a
proxy_pass http://127.0.0.1:8222Clients used: web vault
Reverse proxy and version: N/A
MySQL/MariaDB or PostgreSQL version: I am using sqlite
Other relevant details:
Steps to reproduce
Expected behaviour
Actual behaviour
Troubleshooting data
vaultwarden's log shows:
@BlackDex commented on GitHub (Dec 9, 2021):
Not sure what happened here. Maybe some strange mix/match during rename or removal.
I suggest to remove mfa from this account via the admin interface and try to reapply this.
@ivan commented on GitHub (Dec 12, 2021):
Thank you, I managed to use the admin interface to remove all 2FA for the account and get back in.
After trying the same procedure with the re-adding of the first security key, I was unable to reproduce the issue. My only guess as to the difference now is that when I changed the security keys on October 6, the first key was previously added with older bitwarden-rs in October 2020.
I took a backup of the bad database, but I don't know if that is useful for further investigation.
Feel free to close this, as it might not be worth investigating further.