Database migration broken after upgrading to v1.36.0

[thesnallygaster]

Prerequisites

• I have searched the existing Closed AND Open Issues AND Discussions
• I have searched and read the documentation

Vaultwarden Support String

Vaultwarden doesn't start :)

Vaultwarden Build Version

v1.36.0

Deployment method

OS Package (apt, yum/dnf, pacman, apk, nix, ...)

Custom deployment method

Hi, after upgrading to v1.36.0 I get this error during a migration when using mariadb as database backend
[2026-05-04 08:36:28.855][panic][ERROR] thread 'main' panicked at 'Error running migrations: QueryError(DieselMigrationName { name: "2026-03-09-005927_add_archives", version: MigrationVersion("20260309005927") }, DatabaseError(Unknown, "Can't create table `vaultwarden`.`archives` (errno: 150 \"Foreign key constraint is incorrectly formed\")"))': src/db/mod.rs:501

Reverse Proxy

haproxy 3.0.11-1+deb13u2

Host/Server Operating System

Linux

Operating System Version

No response

Clients

Web Vault

Client Version

No response

Steps To Reproduce

1. Upgrade to v1.36.0

Expected Result

Upgrade works

Actual Result

Migration fails

Logs

[2026-05-04 08:36:28.855][panic][ERROR] thread 'main' panicked at 'Error running migrations: QueryError(DieselMigrationName { name: "2026-03-09-005927_add_archives", version: MigrationVersion("20260309005927") }, DatabaseError(Unknown, "Can't create table `vaultwarden`.`archives` (errno: 150 \"Foreign key constraint is incorrectly formed\")"))': src/db/mod.rs:501

Screenshots or Videos

No response

Additional Context

No response

[BlackDex]

You probably have some collation or charset issues.
See: https://github.com/dani-garcia/vaultwarden/wiki/Using-the-MariaDB-%28MySQL%29-Backend#foreign-key-errors-collation-and-charset

[thesnallygaster]

Thanks for guiding me in the right direction, it was a collation issue, dunno how that wasn't a problem for me earlier.
Sorry for littering the issues.