Vaultwarden error after image upgrade: "Referencing column 'user_uuid' and referenced column 'uuid' in foreign key constraint 'archives_ibfk_1' are incompatible."
-
I assume this may be more of Vaultwarden issue than a Cloudron one but I wanted to say the recent image update (https://forum.cloudron.io/topic/2546/vaultwarden-package-updates/79?_=1778039394241) seems to have broken Vaultwarden, requiring me to restore from backup.
May 05 20:47:32 => Exporting env vars expected by Vaultwarden May 05 20:47:32 => Starting Bitwarden May 05 20:47:32 /--------------------------------------------------------------------\ May 05 20:47:32 | Starting Vaultwarden | May 05 20:47:32 |--------------------------------------------------------------------| May 05 20:47:32 | This is an *unofficial* Bitwarden implementation, DO NOT use the | May 05 20:47:32 | official channels to report bugs/features, regardless of client. | May 05 20:47:32 | Send usage/configuration questions or feature requests to: | May 05 20:47:32 | https://github.com/dani-garcia/vaultwarden/discussions or | May 05 20:47:32 | https://vaultwarden.discourse.group/ | May 05 20:47:32 | Report suspected bugs/issues in the software itself at: | May 05 20:47:32 | https://github.com/dani-garcia/vaultwarden/issues/new | May 05 20:47:32 \--------------------------------------------------------------------/ May 05 20:47:32 2026-05-06T03:47:32Z May 05 20:47:32 [INFO] Using saved config from `/app/data/config.json` for configuration. May 05 20:47:32 2026-05-06T03:47:32Z May 05 20:47:32 [2026-05-06 03:47:32.167][panic][ERROR] thread 'main' panicked at 'Error running migrations: QueryError(DieselMigrationName { name: "2026-03-09-005927_add_archives", version: MigrationVersion("20260309005927") }, DatabaseError(Unknown, "Referencing column 'user_uuid' and referenced column 'uuid' in foreign key constraint 'archives_ibfk_1' are incompatible."))': src/db/mod.rs:501 May 05 20:47:32 0: vaultwarden::init_logging::{{closure}} May 05 20:47:32 1: std::panicking::panic_with_hook May 05 20:47:32 2: std::panicking::panic_handler::{closure#0} May 05 20:47:32 3: std::sys::backtrace::__rust_end_short_backtrace::<std::panicking::panic_handler::{closure#0}, !> May 05 20:47:32 4: __rustc::rust_begin_unwind May 05 20:47:32 5: core::panicking::panic_fmt May 05 20:47:32 6: core::result::unwrap_failed May 05 20:47:32 7: vaultwarden::db::DbPool::from_config May 05 20:47:32 8: vaultwarden::main::{{closure}} May 05 20:47:32 9: vaultwarden::main May 05 20:47:32 10: std::sys::backtrace::__rust_begin_short_backtrace May 05 20:47:32 11: main May 05 20:47:32 12: <unknown> May 05 20:47:32 13: __libc_start_main May 05 20:47:32 14: _startAny ideas on this one?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login