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 to web vault after uprgade to 1.30.5 with error "2FA token not provided" #1872

New Issue
Closed
opened 2026-02-05 02:04:12 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-05 02:04:12 +03:00
Owner
Copy Link

Originally created by @aheath70 on GitHub (Mar 3, 2024).

Subject of the issue

After uprgade to 1.30.5 unable to log in using thge web vault. Log shows the following error:

"[2024-03-03 10:16:21.546][error][ERROR] 2FA token not provided"

Reverted back to version 1.30.3 and still getting the same error. Did a complete re-install of the machine, and still getting the same error.

iOS app appears to be able to still access the vault, but don't want to log out of it in case I can't log back in. Still able to login to admin page as well. Only appears to be the web vault which is affected.

Deployment environment

  • vaultwarden version: 1.30.5

  • Install method: Docker

  • Clients used: web vault

  • Reverse proxy and version: NGINX Proxy Manager, v2.11.1

  • MySQL/MariaDB or PostgreSQL version: N/A

  • Other relevant details:

Steps to reproduce

N/A

Expected behaviour

Able to login successfully.

Actual behaviour

Not able to log in with error,

Troubleshooting data

/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.30.5                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://github.com/dani-garcia/vaultwarden/discussions or        |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/
[INFO] Using saved config from `data/config.json` for configuration.
[2024-03-03 10:16:00.256][error][ERROR] 2FA token not provided
Originally created by @aheath70 on GitHub (Mar 3, 2024). <!-- # ### 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 After uprgade to 1.30.5 unable to log in using thge web vault. Log shows the following error: ``` "[2024-03-03 10:16:21.546][error][ERROR] 2FA token not provided" ``` Reverted back to version 1.30.3 and still getting the same error. Did a complete re-install of the machine, and still getting the same error. iOS app appears to be able to still access the vault, but don't want to log out of it in case I can't log back in. Still able to login to admin page as well. Only appears to be the web vault which is affected. ### 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.30.5 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> web vault * Reverse proxy and version: <!-- if applicable --> NGINX Proxy Manager, v2.11.1 * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> N/A * 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? --> N/A ### Expected behaviour <!-- Tell us what you expected to happen --> Able to login successfully. ### Actual behaviour <!-- Tell us what actually happened --> Not able to log in with error, ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> ``` /--------------------------------------------------------------------\ | Starting Vaultwarden | | Version 1.30.5 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://github.com/dani-garcia/vaultwarden/discussions or | | https://vaultwarden.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/vaultwarden/issues/new | \--------------------------------------------------------------------/ [INFO] Using saved config from `data/config.json` for configuration. [2024-03-03 10:16:00.256][error][ERROR] 2FA token not provided ```
OVERLORD commented 2026-02-05 02:04:18 +03:00
Author
Owner
Copy Link

@aheath70 commented on GitHub (Mar 3, 2024):

Just sorted it! It was a problem with my reverse proxy set up. Apologies!

@aheath70 commented on GitHub (Mar 3, 2024): Just sorted it! It was a problem with my reverse proxy set up. Apologies!
OVERLORD commented 2026-02-05 02:04:20 +03:00
Author
Owner
Copy Link

@celevra commented on GitHub (Mar 4, 2024):

i've the same issue and also an reverse proxy
what was the exact issue?

@celevra commented on GitHub (Mar 4, 2024): i've the same issue and also an reverse proxy what was the exact issue?
OVERLORD commented 2026-02-05 02:04:24 +03:00
Author
Owner
Copy Link

@aheath70 commented on GitHub (Mar 5, 2024):

Not sure, TBH. I use Cloudflare Zero Trust and I ended up bypassing my reverse proxy and just using the reverse proxy built into Cloudflare.

@aheath70 commented on GitHub (Mar 5, 2024): Not sure, TBH. I use Cloudflare Zero Trust and I ended up bypassing my reverse proxy and just using the reverse proxy built into Cloudflare.
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#1872
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?