Cloudron Forum

@nebulon No luck, I don't have a reliable answer for you.

Okay, found and fixed.
/etc/netplan/50-cloud-init.yaml was attempting to manage both of my Ethernet ports. One of them is never connected to a network. Once I disabled the second port in YAML and restarted the service, everything worked perfectly.

it's complicated.
After installing a pending update on the fritz.box, the my dashboard is working again. systemd ...network and unbound-resolvconf have failed (again). Mmh.

nothing special (?) in the logs:
Subject: Unit process exited - An ExecStart= process belonging to unit systemd-networkd-wait-online.service has exited.
Subject: Unit failed - The unit systemd-networkd-wait-online.service has entered the 'failed' state with result 'exit-code'.
Subject: A start job for unit systemd-networkd-wait-online.service has failed - A start job for unit systemd-networkd-wait-online.service has finished with a failure.

No more DNS server behind fritz.box.
No configuration around networking.

Q: I did a quick check on other Cloudron instances and recognizd ● unbound-resolvconf.service loaded failed failed Unbound asyncronous resolvconf update helper on every instance. Is this "normal"?

First time in history!

Problem is: there is no way to log in to my dashboard.

On one of my instances with 9.0.5 (Ubuntu 24.04.3 LTS) in my home network behind a fritz.box: systemctl --failed produces a

● systemd-networkd-wait-online.service loaded failed failed Wait for Network to be Configured
● unbound-resolvconf.service loaded failed failed Unbound asyncronous resolvconf update helper

Restarting the services produces a No DNS servers specified, refusing operation. and Timeout occurred while waiting for network connectivity.

DNS resolving works:

host www.cloudron.io 127.0.0.53
Using domain server:
Name: 127.0.0.53
Address: 127.0.0.53#53
Aliases:

www.cloudron.io has address 165.227.67.76
www.cloudron.io has IPv6 address 2604:a880:800:10::b66:f001

DNS entry for my.example.org is active and correct. VPN & ssh into the instance is also working.

Any ideas on how to fix this?

You can try this: https://github.com/louislam/uptime-kuma/issues/5281#issuecomment-2452376039
That didn't work for me.

package documentation goes to https://docs.cloudron.io/apps/ollama/ ->404
correct link is https://docs.cloudron.io/packages/ollama/

That sounds familiar.

https://forum.cloudron.io/topic/14443/uptime-kuma-2.0.0-package/5?_=1761577361678

Solution was:
https://forum.cloudron.io/topic/14444/brief-note-on-backup-and-cloning-versions-prior-to-2.0

If it is the root cause: try cloning from a backup that was created before the 2.x update. This may work for you.

Um. How can I disable registration? The package does not contain an .env file. New registrations can create projects = newsletters.

Secondly: There is text marked in red in the captcha: Please contact the site admin if you see this

Wait a minute. I'm talking to myself and have no idea what to do.

@Lanhild You should really consider switching to https://github.com/zabbix/zabbix
(Number of monitors: 170)

Woohoo. 2.0.1 update worked.
Q: Any plans to switch the app package to MariaDB instead of sqlite?

I created a new backup of a running Uptime Kuma instance three times and attempted to clone it, as this was a “dry run” for version 2.0.

Each clone generated the following message due to a corrupted database Trace: [Error: select * from heartbeat where monitor_id = 75 ORDER BY time DESC limit 1 - SQLITE_CORRUPT: database disk image is malformed].

The following instructions https://github.com/louislam/uptime-kuma/issues/5281#issuecomment -2452376039 created a 0-byte copy of the database, and nothing else from stackoverflow and Co. worked for me.

The only option was to start my running Uptime Kuma in recovery mode and back up this state. Restoring from this backup created a “valid”, undamaged database.

@joseph maybe. But first I have to fix this: Trace: [Error: select * from heartbeat where monitor_id = 75 ORDER BY time DESC limit 1 - SQLITE_CORRUPT: database disk image is malformed] This is a log entry BEFORE the 2.0 update.

My first try was a showstopper:

Oct 22 13:18:11 Your Node.js version: 18.20.8
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] ERROR: Failed to prepare your database: Aggregate table migration is already in progress
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] INFO: Connected to the database
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] INFO: Creating express and socket.io instance
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] INFO: Data Dir: ./data/
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] INFO: Loading modules
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] INFO: Server Type: HTTP
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] INFO: Uptime Kuma Version: 2.0.1
Oct 22 13:18:12 2025-10-22T11:18:12Z [DB] ERROR: Database migration failed
Oct 22 13:18:12 2025-10-22T11:18:12Z [DB] WARN: Aggregate table migration is already in progress, or it was interrupted
Oct 22 13:18:12 2025-10-22T11:18:12Z [DB] INFO: Database Type: sqlite
Oct 22 13:18:13 \
Oct 22 13:18:38 ==> Overriding settings
Oct 22 13:18:38 ==> Removing sqlite backup files
Oct 22 13:18:38 ==> Starting Uptime Kuma
Oct 22 13:18:39 2025-10-22T13:18:39+02:00
Oct 22 13:18:39 2025-10-22T13:18:39+02:00
Oct 22 13:18:39 Welcome to Uptime Kuma

Now in an endless loop. I'll try it on a second clone.

No user feedback if mandatory fields are not filled in (backup-formats & save button)

@philkunz Let's wait and see what the new UI in Cloudron 9 brings. If you still don't like it, why don't you make a wireframe suggestion in a feature request?

@philkunz You need an app backup. But then it's very simple.

@necrevistonnezr oh! a bad beast

@matix131997 It may help with debugging if you specify the context, i.e., which mobile phone and browser are being used. I've learned that the Galaxy Browser on Samsung phones is a beast.

@jdaviescoates
The good old traditional method: https://docs.bunkerweb.io/latest/integrations/#linux
Runs on a CX22 on https://www.hetzner.com/cloud/.

Bunkerweb acts as a reverse proxy for a Cloudron app that is ‘behind it’. Currently, we only use it in front of our own website (mainly because we are still learning, e.g. what happens when we block bots? Oh, there is no longer support for previews in rocket.chat). In my next spare moment, I'll try out what happens when a complete Cloudron instance is behind Bunkerweb. It should work. From what I've heard, this is the case with Cloudflare, and Bunkerweb is similar (only self-hosted)

@chmod777 In my opinion, you should start with InvoiceNinja. A white label licence is available for only $30 per year.
However, there is no "mail to ticket for new requests" option in the customer portal. The good old Cloudron email server is the simplest option for this. Alternatively, you can set up Freescout, a kind of helpdesk. Perhaps there is an n8n integration for Freescout and InvoiceNinja.