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

The SIGNUPS_ALLOWED variable is ignored. #3862

New Issue
Closed
opened 2026-03-07 19:17:15 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-03-07 19:17:15 -06:00
Owner
Copy Link

Originally created by @JacobCZ on GitHub (Feb 5, 2019).

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). 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
GiteaMirror added the question label 2026-03-07 19:17:15 -06:00
GiteaMirror commented 2026-03-07 19:17:16 -06:00
Author
Owner
Copy Link

@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.
GiteaMirror commented 2026-03-07 19:17:16 -06:00
Author
Owner
Copy Link

@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:
GiteaMirror commented 2026-03-07 19:17:16 -06:00
Author
Owner
Copy Link

@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?
GiteaMirror commented 2026-03-07 19:17:16 -06:00
Author
Owner
Copy Link

@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.
GiteaMirror commented 2026-03-07 19:17:17 -06:00
Author
Owner
Copy Link

@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
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 question
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#3862
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?