WEB_VAULT_ENABLED can not be changed from ENV_FILE, but it is implied that it can be #1932

Closed
opened 2026-02-05 02:16:13 +03:00 by OVERLORD · 0 comments
Owner

Originally created by @slonkazoid on GitHub (Jun 5, 2024).

Subject of the issue

WEB_VAULT_ENABLED can not be changed from ENV_FILE, but it is implied that it can be

Deployment environment

  • vaultwarden version: 1.30.5-r2
  • Install method: apk add vaultwarden vaultwarden-web-vault
  • Clients used: not applicable
  • Reverse proxy and version: Caddy 2.6.2
  • MySQL/MariaDB or PostgreSQL version: postgresql 16.3
  • Other relevant details: not applicable

Steps to reproduce

  1. Install vaultwarden and the web vault
  2. Set WEB_VAULT_ENABLED to true in ENV_FILE
  3. Go to /admin/diagnostics
  4. "Web Vault is disabled"

Expected behaviour

It should be more clear that you can not enable the web vault from the env file,
or alternatively, it should let you enable the web vault from the env file.

Actual behaviour

The web vault feature is disabled even if you set the option, and you are not told why.

Troubleshooting data

not applicable

Originally created by @slonkazoid on GitHub (Jun 5, 2024). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue `WEB_VAULT_ENABLED` can not be changed from `ENV_FILE`, but it is implied that it can be ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.30.5-r2 * Install method: apk add vaultwarden vaultwarden-web-vault * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> not applicable * Reverse proxy and version: <!-- if applicable --> Caddy 2.6.2 * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> postgresql 16.3 * Other relevant details: not applicable ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> 1. Install vaultwarden and the web vault 2. Set `WEB_VAULT_ENABLED` to `true` in `ENV_FILE` 3. Go to /admin/diagnostics 4. "Web Vault is disabled" ### Expected behaviour <!-- Tell us what you expected to happen --> It should be more clear that you can not enable the web vault from the env file, or alternatively, it should let you enable the web vault from the env file. ### Actual behaviour <!-- Tell us what actually happened --> The web vault feature is disabled even if you set the option, and you are not told why. ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> not applicable
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1932