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

Doesn't start up after update #1270

New Issue
Closed
opened 2025-11-07 07:02:08 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-07 07:02:08 -06:00
Owner
Copy Link

Originally created by @GoliathLabs on GitHub (May 23, 2022).

Subject of the issue

Deployment environment

  • vaultwarden version: 1.25.0

  • Install method: docker image

  • Clients used:

  • Reverse proxy and version: traefik 2

  • MySQL/MariaDB or PostgreSQL version:

  • Other relevant details:

Steps to reproduce

using my docker-compose.yml

Expected behaviour

Actual behaviour

Doesn't start up. Log does show this

bitwarden-vaultwarden-1       | Error: Rocket configuration extraction from provider failed.
bitwarden-vaultwarden-1       |    >> invalid value string "off", expected true or false
bitwarden-vaultwarden-1       |    >> for key CLI_COLORS
bitwarden-vaultwarden-1       |    >> in `ROCKET_` environment variable(s)
bitwarden-vaultwarden-1       | thread 'main' panicked at 'aborting due to configuration error(s)', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/rocket-0.5.0-rc.2/src/config/config.rs:293:13
bitwarden-vaultwarden-1       | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
bitwarden-vaultwarden-1       | thread 'main' panicked at 'aborting due to configuration error(s)', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/rocket-0.5.0-rc.2/src/config/config.rs:293:13
bitwarden-vaultwarden-1       | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
bitwarden-vaultwarden-1       | Error: Rocket configuration extraction from provider failed.
bitwarden-vaultwarden-1       |    >> invalid value string "off", expected true or false
bitwarden-vaultwarden-1       |    >> for key CLI_COLORS
bitwarden-vaultwarden-1       |    >> in `ROCKET_` environment variable(s)
bitwarden-vaultwarden-1       | thread 'main' panicked at 'aborting due to configuration error(s)', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/rocket-0.5.0-rc.2/src/config/config.rs:293:13
bitwarden-vaultwarden-1       | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
bitwarden-vaultwarden-1       | Error: Rocket configuration extraction from provider failed.
bitwarden-vaultwarden-1       |    >> invalid value string "off", expected true or false
bitwarden-vaultwarden-1       |    >> for key CLI_COLORS
bitwarden-vaultwarden-1       |    >> in `ROCKET_` environment variable(s)
bitwarden-vaultwarden-1       | Error: Rocket configuration extraction from provider failed.
bitwarden-vaultwarden-1       |    >> invalid value string "off", expected true or false
bitwarden-vaultwarden-1       |    >> for key CLI_COLORS
bitwarden-vaultwarden-1       |    >> in `ROCKET_` environment variable(s)

I did go back to 1.24.0 for the time being.

Troubleshooting data

Originally created by @GoliathLabs on GitHub (May 23, 2022). <!-- # ### 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 <!-- Describe your issue here. --> ### 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.25.0 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: docker image * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> * Reverse proxy and version: <!-- if applicable --> traefik 2 * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> * Other relevant details: ### 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? --> using my docker-compose.yml ### Expected behaviour <!-- Tell us what you expected to happen --> ### Actual behaviour <!-- Tell us what actually happened --> Doesn't start up. Log does show this ``` bitwarden-vaultwarden-1 | Error: Rocket configuration extraction from provider failed. bitwarden-vaultwarden-1 | >> invalid value string "off", expected true or false bitwarden-vaultwarden-1 | >> for key CLI_COLORS bitwarden-vaultwarden-1 | >> in `ROCKET_` environment variable(s) bitwarden-vaultwarden-1 | thread 'main' panicked at 'aborting due to configuration error(s)', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/rocket-0.5.0-rc.2/src/config/config.rs:293:13 bitwarden-vaultwarden-1 | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace bitwarden-vaultwarden-1 | thread 'main' panicked at 'aborting due to configuration error(s)', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/rocket-0.5.0-rc.2/src/config/config.rs:293:13 bitwarden-vaultwarden-1 | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace bitwarden-vaultwarden-1 | Error: Rocket configuration extraction from provider failed. bitwarden-vaultwarden-1 | >> invalid value string "off", expected true or false bitwarden-vaultwarden-1 | >> for key CLI_COLORS bitwarden-vaultwarden-1 | >> in `ROCKET_` environment variable(s) bitwarden-vaultwarden-1 | thread 'main' panicked at 'aborting due to configuration error(s)', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/rocket-0.5.0-rc.2/src/config/config.rs:293:13 bitwarden-vaultwarden-1 | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace bitwarden-vaultwarden-1 | Error: Rocket configuration extraction from provider failed. bitwarden-vaultwarden-1 | >> invalid value string "off", expected true or false bitwarden-vaultwarden-1 | >> for key CLI_COLORS bitwarden-vaultwarden-1 | >> in `ROCKET_` environment variable(s) bitwarden-vaultwarden-1 | Error: Rocket configuration extraction from provider failed. bitwarden-vaultwarden-1 | >> invalid value string "off", expected true or false bitwarden-vaultwarden-1 | >> for key CLI_COLORS bitwarden-vaultwarden-1 | >> in `ROCKET_` environment variable(s) ``` I did go back to 1.24.0 for the time being. ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
GiteaMirror commented 2025-11-07 07:02:09 -06:00
Author
Owner
Copy Link

@GoliathLabs commented on GitHub (May 23, 2022):

If you need anything else from me, feel free to ask.

@GoliathLabs commented on GitHub (May 23, 2022): If you need anything else from me, feel free to ask.
GiteaMirror commented 2025-11-07 07:02:09 -06:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub (May 23, 2022):

Do you happen to have the ROCKET_CLI_COLORS env variable defined in the docker compose file? If so, that was for the older version of the Rocket web server and isn't needed anymore. We should probably unset it in code to avoid it crashing the server though.

@dani-garcia commented on GitHub (May 23, 2022): Do you happen to have the `ROCKET_CLI_COLORS` env variable defined in the docker compose file? If so, that was for the older version of the Rocket web server and isn't needed anymore. We should probably unset it in code to avoid it crashing the server though.
GiteaMirror commented 2025-11-07 07:02:10 -06:00
Author
Owner
Copy Link

@GoliathLabs commented on GitHub (May 23, 2022):

Yeah, I did use an old .env file

@GoliathLabs commented on GitHub (May 23, 2022): Yeah, I did use an old .env file
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
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#1270
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?