starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2025-12-11 09:13:02 +03:00
Code Issues 429 Packages Projects Releases 10 Wiki Activity

Signups don't work #1210

New Issue
Closed
opened 2025-10-09 17:07:47 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2025-10-09 17:07:47 +03:00
Owner
Copy Link

Originally created by @TheDutchSmoke on GitHub.

Subject of the issue

Signups don't work

Deployment environment

  • vaultwarden version: 1.23.1

  • Install method: Unraid App Store (Docker-Compose)

  • Clients used:
    Web-Vault desktop site

  • Reverse proxy and version:
    NGINX Reverse Proxy manager

  • MySQL/MariaDB or PostgreSQL version:

  • Other relevant details:
    The startup log message:
    [WARNING] The following environment variables are being overriden by the config file,
    [WARNING] please use the admin panel to make changes to them:
    [WARNING] SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, ADMIN_TOKEN

The /admin page:
https://www.mijnscreens.nl/Muxa5/XOmABOFO10.png

The Compose File:
https://www.mijnscreens.nl/Muxa5/MOxUjaWE85.png

Steps to reproduce

Set every sign up as "allowed"

Expected behaviour

Signups should be allowed

Actual behaviour

Signups don't work

Signup screen with a new (unknown to the server) account:
https://www.mijnscreens.nl/Muxa5/neLIHeja14.png

The logs:
[2022-01-29 01:31:37.074][request][INFO] POST /api/accounts/register
[2022-01-29 01:31:37.074][vaultwarden::api::core::accounts][ERROR] Registration not allowed or user already exists

[2022-01-29 01:31:37.074][response][INFO] POST /api/accounts/register (register) => 400 Bad Request
[2022-01-29 01:31:37.074][request][INFO] POST /api/accounts/register
[2022-01-29 01:31:37.074][vaultwarden::api::core::accounts][ERROR] Registration not allowed or user already exists

[2022-01-29 01:31:37.074][response][INFO] POST /api/accounts/register (register) => 400 Bad Request

Troubleshooting data

The live instance:
https://www.mijnkorte.link/vaultwarden

Originally created by @TheDutchSmoke on GitHub. <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> Signups don't work ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.23.1 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Unraid App Store (Docker-Compose) * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> Web-Vault desktop site * Reverse proxy and version: <!-- if applicable --> NGINX Reverse Proxy manager * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> * Other relevant details: The startup log message: [WARNING] The following environment variables are being overriden by the config file, [WARNING] please use the admin panel to make changes to them: [WARNING] SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, ADMIN_TOKEN The /admin page: https://www.mijnscreens.nl/Muxa5/XOmABOFO10.png The Compose File: https://www.mijnscreens.nl/Muxa5/MOxUjaWE85.png ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> Set every sign up as "allowed" ### Expected behaviour <!-- Tell us what you expected to happen --> Signups should be allowed ### Actual behaviour <!-- Tell us what actually happened --> Signups don't work Signup screen with a new (unknown to the server) account: https://www.mijnscreens.nl/Muxa5/neLIHeja14.png The logs: [2022-01-29 01:31:37.074][request][INFO] POST /api/accounts/register [2022-01-29 01:31:37.074][vaultwarden::api::core::accounts][ERROR] Registration not allowed or user already exists [2022-01-29 01:31:37.074][response][INFO] POST /api/accounts/register (register) => 400 Bad Request [2022-01-29 01:31:37.074][request][INFO] POST /api/accounts/register [2022-01-29 01:31:37.074][vaultwarden::api::core::accounts][ERROR] Registration not allowed or user already exists [2022-01-29 01:31:37.074][response][INFO] POST /api/accounts/register (register) => 400 Bad Request ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> The live instance: https://www.mijnkorte.link/vaultwarden
OVERLORD commented 2025-10-09 17:07:49 +03:00
Author
Owner
Copy Link

@TheDutchSmoke commented on GitHub:

Well, I guess the security works. I had a certain email domain whitelist set in the admin panel. Did use a other domain, it works as expected. Closing the issue.

@TheDutchSmoke commented on GitHub: Well, I guess the security works. I had a certain email domain whitelist set in the admin panel. Did use a other domain, it works as expected. Closing the issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
bug
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
troubleshooting
wontfix
No Label
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#1210
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?