mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #5463] Database connection bug after updating to Vaultwarden 1.33.0 #2158
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#2158
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 @Ortof on GitHub (Jan 26, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/5463
Vaultwarden Support String
Unfortunately, I am unable to access the /admin/diagnostics page or generate the support string as the Vaultwarden container is not starting. I don't have the necessary access to the relevant directory to retrieve the string manually.
Vaultwarden Build Version
v1.33.0
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
lscr.io/linuxserver/swag:latest
Host/Server Operating System
Linux
Operating System Version
24.04.1 LTS
Clients
Browser Extension, Web Vault, Android
Client Version
No response
Steps To Reproduce
Expected Result
Expected Result:
Vaultwarden should start correctly and connect to the database without any issues. The service should be accessible via the web interface to generate the support string and access all features.
Actual Result
Actual Result:
Vaultwarden fails to connect to the database, and the container fails to start. The log shows the following error:
Logs
Screenshots or Videos
No response
Additional Context
Since updating Vaultwarden to version 1.33.0, I'm encountering an issue during the service startup. The application fails to connect to the database and throws the following error:
Vaultwarden Version: 1.33.0
Docker Version: 20.10.17
Portainer Version: 2.21.5
Ubuntu Version: 24.04.1 LTS
Full Log:
Additional Information:
docker-compose.ymlfile has not been modified since the update.@BlackDex commented on GitHub (Jan 26, 2025):
I think it has something to do with something else then Vaultwarden.
Maybe some security settings? Since nothing changed between 1.32.7 and 1.33.0 regarding the database connection.
The message states it can't connect. So either the databases was not up yet, or it somehow doesn't allow it. I would suggest to check the networking connections, the database logs, try to restart docker services.