-
-
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 silently falls back to SQLite if DATABASE_URL is invalid #2835
Comments
I've noticed the same beavior and IMO it should not fall back to sqlite, but abend with an error message. |
Where did you configured this? Docker compose file? Custom export? Systemd file. And could you give an example? Without the actual password etc if course. |
As mentioned in the issue, I specified this in my docker-compose file. The issue also contains examples without actual passwords. environment:
- DATABASE_URL="postgresql://user:pwd@host/vaultwarden" Specifying it as |
Thanks for the extra info. But, it indeed should not continue if there is a faulty setting. Thanks for the report. |
instead of creating the parent folders to a sqlite database vaultwarden should just exit. this should fix issues like dani-garcia#2835 when a wrongly configured `DATABASE_URL` falls back to using sqlite
instead of creating the parent folders to a sqlite database vaultwarden should just exit. this should fix issues like dani-garcia#2835 when a wrongly configured `DATABASE_URL` falls back to using sqlite
instead of creating the parent folders to a sqlite database vaultwarden should just exit. this should fix issues like dani-garcia#2835 when a wrongly configured `DATABASE_URL` falls back to using sqlite
instead of creating the parent folders to a sqlite database vaultwarden should just exit. this should fix issues like dani-garcia#2835 when a wrongly configured `DATABASE_URL` falls back to using sqlite
instead of creating the parent folders to a sqlite database vaultwarden should just exit if it does not. this should fix issues like dani-garcia#2835 when a wrongly configured `DATABASE_URL` falls back to using sqlite
instead of creating the parent folders to a sqlite database vaultwarden should just exit if it does not. this should fix issues like dani-garcia#2835 when a wrongly configured `DATABASE_URL` falls back to using sqlite
instead of creating the parent folders to a sqlite database vaultwarden should just exit if it does not. this should fix issues like dani-garcia#2835 when a wrongly configured `DATABASE_URL` falls back to using sqlite
instead of creating the parent folders to a sqlite database vaultwarden should just exit if it does not. this should fix issues like #2835 when a wrongly configured `DATABASE_URL` falls back to using sqlite
Should be resolved via #2873 already. |
Subject of the issue
When an invalid
DATABASE_URL
is specified, e.g. with a typo such aspostgreql://user:pwd@host
or with quotes like"postgresql://user:pwd@host"
, Vaultwarden silently falls back to using the SQLite database without logging any errors or warnings.Deployment environment
Used image is
vaultwarden/server:1.26.0
Steps to reproduce
I started vaultwarden via a docker-compose file with the
DATABASE_URL
variable setExpected behaviour
If an invalid
DATABASE_URL
is specified, Vaultwarden should either log an error or a warning along the lines of "Failed to parse DATABASE_URL, falling back to SQLite"Actual behaviour
Vaultwarden starts regularly and runs migrations against an SQLite database.
The text was updated successfully, but these errors were encountered: