[Postgresql/DB] Database URL changes not respected #1155

Closed
opened 2026-04-06 01:41:18 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @Crow-Control on 4/18/2024

Subject of the issue

When changing the DATABASE_URL ENV var, the change isn't respected and the application still tries to access the old url.
This is primarily important when database passwords change.

Having this as an env-var gives the impression it does more than just set it at first boot.

Deployment environment

Docker/Helm/Kubernetes, irrelevant (container feature)

  • vaultwarden version:
    Latest (All?)
  • Install method:

  • MySQL/MariaDB or PostgreSQL version:
    Postgresql, should alson happen with MariaDB

  • Other relevant details:

Steps to reproduce

Expected behaviour

  • Install in what-ever way you fancy
  • Change database password on the side of the DB
  • Change DATABASE_URL env var to match the new password
  • Cannot connect

Actual behaviour

  • It should respect the new env var

Troubleshooting data

Might be related to using the admin interface afterwards or not, this I would need to verify

*Originally created by @Crow-Control on 4/18/2024* ### Subject of the issue When changing the DATABASE_URL ENV var, the change isn't respected and the application still tries to access the old url. This is primarily important when database passwords change. Having this as an env-var gives the impression it does more than just set it at first boot. ### Deployment environment Docker/Helm/Kubernetes, irrelevant (container feature) <!-- 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: Latest (All?) <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: * MySQL/MariaDB or PostgreSQL version: Postgresql, should alson happen with MariaDB * 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? --> ### Expected behaviour <!-- Tell us what you expected to happen --> - Install in what-ever way you fancy - Change database password on the side of the DB - Change DATABASE_URL env var to match the new password - Cannot connect ### Actual behaviour - It should respect the new env var ### Troubleshooting data Might be related to using the admin interface afterwards or not, this I would need to verify
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/vaultwarden#1155