Vaultwarden app fail to start after update

TrueNAS General
1

Hi guys,

I need a bit of help to get the vaultwarden app starting again. I’m on Truenas Scale 1.3.22, and today I updated the few apps, one of them been the vaultwarden, after the update, the app will not start, i stops at 20% and return an error “[EFAULT] Failed ‘up’ action for ‘vaultwarden’ app. Please check /var/log/app_lifecycle.log for more details”

The last log data, makes no sense to me, I tried to restart the server, with no luck, I tried to roll back, but it says It can’t if the app is in stop mode. Also I tried to change from Postgres 15 to 17, if I change to 17 it goes to 20% then the status changes to Crashed.

Before I mess any more with it and possible damage it beyond recover, I thought to ask you guys, can you please help me repair the app or reinstall and import the data back.

For Postgres 15 I get this error:

[2025/11/29 23:17:10] (ERROR) app_lifecycle.compose_action():56 - Failed 'up' action for 'vaultwarden' app: postgres Pulling \n 8e44f01296e3 Already exists \n e27fe9045e2b Pulling fs layer \n 77e540bb81f0 Pulling fs layer \n 20531b75eda0 Pulling fs layer \n 553f3a8e3826 Pulling fs layer \n 562d202602f0 Pulling fs layer \n 3aa4d1912ce6 Pulling fs layer \n daa8c11b5a24 Pulling fs layer \n c95cceb4e496 Pulling fs layer \n 3582aa66cda9 Pulling fs layer \n 63cd415ea828 Pulling fs layer \n a3b536294bc3 Pulling fs layer \n 45fbe811544d Pulling fs layer \n be6ab0a595e3 Pulling fs layer \n 553f3a8e3826 Waiting \n 562d202602f0 Waiting \n 3aa4d1912ce6 Waiting \n c95cceb4e496 Waiting \n daa8c11b5a24 Waiting \n 3582aa66cda9 Waiting \n 63cd415ea828 Waiting \n a3b536294bc3 Waiting \n 45fbe811544d Waiting \n be6ab0a595e3 Waiting \n e27fe9045e2b Downloading \n e27fe9045e2b Retrying in 5 seconds \n 20531b75eda0 Downloading \n 20531b75eda0 Retrying in 5 seconds \n 77e540bb81f0 Retrying in 5 seconds \n e27fe9045e2b Retrying in 4 seconds \n 20531b75eda0 Retrying in 4 seconds \n 77e540bb81f0 Retrying in 4 seconds \n e27fe9045e2b Retrying in 3 seconds \n 20531b75eda0 Retrying in 3 seconds \n 77e540bb81f0 Retrying in 3 seconds \n e27fe9045e2b Retrying in 2 seconds \n 20531b75eda0 Retrying in 2 seconds \n 77e540bb81f0 Retrying in 2 seconds \n e27fe9045e2b Retrying in 1 second \n 20531b75eda0 Retrying in 1 second \n 77e540bb81f0 Retrying in 1 second \n e27fe9045e2b Retrying in 10 seconds \n 77e540bb81f0 Downloading \n 77e540bb81f0 Retrying in 10 seconds \n 20531b75eda0 Retrying in 10 seconds \n e27fe9045e2b Retrying in 9 seconds \n 77e540bb81f0 Retrying in 9 seconds \n 20531b75eda0 Retrying in 9 seconds \n e27fe9045e2b Retrying in 8 seconds \n 77e540bb81f0 Retrying in 8 seconds \n 20531b75eda0 Retrying in 8 seconds \n e27fe9045e2b Retrying in 7 seconds \n 77e540bb81f0 Retrying in 7 seconds \n 20531b75eda0 Retrying in 7 seconds \n e27fe9045e2b Retrying in 6 seconds \n 77e540bb81f0 Retrying in 6 seconds \n 20531b75eda0 Retrying in 6 seconds \n e27fe9045e2b Retrying in 5 seconds \n 77e540bb81f0 Retrying in 5 seconds \n 20531b75eda0 Retrying in 5 seconds \n e27fe9045e2b Retrying in 4 seconds \n 77e540bb81f0 Retrying in 4 seconds \n 20531b75eda0 Retrying in 4 seconds \n e27fe9045e2b Retrying in 3 seconds \n 77e540bb81f0 Retrying in 3 seconds \n 20531b75eda0 Retrying in 3 seconds \n e27fe9045e2b Retrying in 2 seconds \n 77e540bb81f0 Retrying in 2 seconds \n 20531b75eda0 Retrying in 2 seconds \n e27fe9045e2b Retrying in 1 second \n 77e540bb81f0 Retrying in 1 second \n 20531b75eda0 Retrying in 1 second \nerror pulling image configuration: download failed after attempts=6: dial tcp 172.64.66.1:443: i/o timeout\n

For Postgres 17 I get this error:

[2025/11/29 23:36:38] (ERROR) app_lifecycle.compose_action():56 - Failed 'up' action for 'vaultwarden' app:  Network ix-vaultwarden_default  Creating\n Network ix-vaultwarden_default  Created\n Container ix-vaultwarden-permissions-1  Creating\n Container ix-vaultwarden-permissions-1  Created\n Container 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 Container 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-vaultwarden-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-vaultwarden-permissions-1  Waiting\n Container ix-vaultwarden-postgres_upgrade-1  Waiting\n Container ix-vaultwarden-permissions-1  Exited\n Container ix-vaultwarden-postgres_upgrade-1  service "postgres_upgrade" didn't complete successfully: exit 1\nservice "postgres_upgrade" didn't complete successfully: exit 1\n
2

OK,

I got it fixed. Since, I have seen some time errors. I put the server on a vpn and with the vpn on it deploys and its running fine. So it must be something from the isp

3

Update-related failures like this often trace back to a missing environment variable or a permission change inside the app’s dataset, and I’ve hit similar issues after container updates. I like checking the logs first because they usually point directly to the file or library that’s breaking startup. Resetting permissions or reapplying the config often brings Vaultwarden back without needing a full reinstall.