Originally created by @Ortof on GitHub (Jan 26, 2025).
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
Go to '...'
Click on '....'
Scroll down to '....'
Click on '...'
Etc '...'
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
[2025-01-26 19:16:53.172][vaultwarden::util][WARN] Can't connect to database, retrying: Failed to create pool.
[CAUSE] Error(None,)
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:
[2025-01-26 19:16:53.172][vaultwarden::util][WARN] Can't connect to database, retrying: Failed to create pool.
[CAUSE] Error(None,)
[2025-01-26 19:16:53.172][vaultwarden::util][WARN] Can't connect to database, retrying: Failed to create pool.
[CAUSE] Error(None,)
Additional Information:
Vaultwarden is deployed via Docker using Portainer.
This issue only occurs with version 1.33.0. Version 1.32.7 works fine with the same setup.
No changes were made to the database configuration or Docker volumes.
The docker-compose.yml file has not been modified since the update.
Originally created by @Ortof on GitHub (Jan 26, 2025).
### 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
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. Click on '...'
5. Etc '...'
### 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
```text
[2025-01-26 19:16:53.172][vaultwarden::util][WARN] Can't connect to database, retrying: Failed to create pool.
[CAUSE] Error(None,)
```
### 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:
```
[2025-01-26 19:16:53.172][vaultwarden::util][WARN] Can't connect to database, retrying: Failed to create pool.
[CAUSE] Error(None,)
```
**Vaultwarden Version**: 1.33.0
**Docker Version**: 20.10.17
**Portainer Version**: 2.21.5
**Ubuntu Version**: 24.04.1 LTS
**Full Log**:
```
[2025-01-26 19:16:53.172][vaultwarden::util][WARN] Can't connect to database, retrying: Failed to create pool.
[CAUSE] Error(None,)
```
**Additional Information**:
- Vaultwarden is deployed via Docker using Portainer.
- This issue only occurs with version 1.33.0. Version 1.32.7 works fine with the same setup.
- No changes were made to the database configuration or Docker volumes.
- The `docker-compose.yml` file has not been modified since the update.
GiteaMirror
added the bug label 2026-03-07 20:39:15 -06:00
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.
@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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Ortof on GitHub (Jan 26, 2025).
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.