Cloudron Forum

@murgero Got it, makes sense! No rush at all — really appreciate you working on it. Looking forward to trying it once it’s ready

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!

@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.

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.

@murgero said:

I actually already have that packaged! though it needs an update for the latest version

That’s great to hear! I’d definitely be interested once it’s updated to the latest version. I’ve been testing it on another VPS and it works without any issues — it’s a great solution for a single user.

@murgero Hi, would it be possible to package GoToSocial? It would be great to have it available on Cloudron.

The issue was resolved by manually setting the monospace font in Firefox (about:config).

Previously, a different font was being used. After forcing "Noto Sans Mono", everything works correctly.

I'm not sure why it changed on its own.

Sorry for the confusion — it looks like this is not a Cloudron issue.

I tested the web terminal in Vivaldi and the font looks normal there.

So it seems to be related to Firefox on my system rather than Cloudron itself.

I am using Firefox on Arch Linux.

The default monospace font on my system is Noto Sans Mono.

Output of fc-match monospace:
NotoSansMono-Regular.ttf: "Noto Sans Mono" "Regular"

I also have several other monospace fonts installed (Meslo Nerd Font Mono, FiraCode Nerd Font Mono, DejaVu Sans Mono, Liberation Mono, etc.), but the default monospace resolves to Noto Sans Mono.

Before updating Cloudron to version 9.1.3 the font in the web terminal was fine and easy for me to read.

After the update it changed to a different monospace font which is harder for me to read. I will also try testing it in another browser.

After updating Cloudron to version 9.1.3, I noticed that the font in the web terminal inside applications has changed.

Is there any way to change the font or configure a different one?

Unfortunately, the new font is quite hard for me to read. The previous one worked much better for me.

Small update from my side.

I contacted Spamhaus through their ticket system and after communicating with them it seems everything is now resolved and the IP has been removed from the blacklist. Emails are working normally again.

Sorry for the false alarm and thank you for your help and responses. I did notice that occasionally I still see the error that was present in the previous version, so I will keep

After further investigation it seems that this is not a Cloudron bug, but an actual listing of the server IP on a blacklist.

I checked the mail server logs on the Cloudron host in:

/home/yellowtent/platformdata/logs/mail/app.log
/home/yellowtent/platformdata/logs/mail/app.log.1

I do not see any signs of a compromised server or bulk spam activity. The logs mainly contain normal system notifications and failed SMTP authentication attempts from random internet bots.

At the moment I do not see any evidence that the server is compromised or that it is sending spam.

Is it possible that I am looking in the wrong place? Are there any other Cloudron logs related to outgoing mail or postfix that I should check?

Both today – sometimes it’s just one, sometimes both.​​​​​​​​​​​​​​​​

Hi,
Cloudron UI reports my IP as listed on SpamHaus, but check.spamhaus.org shows no issues for my hostname.
If I’m not mistaken, this was already addressed in an older release. I’m on Ubuntu 24.04 with the latest version of Cloudron.
The impact is real – some mail servers are rejecting outbound mail from my server with error 554 5.7.1. MX, DKIM, SPF, DMARC and PTR records are all green.
Is anyone else experiencing this on Ubuntu 24.04 + latest Cloudron? Thanks.

New documents work without any issues, but there is a problem with older documents.

After the latest update, I managed to open an old document by right-clicking on it and selecting Create copy. The created copy then opens normally.

Maybe this can help someone as a temporary workaround until the bug is fully fixed.

Hi, tested on Firefox 148.0 on Arch Linux and Safari on iOS. Issue persists in a private/incognito window with no extensions. Older documents still fail to open.

Hi, thanks for the update. The new package seems to fix the issue for new documents, but older documents still fail to open with the same error.

Hi, we have the same issue. Confirmed on both Firefox and Chrome.
curl -I shows the root cause:

GET /extensions.js?ver=2026.2.0-1772167481346
→ 301 redirect to http://<redacted>/extensions.js/?ver=...

Content-Security-Policy: Nastavení stránky zablokovalo provedení skriptu (script-src-elem) na http://<redacted>/extensions.js/?ver=2026.2.0-1772167481346, protože porušuje direktivu „script-src 'self' 'unsafe-eval' 'unsafe-inline' resource: https://<redacted>"
Zdroj na adrese "https://<redacted>/extensions.js?ver=2026.2.0-1772167481346" byl zablokován kvůli rozdílnému MIME typu ("text/html") (X-Content-Type-Options: nosniff).
URI zdroje <script> není v tomto dokumentu povolen: „https://<redacted>/extensions.js?ver=2026.2.0-1772167481346".
Uncaught TypeError: can't access property "DocEditor", window.DocsAPI is undefined
    startOO https://<redacted>/common/onlyoffice/inner.js?ver=2026.2.0-1772167481346:2544

Nginx adds a trailing slash and downgrades HTTPS to HTTP. HSTS catches it and switches back to HTTPS, but the URL is now /extensions.js/ instead of /extensions.js → server returns HTML instead of JS → CSP blocks it → OnlyOffice fails to load.

@nebulon said in Czech Translation for Cloudron Now 100% Complete :

This is great! We will ship the next Cloudron version then with Czech (internally 9.1 is released for new installs already, so will be added to the next patch release then)

That’s great news, thank you!

@james said in Czech Translation for Cloudron Now 100% Complete :

Hello @archos
Thanks for your contribution.
I have added you to the translator group.

I probably don’t deserve that — my colleague did most of the translation work — but thank you very