starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

Unable to login from Edge extension when FIFO 2FA enabled #1372

New Issue
Closed
opened 2026-02-05 00:44:56 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 00:44:56 +03:00
Owner
Copy Link

Originally created by @plinss on GitHub (Oct 2, 2022).

Subject of the issue

Not sure if this is an issue with Vaultwarden or the Bitwarden Edge extension.

I just installed the extension in Edge and was unable to login to my vault.
In the extension, after entering the email address and master password, I get a page saying 'Refused to connect'. A bit later I get an email from Vaultwarden saying it saw a login but no 2FA. The Vaultwarden log shows: 'Error: 2FA token not provided'.

This account has both TOTP and FIDO 2FA enabled, and I'm able to login from the web client, desktop, and mobile apps.

I disabled FIDO 2FA for the account (leaving TOTP enabled) and was able to login (I got the TOTP prompt after entering the master password).

Deployment environment

  • vaultwarden version: 1.25.2

  • Install method: built from source

  • Clients used: Edge extension 2022.9.1

  • Reverse proxy and version: nginx 1.23.1

  • MySQL/MariaDB or PostgreSQL version: PostgreSQL 13.8

  • Other relevant details:

Steps to reproduce

Enable FIDO and TOTP 2FA for account in web client.
Install browser extension in Edge, try to login.

Expected behaviour

Prompt for FIDO key or TOTP

Actual behaviour

'Refused to connect' error message

Troubleshooting data

Originally created by @plinss on GitHub (Oct 2, 2022). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue Not sure if this is an issue with Vaultwarden or the Bitwarden Edge extension. I just installed the extension in Edge and was unable to login to my vault. In the extension, after entering the email address and master password, I get a page saying 'Refused to connect'. A bit later I get an email from Vaultwarden saying it saw a login but no 2FA. The Vaultwarden log shows: 'Error: 2FA token not provided'. This account has both TOTP and FIDO 2FA enabled, and I'm able to login from the web client, desktop, and mobile apps. I disabled FIDO 2FA for the account (leaving TOTP enabled) and was able to login (I got the TOTP prompt after entering the master password). ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.25.2 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: built from source * Clients used: Edge extension 2022.9.1 * Reverse proxy and version: nginx 1.23.1 * MySQL/MariaDB or PostgreSQL version: PostgreSQL 13.8 * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> Enable FIDO and TOTP 2FA for account in web client. Install browser extension in Edge, try to login. ### Expected behaviour <!-- Tell us what you expected to happen --> Prompt for FIDO key or TOTP ### Actual behaviour <!-- Tell us what actually happened --> 'Refused to connect' error message ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
OVERLORD commented 2026-02-05 00:45:05 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Oct 2, 2022):

Could you provide the support string which you can generate from the admin diagnostics page please.

Also, make sure you do not have added extra headers in nginx to block frames, or external content with custom CSP headers, those will break the functionality. Al the needed headers for security are configured in Vaultwarden already. Expect for HTST.

@BlackDex commented on GitHub (Oct 2, 2022): Could you provide the support string which you can generate from the admin diagnostics page please. Also, make sure you do not have added extra headers in nginx to block frames, or external content with custom CSP headers, those will break the functionality. Al the needed headers for security are configured in Vaultwarden already. Expect for HTST.
OVERLORD commented 2026-02-05 00:45:07 +03:00
Author
Owner
Copy Link

@plinss commented on GitHub (Oct 2, 2022):

I was adding headers in nginx to prevent being framed, removed those and it works now. Sorry for the bother and thanks for the input.

@plinss commented on GitHub (Oct 2, 2022): I was adding headers in nginx to prevent being framed, removed those and it works now. Sorry for the bother and thanks for the input.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear 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
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1372
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?