mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-07-18 01:49:32 -05:00
[GH-ISSUE #7146] Cannot confirm user's account #39873
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 @smbld on GitHub (Apr 28, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7146
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, ORG_CREATION_USERS, EMERGENCY_ACCESS_ALLOWED, EMAIL_CHANGE_ALLOWED, ADMIN_TOKEN, SMTP_HOST, SMTP_SECURITY, SMTP_PORT, SMTP_FROM, SMTP_FROM_NAME
Config:
Vaultwarden Build Version
1.35.8
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
no
Host/Server Operating System
Linux
Operating System Version
Debian 12
Clients
Web Vault
Client Version
No response
Steps To Reproduce
Expected Result
No errors
Actual Result
Error
Logs
Screenshots or Videos
No response
Additional Context
No response
@BlackDex commented on GitHub (Apr 28, 2026):
This is linked to your previous report, because of that issue, this issue happens.
@smbld commented on GitHub (Apr 28, 2026):
Not exactly because the previous report let me confirm the user.
This issue prevent me to confirm the user.
@BlackDex commented on GitHub (Apr 28, 2026):
Did the user excepted the invite already, fully?
Because a public-key is created during registering, if that for some reason failed or had an issue, then that user is not correctly created from the start.
Maybe you can see something in the logs when that user tried to register/create the account?
@smbld commented on GitHub (Apr 28, 2026):
[2026-04-28 15:15:21.335][vaultwarden::mail][ERROR] SMTP 5xx error: permanent error (550): 5.4.1 Recipient address rejected: Access denied, do we need a valid recipient mail when user is registering ? I'm using an internal address with alias on my account but i cannot have alias and the same mail attribute on two different account with Entra so i keep only one at time. Can it be the the root cause?
@BlackDex commented on GitHub (Apr 28, 2026):
I'm not an SSO expert. But these are the base rules for Bitwarden (And thus also Vaultwarden).
The account needs to be a valid e-mail address, that e-mail address needs to be a valid recipient for emails.
E-Mails are sent for import items like 2FA Fallback, or if someone has emergency-access contact, or master-password-reset is enabled. I think some actions even need some extra validation. So, if SMTP is enabled, you need a valid working e-mail address which can be used to contact the user.