Cloudron 9.0 (beta) bug reports
-
I upgraded to 9.0.7 yesterday and everything seems to be working fine, but I woke up this morning to find the following notification:
"Domain yourdomain.tld is not configured properly
General error: defaultProxyStatus must be a boolean"
@hakunamatata thanks, this is fixed in https://git.cloudron.io/platform/box/-/commit/d894de0784ffcb147226c38967311360293e704a .
You can temporarily ignore the notification but if it bothers you:
- Domains -> Edit that Cloudflare domain.
- Change the provider to something else. Then, change it back to Cloudflare. You have to re-enter the API key. Then, Save.
-
Hey,
I'm worried that some API calls I made in the past are no longer working with V9, and that's both with my instance and with Cloudron demo instance.
I'm trying to simply use the API Token and get system disk usage via the route documented in the API.
e.g with the demo instance of cloudron and a token:$ curl -H 'Content-Type: application/json' -H 'Authorization: Bearer <REDACTED>' https://my.demo.cloudron.io/api/v1/system/info { "info": { "sysVendor": "FUJITSU", "productName": "CELSIUS-FTS", "uptimeSecs": 410396, "rebootRequired": false, "activationTime": "2025-01-02T18:04:55.000Z" } } $ curl -H 'Content-Type: application/json' -H 'Authorization: Bearer <REDACTED>' https://my.demo.cloudron.io/api/v1/system/disk_usage { "status": "Not Found", "message": "No such route" }Did some routes change compared to the API Docs?
https://docs.cloudron.io/api.html#tag/System/operation/getDiskUsageThanks!
@SansGuidon yeah, some routes have changed to adapt to the UI. We haven't updated the API and docs with Cloudron 9 API and screenshots yet (sorry, release and everything all going on in parallel) !
Currently, it's roughly this:
/api/v1/system/block_devices- this lists block devices . currently, this does not return used space. this was an oversight, i have added this now./api/v1/system/filesystems- this gives filesystems and size/used information . probably, what you want?/api/v1/system/filesystem_usage?filesystem=/dev/sda1- this does a further "du" on one of the filesystems listed in the above call. Since this takes some time, the output is an event stream. You have to pass-H 'Accept: text/event-stream'.
-
Sorry if this was mentioned already, but it was possible before on 8.x to search by app name in the list of running apps, but this appears to no longer be the case now as of 9.0.7. Is this intentional? Before, I could search for "WordPress" for example and all the apps would filter to the WordPress installs.
@d19dotca said in Cloudron 9.0 (beta) bug reports:
Before, I could search for "WordPress" for example and all the apps would filter to the WordPress installs.
Fixed in https://git.cloudron.io/platform/box/-/commit/a8513cc0fa8e8014da6d8aaa7a963c0ae168b4e5
-
It looks like the multipart upload settings for S3-compatible storage aren’t working as expected.
Last night, I enabled a backup of around 150 GB of data in TGZ format. In the configuration, I set the part size to 256 MB.
This morning, when checking the logs, I found that the upload had stopped at 100 GB because the 10,000-part limit was reached. Based on simple math, that would only make sense if each part were 10 MB — which is Cloudron’s default minimum part size.I double-checked the settings and confirmed that my 256 MB value had been saved correctly. Then I set it to the maximum (1 GB), restarted the server, and manually triggered another backup. Watching the logs again, I noticed the same behavior — a new part was created every 10 MB and uploaded to S3.
Has anyone else run into this issue?
2025-11-09T07:23:19.605Z box:taskworker Starting task 2146. Logs are at /home/yellowtent/platformdata/logs/tasks/2146.log 2025-11-09T07:23:19.624Z box:taskworker Running task of type backup 2025-11-09T07:23:19.644Z box:tasks updating task 2146 with: {"percent":5.761904761904762,"message":"Backing up ***.***.ru (1/18). Waiting for lock"} 2025-11-09T07:23:19.656Z box:locks write: current locks: {"full_backup_task_10b1282f-f0e2-400d-a074-b183f08c16f5":null,"app_backup_07fd2189-9378-4a35-b18d-5cef77461fb1":"2146"} 2025-11-09T07:23:19.656Z box:locks acquire: app_backup_07fd2189-9378-4a35-b18d-5cef77461fb1 2025-11-09T07:23:19.657Z box:tasks updating task 2146 with: {"percent":5.761904761904762,"message":"Snapshotting app ***.***.ru"} 2025-11-09T07:23:19.660Z box:services backupAddons 2025-11-09T07:23:19.660Z box:services backupAddons: backing up ["localstorage","postgresql","sendmail","oidc","redis"] 2025-11-09T07:23:19.661Z box:services Backing up postgresql 2025-11-09T07:23:19.878Z box:services pipeRequestToFile: connected with status code 200 2025-11-09T07:23:23.447Z box:services Backing up redis 2025-11-09T07:23:23.514Z box:services pipeRequestToFile: connected with status code 200 2025-11-09T07:23:23.528Z box:backuptask snapshotApp: ***.***.ru took 3.871 seconds 2025-11-09T07:23:23.564Z box:tasks updating task 2146 with: {"percent":5.761904761904762,"message":"Uploading app snapshot ***.***.ru"} 2025-11-09T07:23:23.564Z box:backuptask runBackupUpload: adjusting heap size to 3840M 2025-11-09T07:23:23.565Z box:shell backuptask: /usr/bin/sudo --non-interactive -E --close-from=4 /home/yellowtent/box/src/scripts/backupupload.js snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc 10b1282f-f0e2-400d-a074-b183f08c16f5 {"localRoot":"/home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1","layout":[{"localDir":"/mnt/md0/IApps/photos","remoteDir":"data"}]} 2025-11-09T07:23:24.304Z box:backupupload Backing up {"localRoot":"/home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1","layout":[{"localDir":"/mnt/md0/IApps/photos","remoteDir":"data"}]} to snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc 2025-11-09T07:23:24.306Z box:backuptask upload: path snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc site 10b1282f-f0e2-400d-a074-b183f08c16f5 dataLayout {"localRoot":"/home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1","layout":[{"localDir":"/mnt/md0/IApps/photos","remoteDir":"data"}]} 2025-11-09T07:23:24.524Z box:backuptask checkPreconditions: mount point status is {"state":"active"} 2025-11-09T07:23:24.524Z box:backuptask checkPreconditions: getting disk usage of /home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1 2025-11-09T07:23:24.524Z box:shell backuptask: du --dereference-args --summarize --block-size=1 --exclude=*.lock --exclude=dovecot.list.index.log.* /home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1 2025-11-09T07:23:24.531Z box:backuptask checkPreconditions: getting disk usage of /mnt/md0/IApps/photos 2025-11-09T07:23:24.531Z box:shell backuptask: du --dereference-args --summarize --block-size=1 --exclude=*.lock --exclude=dovecot.list.index.log.* /mnt/md0/IApps/photos 2025-11-09T07:23:29.436Z box:backuptask checkPreconditions: total required=125109989376 available=Infinity 2025-11-09T07:23:29.448Z box:backupformat/tgz upload: uploading to site 10b1282f-f0e2-400d-a074-b183f08c16f5 path snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc (encrypted: true) dataLayout {"localRoot":"/home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1","layout":[{"localDir":"/mnt/md0/IApps/photos","remoteDir":"data"}]} 2025-11-09T07:23:29.450Z box:tasks updating task 2146 with: {"percent":5.761904761904762,"message":"Uploading backup snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc (***.***.ru)"} 2025-11-09T07:23:29.457Z box:backupformat/tgz tarPack: processing /home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1 2025-11-09T07:23:29.471Z box:backupformat/tgz addToPack: added ./config.json file 2025-11-09T07:23:29.528Z box:backupformat/tgz addToPack: added ./dump.rdb file 2025-11-09T07:23:29.540Z box:backupformat/tgz addToPack: added ./fsmetadata.json file 2025-11-09T07:23:32.318Z box:storage/s3 Upload progress: {"loaded":10485760,"part":1,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc","Bucket":"25fc748e-lvcl-backup"} 2025-11-09T07:23:34.405Z box:storage/s3 Upload progress: {"loaded":20971520,"part":2,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc","Bucket":"25fc748e-lvcl-backup"} 2025-11-09T07:23:37.143Z box:storage/s3 Upload progress: {"loaded":31457280,"part":3,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc","Bucket":"25fc748e-lvcl-backup"} 2025-11-09T07:23:39.234Z box:storage/s3 Upload progress: {"loaded":41943040,"part":4,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc","Bucket":"25fc748e-lvcl-backup"} 2025-11-09T07:23:39.425Z box:storage/s3 Upload progress: {"loaded":52428800,"part":5,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc","Bucket":"25fc748e-lvcl-backup"}@WiseMetalhead said in Cloudron 9.0 (beta) bug reports:
It looks like the multipart upload settings for S3-compatible storage aren’t working as expected.
This works for me on DO Spaces and AWS S3. Which storage provider are you using? I can test with that. Amazon created a new module for S3 uploads and we had to switch over the node module, maybe there is some incompatibility.
-
Thanks @girish, this will work
-
@WiseMetalhead said in Cloudron 9.0 (beta) bug reports:
It looks like the multipart upload settings for S3-compatible storage aren’t working as expected.
This works for me on DO Spaces and AWS S3. Which storage provider are you using? I can test with that. Amazon created a new module for S3 uploads and we had to switch over the node module, maybe there is some incompatibility.
@girish said in Cloudron 9.0 (beta) bug reports:
Which storage provider are you using?
I’m trying to use an
S3 API Compatible (v4)provider. -
@girish said in Cloudron 9.0 (beta) bug reports:
Which storage provider are you using?
I’m trying to use an
S3 API Compatible (v4)provider. -
@WiseMetalhead yes, but which service or set up specifically? (or is this confidential?). How can we reproduce this?
@girish said in Cloudron 9.0 (beta) bug reports:
which service or set up specifically
It’s a local provider for me, and there’s no specific configuration for it in Cloudron.
For convenience, I can create a bucket and send you the access details by email so that you can try to reproduce the issue.
However, if the problem lies in how this provider implements S3 compatibility, I don’t think it’s worth spending too much time on it.
Initially, I thought the issue was related to the generic S3 configuration itself. -
@girish said in Cloudron 9.0 (beta) bug reports:
which service or set up specifically
It’s a local provider for me, and there’s no specific configuration for it in Cloudron.
For convenience, I can create a bucket and send you the access details by email so that you can try to reproduce the issue.
However, if the problem lies in how this provider implements S3 compatibility, I don’t think it’s worth spending too much time on it.
Initially, I thought the issue was related to the generic S3 configuration itself.@WiseMetalhead yeah, our CI tests object storages of DO, AWS, Vultr, Hetzner, minio .
For convenience, I can create a bucket and send you the access details by email so that you can try to reproduce the issue.
Yes please, if that's possible, would be great to understand where the problem is. I suspect this issue will get eventually hit by someone.
-
@WiseMetalhead yeah, our CI tests object storages of DO, AWS, Vultr, Hetzner, minio .
For convenience, I can create a bucket and send you the access details by email so that you can try to reproduce the issue.
Yes please, if that's possible, would be great to understand where the problem is. I suspect this issue will get eventually hit by someone.
@girish said in Cloudron 9.0 (beta) bug reports:
Yes please, if that's possible
I’ve sent the details from my email address vlishchenko****@gmail.com
-
Have these setting be separated out in Cloudron 9?
I wanted to turn of Automatic Platform updates, but leave App updates on:
@jdaviescoates said in Cloudron 9.0 (beta) bug reports:
I wanted to turn of Automatic Platform updates, but leave App updates on:
Not yet, have to look into this in coming releases.
-
I have noticed this on my home server (which does not have a great CPU). The newer backup system adds integrity checks and depending on the CPU power and amount of data this will take more time. Can you tell us CPU info and the how much data you are backing up? If you can tell me how to get an equivalent server (i.e which exact model on netcup), I can test it out directly on that server type.
-
After upgrading to Cloudron 9 I cannot send e-mails with Masquerading-Feature. It got disabled for all Domains, but even after enabling it again, my e-mail client (Apple Mail) still fails to send with another e-mailaddress.
Logfile of email service:
Nov 08 20:45:33 [NOTICE] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D] [core] connect ip=****** port=51653 local_ip=***** local_port=2587 Nov 08 20:45:34 [INFO] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D] [dns-list] pass:******.combined.mail.abusix.zone Nov 08 20:45:34 [INFO] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D] [helo.checks] helo_host: smtpclient.apple, pass:bare_ip, dynamic, valid_hostname, host_mismatch, literal_mismatch, fail:rdns_match Nov 08 20:45:34 [INFO] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D] [spf] identity=helo ip=***** domain="smtpclient.apple" mfrom=<postmaster@smtpclient.apple> result=None Nov 08 20:45:34 [INFO] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D] [spf] scope: helo, result: None, domain: smtpclient.apple Nov 08 20:45:34 [INFO] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D] [tls] secured: cipher=ECDHE-ECDSA-AES128-GCM-SHA256 version=TLSv1.2 verified=false Nov 08 20:45:34 [INFO] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D] [core] hook=unrecognized_command plugin=tls function=upgrade_connection params=STARTTLS retval=OK msg="" Nov 08 20:45:34 [INFO] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D] [helo.checks] helo_host: smtpclient.apple, pass:bare_ip, dynamic, valid_hostname, host_mismatch, literal_mismatch, fail:rdns_match Nov 08 20:45:34 [INFO] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D] [cloudron] Authenticated as MYUSER@SOMEDOMAIN.COM Nov 08 20:45:34 [INFO] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D] [core] hook=unrecognized_command plugin=cloudron function=hook_unrecognized_command params=AUTH retval=OK msg="" Nov 08 20:45:34 [INFO] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D.1] [core] hook=mail plugin=cloudron function=authorize_mail_from params=<MASKED@SOMEDOMAIN.COM> retval=DENY msg="Authenticated user MYUSER@SOMEDOMAIN.COM cannot send mail as MASKED@SOMEDOMAIN.COM" Nov 08 20:45:34 [NOTICE] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D.1] [core] sender <MASKED@SOMEDOMAIN.COM> code=DENY msg="Authenticated user MYUSER@SOMEDOMAIN.COM cannot send mail as MASKED@SOMEDOMAIN.COM" Nov 08 20:45:34 [NOTICE] [1BC2F871-D6E6-46D3-888B-3E7A2D3C716D.1] [core] disconnect ip=***** rdns=****.t-ipconnect.de helo=smtpclient.apple relay=Y early=N esmtp=Y tls=Y pipe=N errors=0 txns=1 rcpts=0/0/0 msgs=0/0/0 bytes=0 lr="550 Authenticated user MYUSER@SOMEDOMAIN.COM cannot send mail as MASKED@SOMEDOMAIN.COM" time=1.764@Kubernetes said in Cloudron 9.0 (beta) bug reports:
After upgrading to Cloudron 9 I cannot send e-mails with Masquerading-Feature
Thanks for reporting! Indeed that flag is inverted! I have fixed the UI text.
Workaround: If you disable it there, I think you will see that masquerading works.
-
@robi this info is there in Backup -> Info dialog (in the global backups). But just noticed it's missing in the App -> Backup -> Info dialog. Will add it there as well.
-
@robi this info is there in Backup -> Info dialog (in the global backups). But just noticed it's missing in the App -> Backup -> Info dialog. Will add it there as well.
