Disable admin page activates registration for everyone

[CamelT0E]

I would like to disable the admin page. On the Synology you can not set the reverse proxy well, that it is blocked externally.

If the admin page is deactivated (Environments or *.json) this works, but new users can register again. The option that no new users are allowed to register is ignored! After activating the admin page, the new registration block works again!

It would be enough for me to activate the admin interface only if necessary. I didn't find anything about this in the wiki.

[BlackDex]

It can be password protected, so i would suggest to do that.
Also, the admin interface is also brute-force protected, you can even make that more tight if you want so that any wrong attempt is blocked for a long time.

vaultwarden/.env.template

Lines 384 to 387 in 2ad33ec

	## Number of seconds, on average, between admin login requests from the same IP address before rate limiting kicks in.
	# ADMIN_RATELIMIT_SECONDS=300
	## Allow a burst of requests of up to this size, while maintaining the average indicated by `ADMIN_RATELIMIT_SECONDS`.
	# ADMIN_RATELIMIT_MAX_BURST=3

[CamelT0E]

maybe "ADMIN_RATELIMIT" would be interesting in the extended admin pages. "Admin session lifetime" is already available.

[CamelT0E]

Just out of curiosity: is it possible to unlock ADMIN_RATELIMIT manually? Or is this not provided for?

[dani-garcia]

I'm not sure I understand the question, both disabling the admin page and user registrations at the same time is supported, just don't set ADMIN_TOKEN and set SIGNUPS_ALLOWED=false. Wether the admin page is enabled or not is irrelevant to the signups_allowed setting.

Just tested it in my setup and it works just fine.

[CamelT0E]

I tried it again. Registration is no longer possible after complete removal. The admin panel gets the same error message as when the token is disabled with #. Due to this error message, I assumed that the admin page was properly disabled. According to the web interface, it is disabled.

tested with a clean test installation. the error message is confusing.

[BlackDex]

How is that message confusing? It tells you exactly what it is missing.
If there is an error in the config or loading of a file, that isn't visible here.

[tessus]

I commented out the line with a # sign.

There are no comments in JSON, thus adding a # to a line in a json document renders that json file invalid.

[CamelT0E]

@tessus,
I think you're right.
The problem is solved for me with this.
Thanks to all the helpers for the quick help!

[BlackDex]

Currently it seems to fail silently, so that is probably not something we want.
What it does then, is it falls back to the env variables.

[CamelT0E]

.env does not work in vaultwarden docker?
With this, you could quickly control some environments that are not available in the admin panel.
This would make it possible to activate/deactivate parts without editing the container. A reboot should be enough.

[BlackDex]

Restarting Vaultwarden or the container should be enough.

[CamelT0E]

.but env is apparently not being read. I've added the ones for a test, the variables for the admin token and web vault. The settings remained without function, and there was nothing to be found in the log either. Which .env was located in the root directory at the *.json & database. Of course, with restart and paused containers.

[BlackDex]

.env needs to be right besides the Vaultwarden binary, or you need to set the correct env variable to point it to an other file.

Without those it will know where to look.

[CamelT0E]

The variables with the .env works.
I have added the following environments in the container. -e ENV_FILE=/data/.env \
With this, I can make the rest of the settings.

Problem solved. Many Thanks 👍