Originally created by @abysso2 on GitHub (Dec 31, 2022).
vaultwarden version: 1.27.0
Install method: docker
Clients used: web vault
Reverse proxy and version: nginx, configuration from vaultwarden wiki
MySQL/MariaDB or PostgreSQL version: splite3
Other relevant details: webauthn as 2fa (yubikeys 5)
Steps to reproduce
Login via webauthn as 2fa
Expected behaviour
Login without error message
Actual behaviour
Successfuly logged in, but showing the error-message in /var/log/bitwarden.log
Troubleshooting data
/var/log/bitwarden.log:
2022-12-31 10:58:44.326][error][ERROR] 2FA token not provided
Originally created by @abysso2 on GitHub (Dec 31, 2022).
* vaultwarden version: 1.27.0
* Install method: docker
* Clients used: web vault
* Reverse proxy and version: nginx, configuration from vaultwarden wiki
* MySQL/MariaDB or PostgreSQL version: splite3
* Other relevant details: webauthn as 2fa (yubikeys 5)
### Steps to reproduce
Login via webauthn as 2fa
### Expected behaviour
Login without error message
### Actual behaviour
Successfuly logged in, but showing the error-message in /var/log/bitwarden.log
### Troubleshooting data
/var/log/bitwarden.log:
2022-12-31 10:58:44.326][error][ERROR] 2FA token not provided
It works for me ok.
Double check your reverse proxy settings, it probably adds some headers or changes some which block some features. Also some reverse proxy capture errors and modify the response, which also causes issues.
The error message you see there is normal, that is the notification for the clients to ask for the mfa token.
@BlackDex commented on GitHub (Dec 31, 2022):
It works for me ok.
Double check your reverse proxy settings, it probably adds some headers or changes some which block some features. Also some reverse proxy capture errors and modify the response, which also causes issues.
The error message you see there is normal, that is the notification for the clients to ask for the mfa token.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @abysso2 on GitHub (Dec 31, 2022).
vaultwarden version: 1.27.0
Install method: docker
Clients used: web vault
Reverse proxy and version: nginx, configuration from vaultwarden wiki
MySQL/MariaDB or PostgreSQL version: splite3
Other relevant details: webauthn as 2fa (yubikeys 5)
Steps to reproduce
Login via webauthn as 2fa
Expected behaviour
Login without error message
Actual behaviour
Successfuly logged in, but showing the error-message in /var/log/bitwarden.log
Troubleshooting data
/var/log/bitwarden.log:
2022-12-31 10:58:44.326][error][ERROR] 2FA token not provided
@BlackDex commented on GitHub (Dec 31, 2022):
It works for me ok.
Double check your reverse proxy settings, it probably adds some headers or changes some which block some features. Also some reverse proxy capture errors and modify the response, which also causes issues.
The error message you see there is normal, that is the notification for the clients to ask for the mfa token.