# Disable SIGNUPS strangeness

**URL:** <https://vaultwarden.discourse.group/t/disable-signups-strangeness/667>\
**Category:** Help\
**Created:** [March 2, 2021, 12:56pm UTC](https://vaultwarden.discourse.group/t/disable-signups-strangeness/667 "2021-03-02T12:56:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wim](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@Wim](https://vaultwarden.discourse.group/u/Wim)\
**Post date:** [March 2, 2021, 12:56pm UTC](https://vaultwarden.discourse.group/t/disable-signups-strangeness/667/1 "2021-03-02T12:56:33Z")

</div>

Just another thanks for the great work here. Followed the relevant instructions to get the bitwardenrs server running in a docker using a docker network to connect to a swag docker container (tip: do not publish parts on bitwardenrs). The swag container gets the LE certificates and forwards the subdomain traffic to bitwardenrs.  
The various environment parameters seemed to work as well, with the exception of SIGNUPS\_ALLOWED. Toggling the value of this environment parameter had no effect on the functionality. Finally managed to track it down to the presence of the signups\_domain\_whitelist parameter which negated the setting of the signups\_allowed field.  
Keep up the great work!