Signups are still possible after disabling it via Environment and/or admin interface. I tried both Environment-var and the admin interface, always restarted the container after disabling, however im still able to create sign up new user on the Login Page. Could someone verify if this is a problem in my deployment or a bug?
Your environment
Bitwarden_rs version: 1.13.1-632d5526
Install method: Docker (using Compose in Portainer)
Clients used: WebVault
Reverse proxy and version: Traefik 1.7
Version of mysql/postgresql: i use the includede database
Other relevant information:
Steps to reproduce
Disable Signup in Admin Interface or via Environment Var, restart the server and sign up with a new email.
Expected behaviour
Signups not possible after disabling them
Actual behaviour
Signups are still possible
Relevant logs
Please tell me which logs i should provide since i do not see anything relevant in the logs i see from the container in portainer.
Originally created by @Zuwizara on GitHub (Jan 29, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/830
### Subject of the issue
Signups are still possible after disabling it via Environment and/or admin interface. I tried both Environment-var and the admin interface, always restarted the container after disabling, however im still able to create sign up new user on the Login Page. Could someone verify if this is a problem in my deployment or a bug?
### Your environment
* Bitwarden_rs version: 1.13.1-632d5526
* Install method: Docker (using Compose in Portainer)
* Clients used: WebVault
* Reverse proxy and version: Traefik 1.7
* Version of mysql/postgresql: i use the includede database
* Other relevant information:
### Steps to reproduce
Disable Signup in Admin Interface or via Environment Var, restart the server and sign up with a new email.
### Expected behaviour
Signups not possible after disabling them
### Actual behaviour
Signups are still possible
### Relevant logs
Please tell me which logs i should provide since i do not see anything relevant in the logs i see from the container in portainer.
GiteaMirror
added the bug label 2026-04-25 19:27:51 -05:00
Same problem here, same bitwarden_rs version, disabling via env var does not work. It does show up as disabled in the admin interface.
<!-- gh-comment-id:579689026 -->
@bergernetch commented on GitHub (Jan 29, 2020):
Same problem here, same bitwarden_rs version, disabling via env var does not work. It does show up as disabled in the admin interface.
@Latschenharry commented on GitHub (Jan 29, 2020):
Have you tried creating an account. Because the register button will always be there. If signups are disabled, you will only get an error when hitting the sent button.
<!-- gh-comment-id:579694546 -->
@Latschenharry commented on GitHub (Jan 29, 2020):
Have you tried creating an account. Because the register button will always be there. If signups are disabled, you will only get an error when hitting the sent button.
Have you tried creating an account. Because the register button will always be there. If signups are disabled, you will only get an error when hitting the sent button.
Yes, i always created test users and it was successful
<!-- gh-comment-id:579705864 -->
@Zuwizara commented on GitHub (Jan 29, 2020):
> Have you tried creating an account. Because the register button will always be there. If signups are disabled, you will only get an error when hitting the sent button.
Yes, i always created test users and it was successful
Have you tried creating an account. Because the register button will always be there. If signups are disabled, you will only get an error when hitting the sent button.
Yes, i always created test users and it was successful
Same here. I would like it when the create button would also be disabled or even better removed.
<!-- gh-comment-id:579719252 -->
@bergernetch commented on GitHub (Jan 29, 2020):
> > Have you tried creating an account. Because the register button will always be there. If signups are disabled, you will only get an error when hitting the sent button.
>
> Yes, i always created test users and it was successful
Same here. I would like it when the create button would also be disabled or even better removed.
Hello, I have the same issue. Whitelisting domains for signup works, but disabling signups not, the same as the original poster. My version is 1.20.0, running on Ubuntu with caddy reverse proxy. Tried both env variable and setting it via web admin interface. Admin interface shows "Allow new signups" as false. I can still create new accounts via the "Create Account" button - the account created is actually working.
Is there some log info I can provide ?
<!-- gh-comment-id:824197225 -->
@molnarriso commented on GitHub (Apr 21, 2021):
Hello, I have the same issue. Whitelisting domains for signup works, but disabling signups not, the same as the original poster. My version is 1.20.0, running on Ubuntu with caddy reverse proxy. Tried both env variable and setting it via web admin interface. Admin interface shows "Allow new signups" as false. I can still create new accounts via the "Create Account" button - the account created is actually working.
Is there some log info I can provide ?
@molnarriso Posting in a closed issue is not very useful.
Besides that, if you have SIGNUPS_ALLOWED=false configured you can't create an account via the web-vault.
There is one exception, and that is if you have configured SIGNUPS_DOMAINS_WHITELIST, every domain in that list is allowed to create an account no matter what SIGNUPS_ALLOWED is set to.
If you have checked those settings and still have an issue, i suggest to open a new topic at the Discussions and provide a support string which you can generate via the /admin/diagnostics page.
<!-- gh-comment-id:824242407 -->
@BlackDex commented on GitHub (Apr 21, 2021):
@molnarriso Posting in a closed issue is not very useful.
Besides that, if you have `SIGNUPS_ALLOWED=false` configured you can't create an account via the web-vault.
There is one exception, and that is if you have configured `SIGNUPS_DOMAINS_WHITELIST`, every domain in that list is allowed to create an account no matter what `SIGNUPS_ALLOWED` is set to.
If you have checked those settings and still have an issue, i suggest to open a new topic at the Discussions and provide a support string which you can generate via the `/admin/diagnostics` page.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Zuwizara on GitHub (Jan 29, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/830
Subject of the issue
Signups are still possible after disabling it via Environment and/or admin interface. I tried both Environment-var and the admin interface, always restarted the container after disabling, however im still able to create sign up new user on the Login Page. Could someone verify if this is a problem in my deployment or a bug?
Your environment
Steps to reproduce
Disable Signup in Admin Interface or via Environment Var, restart the server and sign up with a new email.
Expected behaviour
Signups not possible after disabling them
Actual behaviour
Signups are still possible
Relevant logs
Please tell me which logs i should provide since i do not see anything relevant in the logs i see from the container in portainer.
@bergernetch commented on GitHub (Jan 29, 2020):
Same problem here, same bitwarden_rs version, disabling via env var does not work. It does show up as disabled in the admin interface.
@Latschenharry commented on GitHub (Jan 29, 2020):
Have you tried creating an account. Because the register button will always be there. If signups are disabled, you will only get an error when hitting the sent button.
@Zuwizara commented on GitHub (Jan 29, 2020):
Yes, i always created test users and it was successful
@mprasil commented on GitHub (Jan 29, 2020):
Submitted a PR to hopefully fix this.
@bergernetch commented on GitHub (Jan 29, 2020):
Same here. I would like it when the create button would also be disabled or even better removed.
@dani-garcia commented on GitHub (Jan 29, 2020):
This should be fixed now, sorry about that!
@molnarriso commented on GitHub (Apr 21, 2021):
Hello, I have the same issue. Whitelisting domains for signup works, but disabling signups not, the same as the original poster. My version is 1.20.0, running on Ubuntu with caddy reverse proxy. Tried both env variable and setting it via web admin interface. Admin interface shows "Allow new signups" as false. I can still create new accounts via the "Create Account" button - the account created is actually working.
Is there some log info I can provide ?
@BlackDex commented on GitHub (Apr 21, 2021):
@molnarriso Posting in a closed issue is not very useful.
Besides that, if you have
SIGNUPS_ALLOWED=falseconfigured you can't create an account via the web-vault.There is one exception, and that is if you have configured
SIGNUPS_DOMAINS_WHITELIST, every domain in that list is allowed to create an account no matter whatSIGNUPS_ALLOWEDis set to.If you have checked those settings and still have an issue, i suggest to open a new topic at the Discussions and provide a support string which you can generate via the
/admin/diagnosticspage.