mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #5046] vaultwarden --version fails with Error loading config regarding sqlite database dir data instead of showing version info #2061
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2061
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @gavinbeatty on GitHub (Oct 4, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/5046
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 --versionon the commandlineExpected Result
Output
vaultwarden 1.32.1This used to work: the
--versionoutput from the previous version isvaultwarden 1.32.0Note that
--helpdoes 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
@BlackDex commented on GitHub (Oct 4, 2024):
Thanks. The scenario without any config was overlooked in this case.