-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vaultwarden --version
fails with Error loading config
regarding sqlite database dir data
instead of showing version info
#5046
Labels
bug
Something isn't working
Comments
Thanks. The scenario without any config was overlooked in this case. |
BlackDex
added a commit
to BlackDex/vaultwarden
that referenced
this issue
Oct 6, 2024
Since we added the option to show the web-vault version also when running `--version` this causes the config to always be validated. While this is not very bad in general, it could cause the command to quit during the config validation, and not show the version, but also errors. This is probably not very useful for this specific command, unlike the `--backup` for example. To fix this, and preventing the config from being validated, i added an AtomicBool to check if we need to validate the config on first load. This prevents errors, and will just show the Vaultwarden version, and if possible the web-vault version too. Fixes dani-garcia#5046
BlackDex
added a commit
to BlackDex/vaultwarden
that referenced
this issue
Oct 6, 2024
Since we added the option to show the web-vault version also when running `--version` this causes the config to always be validated. While this is not very bad in general, it could cause the command to quit during the config validation, and not show the version, but also errors. This is probably not very useful for this specific command, unlike the `--backup` for example. To fix this, and preventing the config from being validated, i added an AtomicBool to check if we need to validate the config on first load. This prevents errors, and will just show the Vaultwarden version, and if possible the web-vault version too. Fixes dani-garcia#5046 Signed-off-by: BlackDex <black.dex@gmail.com>
dfunkt
pushed a commit
to dfunkt/vaultwarden
that referenced
this issue
Oct 10, 2024
Since we added the option to show the web-vault version also when running `--version` this causes the config to always be validated. While this is not very bad in general, it could cause the command to quit during the config validation, and not show the version, but also errors. This is probably not very useful for this specific command, unlike the `--backup` for example. To fix this, and preventing the config from being validated, i added an AtomicBool to check if we need to validate the config on first load. This prevents errors, and will just show the Vaultwarden version, and if possible the web-vault version too. Fixes dani-garcia#5046 Signed-off-by: BlackDex <black.dex@gmail.com>
BlackDex
added a commit
to BlackDex/vaultwarden
that referenced
this issue
Oct 11, 2024
Since we added the option to show the web-vault version also when running `--version` this causes the config to always be validated. While this is not very bad in general, it could cause the command to quit during the config validation, and not show the version, but also errors. This is probably not very useful for this specific command, unlike the `--backup` for example. To fix this, and preventing the config from being validated, i added an AtomicBool to check if we need to validate the config on first load. This prevents errors, and will just show the Vaultwarden version, and if possible the web-vault version too. Fixes dani-garcia#5046 Signed-off-by: BlackDex <black.dex@gmail.com>
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, SIGNUPS_VERIFY, SIGNUPS_DOMAINS_WHITELIST, INVITATIONS_ALLOWED, ADMIN_TOKEN, SMTP_HOST, SMTP_SECURITY, SMTP_PORT, SMTP_FROM
Vaultwarden Build Version
1.32.1
Deployment method
Manually Extracted from Container Image
Custom deployment method
No response
Reverse Proxy
caddy 2.6.2
Host/Server Operating System
Linux
Operating System Version
Debian GNU/Linux 12 (bookworm)
Clients
Web Vault
Client Version
bw_web_v2024.6.2c
Steps To Reproduce
vaultwarden --version
on the commandlineExpected Result
Output
vaultwarden 1.32.1
This used to work: the
--version
output from the previous version isvaultwarden 1.32.0
Note that
--help
does output the version string, so there is a workaround to getting this info from cmdline for now:Actual Result
Logs
No response
Screenshots or Videos
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: