SIGNUPS_ALLOWED=false doesn't work for me.

[luckow]

Someone else with this?:

• env-sh file = export SIGNUPS_ALLOWED=false
• restarting the app
• https://vaultwarden.example.org with a link Create account
• Filling out the form & submitting ends up with an email

Thank you for creating an account at https://vaultwarden.example.org You may now log in with your new account.
If you did not request to create an account, you can safely ignore this email. 

And yes: It looks like a fully functional account of a Vaultwarden instance where the admin has decided not to allow registrations.

[jdaviescoates]

@luckow said in SIGNUPS_ALLOWED=false doesn't work for me.:

https://vaultwarden.example.org with a link Create account

I don't follow this step/ what you are talking about here?

I just visited my own instance and don't see any Create account option.

[jdaviescoates]

This post is deleted!

[jdaviescoates]

But, I'm also very confused, because I don't have the option enable in my instance!

I just have this with it still all commented out

# Export bitwarden rs environment variables here to ovveride the defaults

#export SIGNUPS_ALLOWED=false
#export INVITATIONS_ALLOWED=true

# To only allow users with the same email domain as where the app is installed:
#export SIGNUPS_DOMAINS_WHITELIST=ud.coop

export LOG_LEVEL=info

[andreasdueren]

Interesting, I can reproduce this. Looks like Vaultwarden will neither respect the config in the config file, env or admin backend.

[jdaviescoates]

@andreasdueren but how have I manged to not have that link showing on my instance?!?

[andreasdueren]

@jdaviescoates Anyhting in the config.json?

[jdaviescoates]

@andreasdueren I do indeed have this in there:

"signups_allowed": false,

So perhaps that's it!

I was just trying to login to /admin/ to see what I could see there too, but using the admin token in my config.json doesn't seem to be working for me

[jdaviescoates]

said in SIGNUPS_ALLOWED=false doesn't work for me.:

I was just trying to login to /admin/ to see what I could see there too, but using the admin token in my config.json doesn't seem to be working for me

Aha, the docs says:

The token to login to the admin page is the password you entered above to generate the ADMIN_TOKEN.

I hadn't spotted that on a quick read!

I managed to login and see this unchecked box there too:

[james]

Hello @luckow
From the Cloudron doc https://docs.cloudron.io/packages/vaultwarden/#users

By default, open registration is enabled. This can be changed via the config variables by editing /app/data/config.json using the File Manager. For example, to disable signup but allow invitations set the variables as below:

 "signups_allowed": false,
  "invitations_allowed": true,> 

Did you try this instead of the env-sh file?

---

Edit: for some reason my post got delayed for multiple minutes. Ignore this.

[jdaviescoates]

@james I guess perhaps this stuff should be remove from the env.sh file in the package given they seemingly don't do anything and lead to this confusion:

# Export bitwarden rs environment variables here to ovveride the defaults

#export SIGNUPS_ALLOWED=false
#export INVITATIONS_ALLOWED=true

# To only allow users with the same email domain as where the app is installed:
#export SIGNUPS_DOMAINS_WHITELIST=ud.coop

export LOG_LEVEL=info

[girish]

I remember fixing this. I guess very old installations (2022) still have the above comment and env variables . https://git.cloudron.io/packages/vaultwarden-app/-/commit/7de942dcc2ae45294b78ec22931fba906e5c64a1

[jdaviescoates]

@girish is it safe to just delete the left over env.sh and/ or is there a reason to keep it for other settings?

[girish]

@jdaviescoates the comment in the package says there are some values that can only be set in env . But I cannot find what they are . AFAICT, it is safe to empty it out.