mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #6835] Misconfigured SMTP settings prevents logging in to web vault or fresh opening of mobile vault #2551
Labels
No 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
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2551
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @majal on GitHub (Feb 16, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6835
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: ADMIN_TOKEN
Config:
Vaultwarden Build Version
v1.35.3
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
caddy
Host/Server Operating System
Linux
Operating System Version
Ubuntu 24.04
Clients
Web Vault
Client Version
v2026.1.1
Steps To Reproduce
Expected Result
2FA should work
Actual Result
2FA fails
Logs
Screenshots or Videos
No response
Additional Context
This is what happened: I installed Bitwarden on a new phone. It accepted the username and password, but fails TOTP and all passkeys. I went to the web vault. Same thing. Fails all 2FA.
Only clue was the mobile client explained the error that it failed to send out emails. Web vault has no such warning. It just threw an undefined error.
So I went and logged in to
/adminto check SMPT settings. Then I remembered that my SMTP password did change months ago. I then adjusted it to the new password and SMTP worked. Login to both mobile and web vault then worked. (Problem fixed! 😅)The point of this bug report?
I was locked out of the web vault and new mobile device client just because SMTP failed. I don't know if this is by design, or is it something that needs to be corrected.
Kindly note that existing devices can sync and open vaults normally despite the SMTP misconfiguration. It was about six months prior that the SMTP password changed. Just that I did not add a new device or access the web vault since then.
Is it really by design to fail 2FA and lock out users just because SMTP fails, or is it a bug?
@stefan0xC commented on GitHub (Feb 16, 2026):
You have enabled
"require_device_email": true,so this is intentional.github.com/dani-garcia/vaultwarden@36f0620fd1/src/config.rs (L716-L718)