github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-12 01:45:56 -05:00
Code Issues 79 Packages Projects Releases 78 Wiki Activity

Change email doesn't show errors #5846

New Issue
Closed
opened 2026-03-07 20:40:17 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-03-07 20:40:17 -06:00
Owner
Copy Link

Originally created by @SaadBazaz on GitHub (Feb 21, 2025).

Vaultwarden Support String

Can't obtain, idk

Vaultwarden Build Version

Latest as of the date this issue was created

Deployment method

Official Container Image

Custom deployment method

I'm using it through Coolify, as a One-Click service

Reverse Proxy

Traefix

Host/Server Operating System

Linux

Operating System Version

Ubuntu Server 24

Clients

Web Vault

Client Version

No idea

Steps To Reproduce

(Pre-setup)

  1. Go to Admin Console of your VaultWarden instance
  2. Invite a user, let's say "chad@example.com"
  3. This user has NOT joined VaultWarden yet

Test repro:
You are currently "steve@example.com"

  1. Go to your Settings -> My account
  2. Under "Change Email", Enter Master code
  3. Enter New Email -> "chad@example.com"

Expected Result

It should ideally show:
"This email is already in use. Please try a different email."
Or something similar. Or at least throw a 500 unknown error.

Actual Result

It silently fails, even though Network tab shows a 400 request error.

Logs

Screenshots or Videos

https://github.com/user-attachments/assets/c9fc08d7-3510-4e4c-b936-59590f9f187d

Additional Context

No response

Originally created by @SaadBazaz on GitHub (Feb 21, 2025). ### Vaultwarden Support String Can't obtain, idk ### Vaultwarden Build Version Latest as of the date this issue was created ### Deployment method Official Container Image ### Custom deployment method I'm using it through Coolify, as a One-Click service ### Reverse Proxy Traefix ### Host/Server Operating System Linux ### Operating System Version Ubuntu Server 24 ### Clients Web Vault ### Client Version No idea ### Steps To Reproduce (Pre-setup) 1. Go to Admin Console of your VaultWarden instance 2. Invite a user, let's say "chad@example.com" 3. This user has NOT joined VaultWarden yet Test repro: You are currently "steve@example.com" 1. Go to your Settings -> My account 2. Under "Change Email", Enter Master code 3. Enter New Email -> "chad@example.com" ### Expected Result It should ideally show: "This email is already in use. Please try a different email." Or something similar. Or at least throw a 500 unknown error. ### Actual Result It silently fails, even though Network tab shows a 400 request error. ### Logs ```text ``` ### Screenshots or Videos https://github.com/user-attachments/assets/c9fc08d7-3510-4e4c-b936-59590f9f187d ### Additional Context _No response_
GiteaMirror added the enhancementlow priority labels 2026-03-07 20:40:17 -06:00
GiteaMirror commented 2026-03-07 20:40:18 -06:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Feb 21, 2025):

It seems to work fine for me.
And, if you were able to login using that password, you should also be able to use this form, the exact same function is used to check and validate the password.

@BlackDex commented on GitHub (Feb 21, 2025): It seems to work fine for me. And, if you were able to login using that password, you should also be able to use this form, the exact same function is used to check and validate the password.
GiteaMirror commented 2026-03-07 20:40:18 -06:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Feb 21, 2025):

Ah wait, the message is not shown indeed. But that isn't something we can fix I'm afraid.
The web-vault (client) is not something we develop or maintain.

We actually should mimic Bitwarden, and still send an email to the mail address entered and explain the action done, and still return a 200. Which would still not solve the error part, but that way of working seems a bit better.

@BlackDex commented on GitHub (Feb 21, 2025): Ah wait, the message is not shown indeed. But that isn't something we can fix I'm afraid. The web-vault (client) is not something we develop or maintain. We actually should mimic Bitwarden, and still send an email to the mail address entered and explain the action done, and still return a 200. Which would still not solve the error part, but that way of working seems a bit better.
GiteaMirror commented 2026-03-07 20:40:19 -06:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (May 19, 2025):

It seems to be solved in the latest web-vault currently in testing.

Going to close this as it's resolved already, and i have added the mail regarding the existing account to my #5798 PR.

@BlackDex commented on GitHub (May 19, 2025): It seems to be solved in the latest web-vault currently in testing. Going to close this as it's resolved already, and i have added the mail regarding the existing account to my #5798 PR.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No Label enhancement low priority
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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