Fantastic!
caspear
Posts
-
Old images filling the disk -
Old images filling the diskOh no!
To me this does not immediately feel like a race condition: These images are very reliably retained, and other types of images get cleaned up without any issues. So, why this one?
I am happy to add a cron job that deletes all but the 3-4 most recent ones, just to see if the issue is still recurring.
-
Old images filling the diskgrep -H "uptimekuma.app:202610311425350000" /home/yellowtent/platformdata/logs/tasks/.log /home/yellowtent/platformdata/logs/95a0b41d-0525-4b60-b62e-3bb8b11edaf2/apptask.log | cut -c1-300
# docker image inspect --format '{{index .RepoTags 0}} {{.Metadata.LastTagTime}}' cloudron/louislam.uptimekuma.app:202610311425350000 cloudron/louislam.uptimekuma.app:202611011424070000 cloudron/louislam.uptimekuma.app:202610311425350000 0001-01-01 00:00:00 +0000 UTC cloudron/louislam.uptimekuma.app:202611011424070000 2026-11-01 23:00:41.030181353 +0000 UTC# grep -H "uptimekuma.app:202610311425350000" /home/yellowtent/platformdata/logs/tasks/*.log /home/yellowtent/platformdata/logs/95a0b41d-0525-4b60-b62e-3bb8b11edaf2/apptask.log* | cut -c1-300 /home/yellowtent/platformdata/logs/tasks/12500.log:2026-11-01T23:32:35.295Z shell: services: /bin/bash -c docker run --rm --name=sqlite-95a0b41d-0525-4b60-b62e-3bb8b11edaf2 --net cloudron --log-driver=none -v /home/yellowtent/appsdata/95a0b41d-0525-4b60-b62e-3bb8b /home/yellowtent/platformdata/logs/tasks/12500.log:2026-11-01T23:33:02.040Z shell: services: /bin/bash -c docker run --rm --name=sqlite-95a0b41d-0525-4b60-b62e-3bb8b11edaf2 --net cloudron --log-driver=none -v /home/yellowtent/appsdata/95a0b41d-0525-4b60-b62e-3bb8b /home/yellowtent/platformdata/logs/95a0b41d-0525-4b60-b62e-3bb8b11edaf2/apptask.log:2026-11-01T01:00:12.842Z docker: downloadImage: cloudron/louislam.uptimekuma.app:202610311425350000 /home/yellowtent/platformdata/logs/95a0b41d-0525-4b60-b62e-3bb8b11edaf2/apptask.log:2026-11-01T01:00:12.847Z docker: pullImage: will pull registry.docker.com/cloudron/louislam.uptimekuma.app:202610311425350000. auth: no /home/yellowtent/platformdata/logs/95a0b41d-0525-4b60-b62e-3bb8b11edaf2/apptask.log:2026-11-01T01:00:36.738Z docker: pullImage: {"status":"Status: Downloaded newer image for registry.docker.com/cloudron/louislam.uptimekuma.app:202610311425350000"} /home/yellowtent/platformdata/logs/95a0b41d-0525-4b60-b62e-3bb8b11edaf2/apptask.log:2026-11-01T01:00:36.741Z docker: downloaded image registry.docker.com/cloudron/louislam.uptimekuma.app:202610311425350000 . error: false /home/yellowtent/platformdata/logs/95a0b41d-0525-4b60-b62e-3bb8b11edaf2/apptask.log:2026-11-01T01:00:36.741Z docker: downloadImage: tagging registry.docker.com/cloudron/louislam.uptimekuma.app:202610311425350000 as cloudron/louislam.uptimekuma.app:202610311425350000 /home/yellowtent/platformdata/logs/95a0b41d-0525-4b60-b62e-3bb8b11edaf2/apptask.log:2026-11-01T01:00:36.748Z docker: downloadImage: untagging registry.docker.com/cloudron/louislam.uptimekuma.app:202610311425350000 /home/yellowtent/platformdata/logs/95a0b41d-0525-4b60-b62e-3bb8b11edaf2/apptask.log:2026-11-01T01:00:36.748Z docker: deleteImage: removing registry.docker.com/cloudron/louislam.uptimekuma.app:202610311425350000 /home/yellowtent/platformdata/logs/95a0b41d-0525-4b60-b62e-3bb8b11edaf2/apptask.log:2026-11-01T23:00:02.520Z shell: services: /bin/bash -c docker run --rm --name=sqlite-95a0b41d-0525-4b60-b62e-3bb8b11edaf2 --net cloudron --log-driver=none -v /home/yellowtent/appsd /home/yellowtent/platformdata/logs/95a0b41d-0525-4b60-b62e-3bb8b11edaf2/apptask.log:2026-11-01T23:00:06.820Z shell: services: /bin/bash -c docker run --rm --name=sqlite-95a0b41d-0525-4b60-b62e-3bb8b11edaf2 --net cloudron --log-driver=none -v /home/yellowtent/appsd /home/yellowtent/platformdata/logs/95a0b41d-0525-4b60-b62e-3bb8b11edaf2/apptask.log:2026-11-01T23:00:42.444Z docker: deleteImage: removing cloudron/louislam.uptimekuma.app:202610311425350000 -
Old images filling the diskI pasted them together and so they executed sequentially. The # at the beginning is the root prompt.

I will execute them again one at a time so that it is more clear.
# docker ps -a --format '{{.ID}} {{.Image}} {{.Names}} {{.Status}} {{.Label "appId"}} {{.Label "isCloudronManaged"}}' | grep -i uptimekuma 167109c4b757 cloudron/louislam.uptimekuma.app:202611011424070000 95a0b41d-0525-4b60-b62e-3bb8b11edaf2 Up 2 days 95a0b41d-0525-4b60-b62e-3bb8b11edaf2 true# docker images --digests | grep -i uptimekuma | head cloudron/louislam.uptimekuma.app 202611011424070000 <none> 81ce16f02a7e 5 days ago 2.49GB cloudron/louislam.uptimekuma.app 202610311425350000 sha256:585554c282e88cfa79efd6f6ef0e651700f394de3d2e5f7ae8f48bb612b160d8 555d251b4542 5 days ago 2.49GB cloudron/louislam.uptimekuma.app 202610281425490000 sha256:15ade59f35a8aa256706bb8c7930b9a6a56270c2d2b3bb6b39d472c0100ac464 a8fee11920ee 8 days ago 2.49GB cloudron/louislam.uptimekuma.app 202610231334320000 sha256:0c00116c5fb25f8c58ebd40505b849c26d0252220883403586d3ec64cc1ccdf7 5db34eb4f263 2 weeks ago 2.49GB cloudron/louislam.uptimekuma.app 202610221334590000 sha256:7da13fbe7c4a0e14f0de5f000ffc773b68a573de349c5fd318deba7a79098c06 a8885b2c1967 2 weeks ago 2.49GB cloudron/louislam.uptimekuma.app 202610201324590000 sha256:1f02d509787ccea7f2e016dc75ae5a32d36a2c0d8a394ad21d3b1fed943e0861 1fc29da1e576 2 weeks ago 2.49GB cloudron/louislam.uptimekuma.app 202610101326010000 sha256:4b3938f95fa9b0dd525feacae43b8f9c2471e855177e0bcc8aebf41acf8be1c2 0ed29fbb1a3e 3 weeks ago 2.48GB cloudron/louislam.uptimekuma.app 202610061328140000 sha256:47bdd8aa81cd64880741735676c6abac34835c142f96c0182c86fdb4895646a4 41ee44f20c5b 4 weeks ago 2.48GB cloudron/louislam.uptimekuma.app 202609251853530000 sha256:d00039a73a9b8e6e88c1ad9040ba99a4f5f8998970538c0813c35171596b9f81 b784b501be0e 5 weeks ago 2.48GB cloudron/louislam.uptimekuma.app 202609230702240000 sha256:91938385453ce51292f868822ccda85d4d562429a9da7b8099b1de31e8681d27 9c9a62d0439a 6 weeks ago 2.48GB# grep -h "deleteImage: removing cloudron/louislam" /home/yellowtent/platformdata/logs/tasks/*.log | tailLast command returns nothing - uptime kuma images never get deleted, that is indeed my bug report!

-
Old images filling the disk# docker ps -a --format '{{.ID}} {{.Image}} {{.Names}} {{.Status}} {{.Label "appId"}} {{.Label "isCloudronManaged"}}' | grep -i uptimekuma docker images --digests | grep -i uptimekuma | head grep -h "deleteImage: removing cloudron/louislam" /home/yellowtent/platformdata/logs/tasks/*.log | tail 167109c4b757 cloudron/louislam.uptimekuma.app:202611011424070000 95a0b41d-0525-4b60-b62e-3bb8b11edaf2 Up 2 days 95a0b41d-0525-4b60-b62e-3bb8b11edaf2 true cloudron/louislam.uptimekuma.app 202611011424070000 <none> 81ce16f02a7e 4 days ago 2.49GB cloudron/louislam.uptimekuma.app 202610311425350000 sha256:585554c282e88cfa79efd6f6ef0e651700f394de3d2e5f7ae8f48bb612b160d8 555d251b4542 5 days ago 2.49GB cloudron/louislam.uptimekuma.app 202610281425490000 sha256:15ade59f35a8aa256706bb8c7930b9a6a56270c2d2b3bb6b39d472c0100ac464 a8fee11920ee 8 days ago 2.49GB cloudron/louislam.uptimekuma.app 202610231334320000 sha256:0c00116c5fb25f8c58ebd40505b849c26d0252220883403586d3ec64cc1ccdf7 5db34eb4f263 13 days ago 2.49GB cloudron/louislam.uptimekuma.app 202610221334590000 sha256:7da13fbe7c4a0e14f0de5f000ffc773b68a573de349c5fd318deba7a79098c06 a8885b2c1967 2 weeks ago 2.49GB cloudron/louislam.uptimekuma.app 202610201324590000 sha256:1f02d509787ccea7f2e016dc75ae5a32d36a2c0d8a394ad21d3b1fed943e0861 1fc29da1e576 2 weeks ago 2.49GB cloudron/louislam.uptimekuma.app 202610101326010000 sha256:4b3938f95fa9b0dd525feacae43b8f9c2471e855177e0bcc8aebf41acf8be1c2 0ed29fbb1a3e 3 weeks ago 2.48GB cloudron/louislam.uptimekuma.app 202610061328140000 sha256:47bdd8aa81cd64880741735676c6abac34835c142f96c0182c86fdb4895646a4 41ee44f20c5b 4 weeks ago 2.48GB cloudron/louislam.uptimekuma.app 202609251853530000 sha256:d00039a73a9b8e6e88c1ad9040ba99a4f5f8998970538c0813c35171596b9f81 b784b501be0e 5 weeks ago 2.48GB cloudron/louislam.uptimekuma.app 202609230702240000 sha256:91938385453ce51292f868822ccda85d4d562429a9da7b8099b1de31e8681d27 9c9a62d0439a 6 weeks ago 2.48GB -
Old images filling the disk# echo "Cloudron $(cat /home/yellowtent/box/VERSION)" Cloudron 10.1.6 -
Old images filling the diskUptime Kuma does not seem to be cleaning up old docker images, which is slowly but surely filling the disk.
# docker images -q cloudron/louislam.uptimekuma.app | wc -l 56# docker images cloudron/louislam.uptimekuma.app --format 'table {{.Tag}}\t{{.CreatedSince}}\t{{.Size}}' TAG CREATED SIZE 202611011424070000 4 days ago 2.49GB 202610311425350000 5 days ago 2.49GB 202610281425490000 8 days ago 2.49GB 202610231334320000 13 days ago 2.49GB 202610221334590000 2 weeks ago 2.49GB 202610201324590000 2 weeks ago 2.49GB 202610101326010000 3 weeks ago 2.48GB 202610061328140000 4 weeks ago 2.48GB 202609251853530000 5 weeks ago 2.48GB 202609230702240000 6 weeks ago 2.48GB 202609221324260000 6 weeks ago 2.58GB 202609121323500000 7 weeks ago 3.64GB 202609101324360000 8 weeks ago 3.64GB 202608311323360000 2 months ago 3.64GB 202608221323290000 2 months ago 3.64GB 202608151323590000 2 months ago 3.64GB 202608031037220000 3 months ago 3.65GB 202607231323390000 3 months ago 3.64GB 202607161323260000 3 months ago 3.63GB 202607101323560000 3 months ago 3.63GB 202606191323050000 4 months ago 3.63GB 202606091323070000 4 months ago 3.64GB 202605311323040000 5 months ago 3.64GB 202605251323070000 5 months ago 3.64GB 202605131324090000 5 months ago 3.64GB 202605040734180000 6 months ago 3.64GB 202605011457400000 6 months ago 3.64GB 202603100309490000 8 months ago 3.62GB 202603050653400000 8 months ago 3.58GB 202602191408550000 8 months ago 3.61GB 202602131712530000 8 months ago 3.6GB 202602090716130000 9 months ago 3.64GB 202602071425440000 9 months ago 3.75GB 202601271425310000 9 months ago 3.75GB 202601201425020000 9 months ago 3.74GB 202511081423470000 12 months ago 3.74GB 202511071426450000 12 months ago 3.74GB 202510311426170000 12 months ago 3.74GB 202510211435340000 12 months ago 3.74GB 202509231325220000 13 months ago 4.32GB 202509181325050000 13 months ago 4.32GB 202508221422060000 14 months ago 4.32GB 202508091326260000 15 months ago 4.33GB 202507041324150000 16 months ago 4.33GB 202506171327000000 16 months ago 4.33GB 202506111326470000 17 months ago 4.32GB 202505161324190000 17 months ago 4.32GB 202505011323380000 18 months ago 4.31GB 202504071849220000 19 months ago 4.31GB 202504031324250000 19 months ago 3.69GB 202503271803390000 19 months ago 3.69GB 202502271429150000 20 months ago 3.36GB 202502051425410000 21 months ago 3.36GB 202501311424270000 21 months ago 3.36GB 202501071425390000 22 months ago 3.36GB 202412200803170000 22 months ago 3.34GB# docker system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 90 30 120.2GB 75.35GB (62%) Containers 98 64 0B 0B Local Volumes 173 173 12.55GB 0B (0%) Build Cache 0 0 0B 0B -
DKIM when external relay is configuredWithout the DNS entry mail from cloudron ends up with
ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@smtpcorp.com header.s=a1-4 header.b=38VpoA5C; dkim=pass header.i=@permamed.org header.s=s1004192 header.b=IvzZvAEF; dkim=permerror (no key for signature) header.i=@permamed.org header.s=cloudron-0d9262 header.b=cSc2yqyX; spf=pass (google.com: domain of bounce.3wqhqixyft3pua6=46muc2596w7f=34l98tc3oj4uzw@em1004192.permamed.org designates 158.120.86.203 as permitted sender)Once I add the entry I get
ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@smtpcorp.com header.s=a1-4 header.b=hge5ICDL; dkim=pass header.i=@permamed.org header.s=s1004192 header.b=HnqT1ibh; dkim=pass header.i=@permamed.org header.s=cloudron-0d9262 header.b="bpPl/+t5"; spf=pass (google.com: domain of bounce.w5qkkdyfnaxsxb7=ojoiat7bxbcy=pc4cfvy7huru7n@em1004192.permamed.org designates 158.120.86.203 as permitted sender) -
DKIM when external relay is configuredSend an email through the Cloudron and look at the mail headers in the mail you end up with.
It will include DKIM signature from Cloudron, which fails to validate if the DNS entry is missing.
DMARC reports will also list it as an issue, if you have that configured.
-
DKIM when external relay is configuredWhen external SMTP relay is configured Cloudron still signs all outgoing mail with DKIM, but the UI hides the DNS entry it wants.
Without the matching entry some mail servers then reject the mail because of the DKIM failure.
Please either:
- Do not sign the mail when using external relay to send mail
- Expose the expected DKIM DNS entry to the end user so that they can configure it
The half-way house does not work.
As a workaround I disabled external relay to reveal the DNS entry, created the DNS entry, and then added the SMTP relay back again.
-
Attempting to download any backups causes a cloudron crashI changed nothing, but it is working today.
I imagine what is happening is that the upstream storage drops connections occasionally and cloudron simply passes that on to the user instead of having a retry loop in the background.
So, I still believe this functionality would benefit from being more robust, as before it would manage 20-50MB per go before drop, and if the thing was in a retry loop it would be able to get the archive out by just resuming downloads.
I realise it is annoying having to deal with people who insist on unreliable storage... but it is what we have.
-
Attempting to download any backups causes a cloudron crashSometimes it breaks almost instantly, at other times it manages to go for a few seconds and get to 20-30MB before crashing.
-
Attempting to download any backups causes a cloudron crash2026-03-05T16:02:10.196Z box:apphealthmonitor app health: 30 running / 6 stopped / 0 unresponsive 2026-03-05T16:02:39.547Z box:server ========================================== 2026-03-05T16:02:39.549Z box:server Cloudron 9.0.17 2026-03-05T16:02:39.549Z box:server ========================================== 2026-03-05T16:02:39.550Z box:platform initialize: start platform 2026-03-05T16:02:39.551Z box:tasks stopAllTasks: 0 tasks are running. sending abort signal 2026-03-05T16:02:39.551Z box:shell tasks: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/stoptask.sh all 2026-03-05T16:02:39.665Z box:locks releaseAll: all locks released 2026-03-05T16:02:39.671Z box:reverseproxy writeDashboardConfig: writing dashboard config for thedigitalcircle.org 2026-03-05T16:02:39.687Z box:shell reverseproxy: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/restartservice.sh nginx 2026-03-05T16:02:40.402Z box:platform onActivated: starting post activation services 2026-03-05T16:02:40.402Z box:platform startInfra: checking infrastructure 2026-03-05T16:02:40.403Z box:platform startInfra: infra is uptodate at version 49.9.0 2026-03-05T16:02:40.403Z box:platform onInfraReady: platform is ready. infra changed: false 2026-03-05T16:02:40.403Z box:apps schedulePendingTasks: scheduling app tasks 2026-03-05T16:02:40.451Z box:apptaskmanager started 2026-03-05T16:02:40.452Z box:cron startJobs: starting cron jobs with hour 15 and minute 28 2026-03-05T16:02:40.499Z box:cron handleBackupScheduleChanged: schedule 00 00 23 * * * (Europe/London) 2026-03-05T16:02:40.503Z box:cron autoupdatePatternChanged: pattern - 00 00 1,3,5,23 * * * (Europe/London) 2026-03-05T16:02:40.508Z box:cron Dynamic DNS setting changed to false 2026-03-05T16:02:40.510Z box:dockerproxy start: listening on 172.18.0.1:3003 2026-03-05T16:02:43.334Z box:shell system: lsblk --paths --bytes --json --list --fs --output +rota,fsused,fsavail 2026-03-05T16:02:50.227Z box:apphealthmonitor app health: 30 running / 6 stopped / 0 unresponsive -
Attempting to download any backups causes a cloudron crash- On Cloudron admin UI go to My Apps page.
- Press the little cog button in the top right corner of an App.
- Select "Backups" in list of pages that appears.
- In the list of backups that comes up press the thee dots button to the right of the most recent backup.
- Press "Download".
- Observe a download start.
- Observe the download stop.
- Observe a red "Cloudron is offline" bar come up on top of the page.
- Observe Cloudron restart itself.
- Attempt resuming the download.
- Observe Download break.
- Observe Cloudron restart itself
...
Is this sufficient detail or would you like me to include some screenshots?
-
Attempting to download any backups causes a cloudron crashOnly post Cloudron or server issues in this topic. Use the specific app category for app issues.
- Please include a detailed description of the problem. Include screenshots when applicable.
Attempting to download a backup archive of a service ends up with the whole cloudron crashing, the download stopping, and a message in the log to appear that reads:
Cloudron started with version 9.0.17Backups are running without issues and the configured storage is
Storage: scaleway-objectstorage (tgz) at Amsterdam (NL-AMS) / dc1 / backups- Run
cloudron-support --troubleshooton your server and post the output here like this:
root@cloudron-1:~# cloudron-support --troubleshoot Vendor: Hetzner Product: vServer Linux: 5.15.0-157-generic Ubuntu: jammy 22.04 Execution environment: kvm Processor: AMD EPYC-Rome Processor x 16 RAM: 32086348KB Disk: /dev/sda1 187G [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] netplan is good [OK] DNS is resolving via systemd-resolved [OK] unbound is running [OK] nginx is running [OK] dashboard cert is valid [OK] dashboard is reachable via loopback [OK] No pending database migrations [OK] Service 'mysql' is running and healthy [OK] Service 'postgresql' is running and healthy [OK] Service 'mongodb' is running and healthy [OK] Service 'mail' is running and healthy [OK] Service 'graphite' is running and healthy [OK] Service 'sftp' is running and healthy [OK] box v9.0.17 is running [OK] Dashboard is reachable via domain name [OK] Domain thedigitalcircle.org is valid and has not expired- Check for any errors in
/home/yellowtent/platformdata/logs/box.log
Delete everything above before making a new post.
-
/admin attempts to redirect to an internal portConfirmed fixed.
You are wonderful.

-
/admin attempts to redirect to an internal portDescription:
When using the LimeSurvey Cloudron app:Accessing /admin/index.php works correctly.
Accessing /admin alone redirects to http://example.app:8000/admin/ and hangs.
This happens because the LimeSurvey rooturl configuration is not automatically set to the Cloudron public URL. The redirect uses the internal service port instead of the public domain.
Steps to Reproduce:
Install LimeSurvey on Cloudron.
Navigate to https://<your-domain>/admin.
Observe the redirect to internal port :8000 and failure to load.
Navigate to https://<your-domain>/admin/index.php — page loads correctly.
Expected Behavior:
/admin should redirect to the correct public URL and load the admin interface.Additional Notes:
Setting rooturl manually in application/config/config.php fixes the issue, but the config is reset when the service is restarted.
Suggestion: Cloudron should automatically set and persist rooturl based on the app’s public domain.
-
Bump PHP to 8.2We need the functionality quite badly - is there anything that I can do to expedite the bump?
-
Bump PHP to 8.2Please bump PHP to 8.2 to resolve this issue in Leantime:
https://github.com/Leantime/leantime/issues/2970
Thanks!