mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #6602] DatabaseError(Unknown, "Can't create table vaultwarden.sso_users (errno: 150 \"Foreign key constraint is incorrectly formed\")")) #2477
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#2477
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 @DMJoh on GitHub (Dec 28, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6602
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
v1.35.0
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Caddy v2.10.2
Host/Server Operating System
Linux
Operating System Version
Debian Trixie 13.2
Clients
Web Vault
Client Version
2025.7.0
Steps To Reproduce
Install the latest version and start.
The server fails to start due to database migration error.
Expected Result
VW should be up and running.
Actual Result
After upgrading to v 1.35.0, Vaultwarden with MariaDB is throwing a migration error and is failing to start.
Logs
Screenshots or Videos
No response
Additional Context
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
I have reverted to 1.34.3 for now and is working as expected.
@BlackDex commented on GitHub (Dec 28, 2025):
This is already resolved in testing/main.
@stefan0xC commented on GitHub (Dec 28, 2025):
@DMJoh If I recall correctly some users had problems like that before when upgrading. Can you make sure that the collation and charset of your database and tables are correctly set?
@BlackDex Are you sure? The only difference between the latest release (1.35.0) and
mainis an update of theCargo.lockfile (github.com/dani-garcia/vaultwarden@eb2a56aea1).@BlackDex commented on GitHub (Dec 28, 2025):
@stefan0xC, @DMJoh is using 1.34.3, and it should be solved in 1.35.0 actually.
@stefan0xC commented on GitHub (Dec 28, 2025):
If you check the logs @DMJoh was using
1.35.0. (1.34.3does not have that migration yet.)@DMJoh commented on GitHub (Dec 28, 2025):
@stefan0xC @BlackDex With 1.35.0, Vaultwarden was not starting. So I reverted back to 1.34.3 to get the diagnostics.
Collation and charset from my VW db
@stefan0xC commented on GitHub (Dec 28, 2025):
@DMJoh Not sure if that is the cause of the issue but I see a default collation of
utf8mb4_general_cibut a collation ofutf8mb4_unicode_cifor the tables, so you might want to change the default collation to the latter?@DMJoh commented on GitHub (Dec 28, 2025):
@stefan0xC Very well, that did the trick. Now I can see vaultwarden up and healthy.
Thank you so much for the quick responses.