[GH-ISSUE #384] The SIGNUPS_ALLOWED variable is ignored. #223

New issue

Closed

opened 2026-03-03 01:26:54 +03:00 by kerem · 5 comments

kerem commented

2026-03-03 01:26:54 +03:00

Owner

Originally created by @JacobCZ on GitHub (Feb 5, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/384

When I try to run the docker image with the SIGNUPS_ALLOWED set to false like so:

docker run -d --name bitwarden \                                                                                                                                      
  2   -e SIGNUPS_ALLOWED=false \                                                                                                                                          
  3   -e INVITATIONS_ALLOWED=false \                                                                                                                                      
  5   -v /bw-data/:/data/ \                                                                                                                                               
  6   -p 8666:80 \                                                                                                                                                        
  7   mprasil/bitwarden:latest

the signup button is still there and users can still create an account.

I'm running BW version 2.8.0 on Ubuntu 18.04.1 (4.15.0-34) and docker version 18.09.1

Originally created by @JacobCZ on GitHub (Feb 5, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/384 When I try to run the docker image with the SIGNUPS_ALLOWED set to false like so: ``` docker run -d --name bitwarden \ 2 -e SIGNUPS_ALLOWED=false \ 3 -e INVITATIONS_ALLOWED=false \ 5 -v /bw-data/:/data/ \ 6 -p 8666:80 \ 7 mprasil/bitwarden:latest ``` the signup button is still there and users can still create an account. I'm running BW version 2.8.0 on Ubuntu 18.04.1 (4.15.0-34) and docker version 18.09.1

kerem

2026-03-03 01:26:54 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-03 01:26:55 +03:00

Author

Owner

@mprasil commented on GitHub (Feb 5, 2019):

Are you sure users can still register? The button won't disappear, because Vault isn't aware of the registration availability, but when you try to register you should get an error response back saying that registrationisn't allowed.

@mprasil commented on GitHub (Feb 5, 2019): Are you sure users can still register? The button won't disappear, because Vault isn't aware of the registration availability, but when you try to register you should get an error response back saying that registrationisn't allowed.

kerem commented

2026-03-03 01:26:55 +03:00

Author

Owner

@JacobCZ commented on GitHub (Feb 5, 2019):

@mprasil oooooh! My bad, sorry. 🙂

@JacobCZ commented on GitHub (Feb 5, 2019): @mprasil oooooh! My bad, sorry. :slightly_smiling_face:

kerem commented

2026-03-03 01:26:55 +03:00

Author

Owner

@Happyfeet01 commented on GitHub (Mar 7, 2019):

Can i run this command on an existing container?

@Happyfeet01 commented on GitHub (Mar 7, 2019): Can i run this command on an existing container?

kerem commented

2026-03-03 01:26:56 +03:00

Author

Owner

@dani-garcia commented on GitHub (Mar 7, 2019):

Yes, you can either stop the container and run it again with the same command but adding -e SIGNUPS_ALLOWED=false to it. Or, if you have the admin panel activated, you can change it from there without restarting.

@dani-garcia commented on GitHub (Mar 7, 2019): Yes, you can either stop the container and run it again with the same command but adding `-e SIGNUPS_ALLOWED=false` to it. Or, if you have the admin panel activated, you can change it from there without restarting.

kerem commented

2026-03-03 01:26:56 +03:00

Author

Owner

@Happyfeet01 commented on GitHub (Mar 8, 2019):

Yes, you can either stop the container and run it again with the same command but adding -e SIGNUPS_ALLOWED=false to it. Or, if you have the admin panel activated, you can change it from there without restarting.

i added the option the docker-compose.yml it works now

@Happyfeet01 commented on GitHub (Mar 8, 2019): > > > Yes, you can either stop the container and run it again with the same command but adding `-e SIGNUPS_ALLOWED=false` to it. Or, if you have the admin panel activated, you can change it from there without restarting. i added the option the docker-compose.yml it works now