Vikunja 1.22.0 - app fails to start after update (migration error)

[archos]

Hi,

I tried updating the Vikunja package to version 1.22.0 (Vikunja 2.2.0), but the app fails to start after the update.

The log shows the same error on every startup:

Migration failed: migration 20260224215050 failed: pq: column "project_id" of relation "webhooks" does not exist

The app keeps retrying but never becomes healthy (healthcheck EHOSTUNREACH on port 3456). I had to roll back using the Cloudron backup restore.

I also find it strange that package 1.22.0 was published 19 days ago, but I only received the update notification today. Is that expected behavior or is there an issue with update notifications?

Thank you so much for your help.

[nebulon]

This sounds like some database migration didn't run. Can you open a webterminal into the app and in the /app/data folder, run gosu cloudron:cloudron /usr/bin/vikunja migrate. If this fixes it I think we have to add this to the start.sh then.

[archos]

@nebulon said:

gosu cloudron:cloudron /usr/bin/vikunja migrate

Thank you for your response. I tried your suggestion. After updating to 1.22.0, the app keeps crashing on startup with the same error. Here are the full logs:

Mar 23 18:37:57 ==> Updating OIDC configuration
Mar 23 18:37:57 time=2026-03-23T17:37:57.342Z level=INFO msg="Using config file: /app/data/config.yml"
Mar 23 18:37:57 time=2026-03-23T17:37:57.343Z level=INFO msg="Running migrations…"
Mar 23 18:37:57 time=2026-03-23T17:37:57.360Z level=ERROR msg="Migration failed: migration 20260224215050 failed: pq: column \"project_id\" of relation \"webhooks\" does not exist"
Mar 23 18:37:58 time=2026-03-23T17:37:58.108Z level=INFO msg="Running migrations…"
Mar 23 18:37:58 time=2026-03-23T17:37:58.130Z level=ERROR msg="Migration failed: migration 20260224215050 failed: pq: column \"project_id\" of relation \"webhooks\" does not exist"
Mar 23 18:37:59 ==> Changing ownership
Mar 23 18:37:59 ==> Starting Vikunja
Mar 23 18:37:59 ==> Updating OIDC configuration
Mar 23 18:37:59 time=2026-03-23T17:37:59.320Z level=INFO msg="Running migrations…"
Mar 23 18:37:59 time=2026-03-23T17:37:59.337Z level=ERROR msg="Migration failed: migration 20260224215050 failed: pq: column \"project_id\" of relation \"webhooks\" does not exist"
Mar 23 18:38:01 ==> Changing ownership
Mar 23 18:38:01 ==> Starting Vikunja
Mar 23 18:38:01 ==> Updating OIDC configuration
Mar 23 18:38:01 time=2026-03-23T17:38:01.431Z level=INFO msg="Using config file: /app/data/config.yml"
Mar 23 18:38:01 time=2026-03-23T17:38:01.432Z level=INFO msg="Running migrations…"
Mar 23 18:38:01 time=2026-03-23T17:38:01.463Z level=ERROR msg="Migration failed: migration 20260224215050 failed: pq: column \"project_id\" of relation \"webhooks\" does not exist"
Mar 23 18:38:25 ==> Changing ownership
Mar 23 18:38:25 ==> Starting Vikunja
Mar 23 18:38:25 ==> Updating OIDC configuration
Mar 23 18:38:25 time=2026-03-23T17:38:25.421Z level=INFO msg="Running migrations…"
Mar 23 18:38:25 time=2026-03-23T17:38:25.452Z level=ERROR msg="Migration failed: migration 20260224215050 failed: pq: column \"project_id\" of relation \"webhooks\" does not exist"

I then enabled repair mode and ran the migration manually in the web terminal:

gosu cloudron:cloudron /usr/bin/vikunja migrate

Result:

time=2026-03-23T17:37:06.471Z level=INFO msg="Using config file: /app/data/config.yml"
time=2026-03-23T17:37:06.471Z level=INFO msg="Running migrations…"
time=2026-03-23T17:37:06.490Z level=ERROR msg="Migration failed: migration 20260224215050 failed: pq: column \"project_id\" of relation \"webhooks\" does not exist"

Same error — the migration fails both on startup and when run manually.

[joseph]

I think https://github.com/go-vikunja/vikunja/issues/2431 . Can you see if the workaround there solves it?

[archos]

The manual fix worked for me. I ran the following in the web terminal (repair mode):

psql $CLOUDRON_POSTGRESQL_URL

ALTER TABLE webhooks ADD COLUMN IF NOT EXISTS project_id bigint NULL;
INSERT INTO migration (id) VALUES ('20260224215050');
\q

After restarting the app, migrations ran successfully and Vikunja 2.2.0 is up and running.

Thanks for the help!