Vaultwarden keeps crashing after crash/update

Here is the last log, ive fixed this with chatgpt a few times but it keeps happening so im looking for a lasting solution.

[2026/04/10 10:48:15] (ERROR) app_lifecycle.compose_action():58 - Failed ‘up’ action for ‘vaultwarden’ app: Container ix-vaultwarden-permissions-1 Creating\n Container ix-vaultwarden-permissions-1 Created\n Co
ntainer ix-vaultwarden-postgres_upgrade-1 Creating\n Container ix-vaultwarden-postgres_upgrade-1 Created\n Container ix-vaultwarden-postgres-1 Creating\n Container ix-vaultwarden-postgres-1 Created\n Containe
r ix-vaultwarden-vaultwarden-1 Creating\n Container ix-vaultwarden-vaultwarden-1 Created\n Container ix-vaultwarden-permissions-1 Starting\n Container ix-vaultwarden-permissions-1 Started\n Container ix-vault
warden-permissions-1 Waiting\n Container ix-vaultwarden-permissions-1 Exited\n Container ix-vaultwarden-postgres_upgrade-1 Starting\n Container ix-vaultwarden-postgres_upgrade-1 Started\n Container ix-vaultwa
rden-postgres_upgrade-1 Waiting\n Container ix-vaultwarden-permissions-1 Waiting\n Container ix-vaultwarden-permissions-1 Exited\n Container ix-vaultwarden-postgres_upgrade-1 Exited\n Container ix-vaultwarden
-postgres-1 Starting\nError response from daemon: failed to set up container networking: endpoint with name ix-vaultwarden-postgres-1 already exists in network ix-vaultwarden_ix-internal-vaultwarden-net\n

I have it installed through the truenas appstore.

That’s just a docker error. You’d have to check what is happening on the truenas side that is giving you that error.

Looks like there are two postgres containers maybe (one normal, one “upgrade”) and there is some hangup there.