mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-05-22 16:14:20 -05:00
[GH-ISSUE #6732] Vaultwarden v1.35.2: 2FA setup failing for old users, but working for new users. #15313
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 @GN998 on GitHub (Jan 17, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6732
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
vaultwarden/server:1.35.2-alpine
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
openresty:1.21.4.3-3-3-focal
Host/Server Operating System
Linux
Operating System Version
windows 11
Clients
Web Vault
Client Version
edge Vaultwarden Web 2025.12.1
Steps To Reproduce
Expected Result
Existing users should be able to manage and add 2FA/WebAuthn methods regardless of when their account was created or which version they originated from.
Actual Result
Timeline: The feature was working perfectly before 2025/12/29 on version 1.34.3.
Observation: The issue appeared after the sequential updates to the 1.35.x branch. It seems like a regression or a database compatibility issue affecting legacy user data.
Error Message: The web UI simply shows "An error has occurred" when clicking the setup button.
Logs
Screenshots or Videos
Additional Context
I have attached a screenshot of the F12 Developer Tools console logs showing the error.
@stefan0xC commented on GitHub (Jan 18, 2026):
Thanks for the report. I think I found the issue but just to confirm: does the user account where this fails have a user name?
@GN998 commented on GitHub (Jan 18, 2026):
Thank you for your response; a username has not been configured.