1.35.0 database migration error

[bigjaws]

I am running vaultwarden in docker and it is using a mariadb:lts also as a docker container.
After the current update, my vaultwarden does not start anymore and I get the following error in the docker logs.

[2025-12-28 07:48:37.136][panic][ERROR] thread 'main' panicked at 'Error running migrations: QueryError(DieselMigrationName { name: "2024-03-06-170000_add_sso_users", version: MigrationVersion("20240306170000") }, DatabaseError(Unknown, "Can't create table `vaultwarden`.`sso_users` (errno: 150 \"Foreign key constraint is incorrectly formed\")"))': src/db/mod.rs:505
   0: vaultwarden::init_logging::{{closure}}
   1: std::panicking::panic_with_hook
   2: std::panicking::panic_handler::{{closure}}
   3: std::sys::backtrace::__rust_end_short_backtrace
   4: __rustc::rust_begin_unwind
   5: core::panicking::panic_fmt
   6: core::result::unwrap_failed
   7: vaultwarden::db::DbPool::from_config
   8: vaultwarden::main::{{closure}}
   9: vaultwarden::main
  10: std::sys::backtrace::__rust_begin_short_backtrace
  11: main
  12: <unknown>
  13: __libc_start_main
�
  14: _start

[stefan0xC]

Can you make sure that the collation and charset of your database and tables are correctly set? (Cf. #6602 (comment))

[vincentkoevoets]

My error looks like this one, but is a bit different:

/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.35.0                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://github.com/dani-garcia/vaultwarden/discussions or        |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/

[INFO] Using saved config from `data/config.json` for configuration.

[2025-12-29 23:40:39.348][panic][ERROR] thread 'main' panicked at 'Error running migrations: QueryError(DieselMigrationName { name: "2024-03-06-170000_add_sso_users", version: MigrationVersion("20240306170000") }, DatabaseError(Unknown, "Failed to add the foreign key constraint. Missing unique key for constraint 'sso_users_ibfk_1' in the referenced table 'users'"))': src/db/mod.rs:505
   0: vaultwarden::init_logging::{{closure}}
   1: std::panicking::panic_with_hook
   2: std::panicking::panic_handler::{{closure}}
   3: std::sys::backtrace::__rust_end_short_backtrace
   4: __rustc::rust_begin_unwind
   5: core::panicking::panic_fmt
   6: core::result::unwrap_failed
   7: vaultwarden::db::DbPool::from_config
   8: vaultwarden::main::{{closure}}
   9: vaultwarden::main
  10: std::sys::backtrace::__rust_begin_short_backtrace
  11: main
  12: <unknown>
  13: __libc_start_main
  14: _start

Collation and charset are checked and double checked. No dice. Reverting back to 1.34.3 at least starts the container for now.

[stefan0xC]

Collation and charset are checked and double checked. No dice.

Can you share what the collation is?

SELECT DEFAULT_CHARACTER_SET_NAME, DEFAULT_COLLATION_NAME FROM information_schema.SCHEMATA WHERE SCHEMA_NAME = "vaultwarden";
SELECT CHARACTER_SET_NAME, COLLATION_NAME FROM information_schema.`COLUMNS` WHERE TABLE_SCHEMA = "vaultwarden" AND CHARACTER_SET_NAME IS NOT NULL;

[vincentkoevoets]

There we go:

SELECT DEFAULT_CHARACTER_SET_NAME, DEFAULT_COLLATION_NAME FROM information_schema.SCHEMATA WHERE SCHEMA_NAME = "vaultwarden";

DEFAULT_CHARACTER_SET_NAME	DEFAULT_COLLATION_NAME	
utf8mb4	utf8mb4_unicode_ci	

SELECT CHARACTER_SET_NAME, COLLATION_NAME FROM information_schema.`COLUMNS` WHERE TABLE_SCHEMA = "vaultwarden" AND CHARACTER_SET_NAME IS NOT NULL;

CHARACTER_SET_NAME	COLLATION_NAME	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci	
utf8mb4	utf8mb4_unicode_ci