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

Bitwarden Client (2025.2.1+) causes 404 Error during registration #2220

New Issue
Closed
opened 2026-02-05 03:37:47 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-05 03:37:47 +03:00
Owner
Copy Link

Originally created by @Sidicer on GitHub (Mar 17, 2025).

Vaultwarden Support String

Generate Support String does not do anything (Console error on page load Uncaught TypeError: serverInstalled is null). Copying page contents.

Diagnostics
Versions

Server Installed
Server Latest
    1.33.2 
Web Installed
    2024.6.2c 
Web Latest
    2025.1.1 
Database
    SQLite: 3.46.0 

Checks

OS/Arch
    freebsd / x86_64 
Running within a container
    No 
Environment settings overridden
    No 
Uses a reverse proxy
    Yes 
IP header Match
    Config/Server: X-Real-IP 
Internet access Ok
    Yes 
Internet access via a proxy
    No 
Websocket enabled
    Yes 
DNS (github.com)
    <REDACTED> 
Date & Time (Local)
    Server: 2025-03-17 13:32:14 +00:00 
Date & Time (UTC) Server/Browser Ok Server NTP Ok Browser NTP Ok
    NTP: 2025-03-17 13:32:18 UTC Server: 2025-03-17 13:32:14 UTC Browser: 2025-03-17 13:32:19 UTC 
Domain configuration No Match HTTPS
    Server: <REDACTED DUE TO PRIVACY> 
    Browser: <REDACTED DUE TO PRIVACY>

Vaultwarden Build Version

1.32.7 & 1.33.2

Deployment method

OS Package (apt, yum/dnf, pacman, apk, nix, ...)

Custom deployment method

Name           : vaultwarden
Version        : 1.32.7
Installed on   : Thu Feb 27 14:43:28 2025 UTC
Origin         : security/vaultwarden
Architecture   : FreeBSD:13:amd64
Prefix         : /usr/local
Categories     : security
Licenses       : GPLv3
Maintainer     : mr@FreeBSD.org
WWW            : https://github.com/dani-garcia/vaultwarden
Comment        : Bitwarden compatible backend server
Options        :
	MYSQL          : on
	PGSQL          : on
	SQLITE         : on
	WEBVAULT       : on
Shared Libs required:
	libpq.so.5
	libmysqlclient.so.21
Annotations    :
	FreeBSD_version: 1304000
	build_timestamp: 2025-02-01T15:08:50+0000
	built_by       : poudriere-git-3.4.2
	port_checkout_unclean: no
	port_git_hash  : dddb9bab3
	ports_top_checkout_unclean: no
	ports_top_git_hash: 2e0e0c62c
	repo_type      : binary
	repository     : FreeBSD

Reverse Proxy

nginx/1.26.2

Host/Server Operating System

Other

Operating System Version

FreeBSD 13.4-RELEASE-p4

Clients

Desktop

Client Version

Desktop 2025.2.1-1

Steps To Reproduce

  1. Open 2025.2.1-1 (or later) desktop client
  2. Set self-hosted to your vaultwarden endpoint
  3. Go to Create account
  4. Enter email, name clint "Continue"
  5. Error appears in top right
  6. In logs you can see 404
Mar 17 13:14:18 vaultwarden vaultwarden[74264]: [2025-03-17 13:14:18.751][request][INFO] POST /identity/accounts/register/send-verification-email
Mar 17 13:14:18 vaultwarden vaultwarden[74264]: [2025-03-17 13:14:18.751][response][INFO] 404 Not Found

Expected Result

Successful next page for registration

Actual Result

Error in Client and Logs

Logs

Mar 17 13:14:18 vaultwarden vaultwarden[74264]: [2025-03-17 13:14:18.751][request][INFO] POST /identity/accounts/register/send-verification-email
Mar 17 13:14:18 vaultwarden vaultwarden[74264]: [2025-03-17 13:14:18.751][response][INFO] 404 Not Found

Screenshots or Videos

No response

Additional Context

No response

Originally created by @Sidicer on GitHub (Mar 17, 2025). ### Vaultwarden Support String `Generate Support String` does not do anything (Console error on page load `Uncaught TypeError: serverInstalled is null`). Copying page contents. ``` Diagnostics Versions Server Installed Server Latest 1.33.2 Web Installed 2024.6.2c Web Latest 2025.1.1 Database SQLite: 3.46.0 Checks OS/Arch freebsd / x86_64 Running within a container No Environment settings overridden No Uses a reverse proxy Yes IP header Match Config/Server: X-Real-IP Internet access Ok Yes Internet access via a proxy No Websocket enabled Yes DNS (github.com) <REDACTED> Date & Time (Local) Server: 2025-03-17 13:32:14 +00:00 Date & Time (UTC) Server/Browser Ok Server NTP Ok Browser NTP Ok NTP: 2025-03-17 13:32:18 UTC Server: 2025-03-17 13:32:14 UTC Browser: 2025-03-17 13:32:19 UTC Domain configuration No Match HTTPS Server: <REDACTED DUE TO PRIVACY> Browser: <REDACTED DUE TO PRIVACY> ``` ### Vaultwarden Build Version 1.32.7 & 1.33.2 ### Deployment method OS Package (apt, yum/dnf, pacman, apk, nix, ...) ### Custom deployment method ``` Name : vaultwarden Version : 1.32.7 Installed on : Thu Feb 27 14:43:28 2025 UTC Origin : security/vaultwarden Architecture : FreeBSD:13:amd64 Prefix : /usr/local Categories : security Licenses : GPLv3 Maintainer : mr@FreeBSD.org WWW : https://github.com/dani-garcia/vaultwarden Comment : Bitwarden compatible backend server Options : MYSQL : on PGSQL : on SQLITE : on WEBVAULT : on Shared Libs required: libpq.so.5 libmysqlclient.so.21 Annotations : FreeBSD_version: 1304000 build_timestamp: 2025-02-01T15:08:50+0000 built_by : poudriere-git-3.4.2 port_checkout_unclean: no port_git_hash : dddb9bab3 ports_top_checkout_unclean: no ports_top_git_hash: 2e0e0c62c repo_type : binary repository : FreeBSD ``` ### Reverse Proxy nginx/1.26.2 ### Host/Server Operating System Other ### Operating System Version FreeBSD 13.4-RELEASE-p4 ### Clients Desktop ### Client Version Desktop 2025.2.1-1 ### Steps To Reproduce 1. Open `2025.2.1-1` (or later) desktop client 2. Set `self-hosted` to your vaultwarden endpoint 3. Go to `Create account` 4. Enter email, name clint "Continue" 5. Error appears in top right 6. In logs you can see 404 ``` Mar 17 13:14:18 vaultwarden vaultwarden[74264]: [2025-03-17 13:14:18.751][request][INFO] POST /identity/accounts/register/send-verification-email Mar 17 13:14:18 vaultwarden vaultwarden[74264]: [2025-03-17 13:14:18.751][response][INFO] 404 Not Found ``` ### Expected Result Successful next page for registration ### Actual Result Error in Client and Logs ### Logs ```text Mar 17 13:14:18 vaultwarden vaultwarden[74264]: [2025-03-17 13:14:18.751][request][INFO] POST /identity/accounts/register/send-verification-email Mar 17 13:14:18 vaultwarden vaultwarden[74264]: [2025-03-17 13:14:18.751][response][INFO] 404 Not Found ``` ### Screenshots or Videos _No response_ ### Additional Context _No response_ ---
OVERLORD added the bug label 2026-02-05 03:37:47 +03:00
OVERLORD commented 2026-02-05 03:37:51 +03:00
Author
Owner
Copy Link

@Sidicer commented on GitHub (Mar 17, 2025):

Update: This is also an issue with 1.33.2 vaultwarden and 2025.1.1 vaultwarden-web
_smtp_enabled: false does not disable POST /identity/accounts/register/send-verification-email so even disabling mail/smtp does not resolve the issue temporarily

@Sidicer commented on GitHub (Mar 17, 2025): Update: This is also an issue with `1.33.2` vaultwarden and `2025.1.1` vaultwarden-web `_smtp_enabled: false` does not disable `POST /identity/accounts/register/send-verification-email` so even disabling mail/smtp does not resolve the issue temporarily
OVERLORD commented 2026-02-05 03:37:55 +03:00
Author
Owner
Copy Link

@Sidicer commented on GitHub (Mar 17, 2025):

From further testing I can confirm that this issue is caused by the Bitwarden Client as it does not check if email verification or smtp is disabled and forces POST /identity/accounts/register/send-verification-email

For testing reasons I set nginx to return 204 from /identity/accounts/register/send-verification-email which the client just shows

Follow the link in the email sent to email@address and continue creating your account

Even with smtp disabled and SIGNUPS_VERIFY set to false.

@Sidicer commented on GitHub (Mar 17, 2025): From further testing I can confirm that this issue is caused by the Bitwarden Client as it does not check if email verification or smtp is disabled and forces `POST /identity/accounts/register/send-verification-email` For testing reasons I set nginx to `return 204` from `/identity/accounts/register/send-verification-email` which the client just shows > Follow the link in the email sent to email@address and continue creating your account Even with smtp disabled and `SIGNUPS_VERIFY` set to `false`.
OVERLORD commented 2026-02-05 03:37:58 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub (Mar 17, 2025):

This is due to a new endpoint that needs to be implemented. Note that the send-verification-email will be used regardless of whether SMTP is enabled or not, that is expected. It should be solved with https://github.com/dani-garcia/vaultwarden/pull/5215, you can try the testing docker tag in half an hour or so, as I've just merged that PR.

@dani-garcia commented on GitHub (Mar 17, 2025): This is due to a new endpoint that needs to be implemented. Note that the `send-verification-email` will be used regardless of whether SMTP is enabled or not, that is expected. It should be solved with https://github.com/dani-garcia/vaultwarden/pull/5215, you can try the `testing` docker tag in half an hour or so, as I've just merged that PR.
OVERLORD commented 2026-02-05 03:38:02 +03:00
Author
Owner
Copy Link

@Sidicer commented on GitHub (Mar 17, 2025):

This is due to a new endpoint that needs to be implemented. Note that the send-verification-email will be used regardless of whether SMTP is enabled or not, that is expected. It should be solved with https://github.com/dani-garcia/vaultwarden/pull/5215, you can try the testing docker tag in half an hour or so, as I've just merged that PR.

Registration using Vaultwardens WebUI should not have this issue correct? It's only when using Bitwardens official clients?

Because if so we can move registration from the client to our web ui until the fix is part of the next release (no possibility of using docker test builds)

@Sidicer commented on GitHub (Mar 17, 2025): > This is due to a new endpoint that needs to be implemented. Note that the `send-verification-email` will be used regardless of whether SMTP is enabled or not, that is expected. It should be solved with https://github.com/dani-garcia/vaultwarden/pull/5215, you can try the `testing` docker tag in half an hour or so, as I've just merged that PR. Registration using Vaultwardens WebUI should not have this issue correct? It's only when using Bitwardens official clients? Because if so we can move registration from the client to our web ui until the fix is part of the next release (no possibility of using docker test builds)
OVERLORD commented 2026-02-05 03:38:05 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub (Mar 17, 2025):

That's correct, at the moment the web vault included with Vaultwarden is older and so isn't trying to use this new endpoint.

@dani-garcia commented on GitHub (Mar 17, 2025): That's correct, at the moment the web vault included with Vaultwarden is older and so isn't trying to use this new endpoint.
OVERLORD commented 2026-02-05 03:38:10 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Mar 26, 2025):

Closing this issue as it's Resolved via #5215
Not yet in a stable release though, testing only.

@BlackDex commented on GitHub (Mar 26, 2025): Closing this issue as it's Resolved via #5215 Not yet in a stable release though, testing only.
OVERLORD commented 2026-02-05 03:38:13 +03:00
Author
Owner
Copy Link

@StrikeZW commented on GitHub (Jul 16, 2025):

is this still not available in the stable release ( 2025.7.0 ) ?

after a fresh install I saw this

Request finished HTTP/1.1 POST http://xxxxxxxx.de/identity/accounts/register/send-verification-email - 404 0 - 0.0727ms

in my logs and I am unable to register

@StrikeZW commented on GitHub (Jul 16, 2025): is this still not available in the stable release ( 2025.7.0 ) ? after a fresh install I saw this **Request finished HTTP/1.1 POST http://xxxxxxxx.de/identity/accounts/register/send-verification-email - 404 0 - 0.0727ms** in my logs and I am unable to register
OVERLORD commented 2026-02-05 03:38:22 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Jul 16, 2025):

Already resolved in https://github.com/dani-garcia/vaultwarden/releases/tag/1.34.0

So, should be in :testing and :latest.

@BlackDex commented on GitHub (Jul 16, 2025): Already resolved in https://github.com/dani-garcia/vaultwarden/releases/tag/1.34.0 So, should be in `:testing` and `:latest`.
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 bug
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#2220
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?