@luckow said in Kuma Uptime - ERROR: Database migration failed:
You can try this: https://github.com/louislam/uptime-kuma/issues/5281#issuecomment-2452376039
That didn't work for me.
That didn't work for me either!
Funny thing is, since the monitoring data is not important, I took a backup of all my hosts, uninstalled the app, when I want to import it, the backup/restore function is completely removed from Kuma in the new version 
/settings/backup does not exit in new update
I am sort of stuck here.
I gave it 16 GB of RAM and still at some point same scenario happened.
My monitor history is too large, so what I tried was to purge all data so it will be light weight for the upgrade. The history data is not important, I used the tool under setting> Monitor history> Clear Statistics
However I get this error:
I dont have any other older working backups.
I gave it 8GB of RAM and then updated it. At some point it forwarded the domain domain to /migrate-status and then in the log I am getting this:
Oct 28 17:53:59 2025-10-28T14:23:59Z [SERVER] ERROR: Failed to prepare your database: Aggregate table migration is already in progress
Oct 28 17:53:59 2025-10-28T14:23:59Z [SERVER] INFO: Connected to the database
Oct 28 17:53:59 2025-10-28T14:23:59Z [SERVER] INFO: Creating express and socket.io instance
Oct 28 17:53:59 2025-10-28T14:23:59Z [SERVER] INFO: Data Dir: ./data/
Oct 28 17:53:59 2025-10-28T14:23:59Z [SERVER] INFO: Server Type: HTTP
Oct 28 17:53:59 2025-10-28T14:23:59Z [DB] ERROR: Database migration failed
Oct 28 17:53:59 2025-10-28T14:23:59Z [DB] WARN: Aggregate table migration is already in progress, or it was interrupted
Oct 28 17:53:59 2025-10-28T14:23:59Z [DB] INFO: Database Type: sqlite
Oct 28 17:54:03 => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.87:3001
Oct 28 17:54:13 => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.87:3001
Oct 28 17:54:23 => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.87:3001
Oct 28 17:54:33 => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.87:3001
Oct 28 17:54:43 => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.87:3001
Oct 28 17:54:53 => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.87:3001
Oct 28 17:54:59 2025-10-28T14:24:59Z
Oct 28 17:54:59 2025-10-28T14:24:59Z
Oct 28 17:54:59 ==> Overriding settings
Oct 28 17:54:59 ==> Removing sqlite backup files
Oct 28 17:54:59 ==> Starting Uptime Kuma
Oct 28 17:54:59 > node server/server.js
Oct 28 17:54:59 > uptime-kuma@2.0.1 start-server
Oct 28 17:55:00 => Healtheck error: Error: connect ECONNREFUSED 172.18.16.87:3001
Oct 28 17:55:00 Welcome to Uptime Kuma
Oct 28 17:55:00 2025-10-28T14:25:00Z [SERVER] INFO: Env: production
Oct 28 17:55:00 2025-10-28T14:25:00Z [SERVER] INFO: Loading modules
Oct 28 17:55:00 2025-10-28T14:25:00Z [SERVER] INFO: Uptime Kuma Version: 2.0.1
Oct 28 17:55:00 Your Node.js version: 18.20.8
and its getting repeated. Does it mean its migrating?
Whatever this is, it happened after the recent update. When I restore to a working backup before the update, the app comes back online but my entries dont work.
Hi guys
Kuma has update automatically and its not working anymore. The apps states its not responding. Terminal is also not connecting for this particular app. It keeps saying reconnecting.
In the logs we have this error:
Oct 27 17:24:23 => Healtheck error: Error: connect EHOSTUNREACH 172.18.20.21:3001
Oct 27 17:24:33 => Healtheck error: Error: connect EHOSTUNREACH 172.18.20.21:3001
Oct 27 17:24:43 => Healtheck error: Error: connect EHOSTUNREACH 172.18.20.21:3001
Oct 27 17:24:53 => Healtheck error: Error: connect EHOSTUNREACH 172.18.20.21:3001
Oct 27 17:25:03 => Healtheck error: Error: connect EHOSTUNREACH 172.18.20.21:3001
Oct 27 17:25:13 => Healtheck error: Error: connect EHOSTUNREACH 172.18.20.21:3001
Oct 27 17:25:15 ==> Removing sqlite backup files
Oct 27 17:25:15 ==> Overriding settings
Oct 27 17:25:15 ==> Starting Uptime Kuma
Oct 27 17:25:15 2025-10-27T13:55:15Z
Oct 27 17:25:15 > uptime-kuma@2.0.1 start-server
Oct 27 17:25:15 > node server/server.js
Oct 27 17:25:15 2025-10-27T13:55:15Z
Oct 27 17:25:15 Welcome to Uptime Kuma
Oct 27 17:25:15 Your Node.js version: 18.20.8
Oct 27 17:25:15 2025-10-27T13:55:15Z [SERVER] INFO: Env: production
Oct 27 17:25:16 2025-10-27T13:55:16Z [SERVER] INFO: Uptime Kuma Version: 2.0.1
Oct 27 17:25:16 2025-10-27T13:55:16Z [SERVER] INFO: Loading modules
Oct 27 17:25:17 2025-10-27T13:55:17Z [SERVER] INFO: Creating express and socket.io instance
Oct 27 17:25:17 2025-10-27T13:55:17Z [SERVER] INFO: Server Type: HTTP
Oct 27 17:25:17 2025-10-27T13:55:17Z [SERVER] INFO: Data Dir: ./data/
Oct 27 17:25:17 2025-10-27T13:55:17Z [DB] INFO: Database Type: sqlite
Oct 27 17:25:17 2025-10-27T13:55:17Z [SERVER] INFO: Connected to the database
Oct 27 17:25:17 2025-10-27T13:55:17Z [DB] WARN: Aggregate table migration is already in progress, or it was interrupted
Oct 27 17:25:17 2025-10-27T13:55:17Z [DB] ERROR: Database migration failed
Oct 27 17:25:17 2025-10-27T13:55:17Z [SERVER] ERROR: Failed to prepare your database: Aggregate table migration is already in progress
I also ran: cloudron-support --troubleshoot
and here is the log:
root@Cloudron:~# cloudron-support --troubleshoot
Vendor: Hetzner Product: vServer
Linux: 6.8.0-86-generic
Ubuntu: noble 24.04
Processor: AMD EPYC-Rome Processor
BIOS NotSpecified CPU @ 2.0GHz x 16
RAM: 32089172KB
Disk: /dev/sda1 157G
[OK] node version is correct
[OK] IPv6 is enabled and public IPv6 address is working
[OK] docker is running
[OK] docker version is correct
[OK] MySQL is running
[OK] nginx is running
[OK] dashboard cert is valid
[OK] dashboard is reachable via loopback
[OK] box v8.3.2 is running
[OK] netplan is good
[OK] DNS is resolving via systemd-resolved
[OK] Dashboard is reachable via domain name
[WARN] Domain domain.tld expiry check skipped because whois does not have this information
[OK] unbound is running
Anyone else having this issue?
in health monitor we have this:
example.com (Uptime Kuma) is down
{
"app": {
"id": "c57a1ed7-789c-4378-aa73-d718754fc3eb",
"appStoreId": "louislam.uptimekuma.app",
"installationState": "installed",
"runState": "running",
"health": "healthy",
"containerId": "c9e70ede9775c1ab07a0c96e6b5d1ff6fc2ec7d95b3d2eb61f09272d731b907b",
"memoryLimit": 2147483648,
"cpuQuota": 100,
"label": null,
"notes": null,
"taskId": null,
"sso": false,
"enableBackup": true,
"proxyAuth": false,
"containerIp": "172.18.20.21",
"crontab": null,
"creationTime": "2025-03-18T09:55:42.000Z",
"updateTime": "2025-10-27T10:04:10.000Z",
"enableAutomaticUpdate": true,
"upstreamUri": "",
"enableMailbox": true,
"mailboxDisplayName": "",
"mailboxName": null,
"mailboxDomain": null,
"enableInbox": false,
"inboxName": null,
"inboxDomain": null,
"enableTurn": 1,
"enableRedis": 1,
"storageVolumeId": null,
"storageVolumePrefix": null,
"ts": "2025-10-27T10:04:10.000Z",
"healthTime": "2025-10-27T10:23:30.000Z",
"hasIcon": false,
"hasAppStoreIcon": true,
"manifest": {
"id": "louislam.uptimekuma.app",
"title": "Uptime Kuma",
"author": "Uptime Kuma Team",
"description": "## About\n\nIt is a self-hosted monitoring tool like \"Uptime Robot\".\n \n## Feature\n\n* Monitoring uptime for HTTP(s) / TCP / Ping.\n* Fancy, Reactive, Fast UI/UX.\n* Notifications via Webhook, Telegram, Discord and email (SMTP).\n* 20 seconds interval.\n\n",
"tagline": "Self-hosted monitoring tool like Uptime Robot",
"version": "2.0.0",
"upstreamVersion": "2.0.1",
"healthCheckPath": "/",
"httpPort": 3001,
"addons": {
"localstorage": {
"sqlite": {
"paths": [
"/app/data/data/kuma.db"
]
}
}
},
"multiDomain": true,
"manifestVersion": 2,
"icon": "logo.png",
"tags": [
"uptime",
"ping",
"status",
"pingdom",
"pingdown",
"monitoring"
],
"documentationUrl": "https://docs.cloudron.io/packages/uptime-kuma/",
"changelog": "* Update uptime-kuma to 2.0.1\n* [Full Changelog](https://github.com/louislam/uptime-kuma/releases/tag/2.0.1)\n* This is a major upgrade. See [breaking changes](https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2#breaking-changes)\n* [#6204](https://github.com/louislam/uptime-kuma/issues/6204) Fix: healthcheck could shutdown Uptime Kuma during migration\n* [#6158](https://github.com/louislam/uptime-kuma/issues/6158) feat: Add Nextcloud Talk notification provider (Thanks [@SystemKeeper](https://github.com/SystemKeeper))\n* [#6150](https://github.com/louislam/uptime-kuma/issues/6150) feat: Add Brevo notification provider (Thanks [@smitmartijn](https://github.com/smitmartijn))\n* [#6135](https://github.com/louislam/uptime-kuma/issues/6135) Added Evolution API as notification provider (Thanks [@bode327](https://github.com/bode327))\n* [#6128](https://github.com/louislam/uptime-kuma/issues/6128) feat(login): Autofocus 2FA (Thanks [@cyril59310](https://github.com/cyril59310))\n* [#6111](https://github.com/louislam/uptime-kuma/issues/6111) feat: Added Slovak language to dropdown menu (Thanks [@dodog](https://github.com/dodog))\n* [#6189](https://github.com/louislam/uptime-kuma/issues/6189) Fix: Maintenance: Handle optional startDateTime to prevent errors when null\n* [#6188](https://github.com/louislam/uptime-kuma/issues/6188) Fix: Set default value for `ping` column to 0 in stat tables\n* [#6187](https://github.com/louislam/uptime-kuma/issues/6187) Fix: Change `monitor`.`ip_family` data type from boolean to string\n* [#6156](https://github.com/louislam/uptime-kuma/issues/6156) fix: Replace proxy-agent due to vm2 vulnerability (Thanks [@MatanAmoyal1](https://github.com/MatanAmoyal1))\n",
"postInstallMessage": "On first visit, you will be asked to set up an admin account.\n",
"website": "https://github.com/louislam/uptime-kuma",
"forumUrl": "https://forum.cloudron.io/category/133/uptime-kuma",
"contactEmail": "support@cloudron.io",
"mediaLinks": [
"https://screenshots.cloudron.io/louislam.uptimekuma.app/dashboard.jpg"
],
"configurePath": "/dashboard",
"capabilities": [
"ping"
],
"minBoxVersion": "8.2.0",
"dockerImage": "cloudron/louislam.uptimekuma.app:202510211435340000"
},
"tags": [],
"checklist": {},
"reverseProxyConfig": {},
"portBindings": {},
"accessRestriction": null,
"operators": null,
"debugMode": null,
"servicesConfig": {},
"secondaryDomains": [],
"redirectDomains": [],
"aliasDomains": [],
"subdomain": "",
"domain": "example.com",
"certificate": null,
"env": {},
"mounts": [],
"error": null,
"devices": {},
"iconUrl": "/api/v1/apps/c57a1ed7-789c-4378-aa73-d718754fc3eb/icon",
"fqdn": "example.com"
}
}
Thank you for clarification.
Hi
Yes it’s fixed now
Does this mean after we reach 300 we need to get in touch again?
I still don't see the reasoning behind this limitation while the license agreement clearly states unlimited apps.
I'd appreciate a clarification.
Thank you
Hi, any updates?
Need to reissue the license or some command? I did restart the server and restarted box as well. But still it says the same thing.
Hi,
We are using the UI to create apps. Getting same error as I initially stated. The screenshot.
Hi again,
I checked, its not allowing me to create more apps. I have total of 210 apps.
Its interrupting our workflow. Could you kindly check this from your end?
Thank you
Thank you for the prompt response
Hi
I have pro license and after creating 200 apps now it don’t allow me to create more.
Note that I recently successfully migrated to a new server. Everything is fine and working well but this message shows that I can’t create more apps and it asks me to purchase a subscription despite the fact that I already have an active subscription.
To install more apps, a paid subscription is required.
Then there is a setup subscription button. As if I am on free plan.
Any thought?
Hi,
How can I reset admin password for n8n?
I've installed n8n on cloudron, now I can't remember the password.
Reset password also is not working. Probably the email I wrote upon registration wasn't a valid one to receive emails or SMTP is not working.
Thank you
Link: https://github.com/TelegramMessenger/MTProxy
Please add this widely used tool for telegram users. We are very interested to use this tool within CloudRon. The implementation is pretty simple.
Thank you so much for making everything so easy.