@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.
@stoccafisso said in Install errors:
Will this work well for later updates of the app?
I am trying to fix this issue without this dirty hands-on fix.
So, if I get this fixed, my quickfix guide is not needed.
Yes, we currently roll out the release slowly by first character of the dashboard domain, however now a-z but a bit random, so it is isn't always the same Cloudrons getting the versions first.
At the moment the release is only available for those but will not auto-update yet.
To update everyone here, this is fixed with https://git.cloudron.io/platform/box/-/commit/21191bdc5075bfd334c11d9ffc321e222fa0b6d4
Turns out the code would cleanup ssh identity files when a temporary mount (for the app import) gets removed, despite that key file still being used in another volume or backup site. Root cause was that the key file name was just the host of the remote, which is not unique. We have made the filenames now unique.
Ok, based on the box.log file I got a LLM/Claude debug session going and it was pretty quick showing me, that there was a docker container (postgres) running that was attached to the Cloudron Network, but not managed by Cloudron. I think that was something I set up super early, before I understood how Cloudron works. Claude helped me dettaching it and now the update went through without issues and everything is running again. Thanks for the hint with the box.log file @joseph !
@nebulon , per request:
https://forum.cloudron.io/topic/14525/improving-user-experience-with-ssh-keys-for-sshfs-and-volume-mounts
Many, many thanks. And, if I find anything useful, I'll update that thread. Or, this one, and cross-link.
Good catch, this is fixed now with https://git.cloudron.io/platform/box/-/commit/c35543af924a5cc8e82eac8c8fc0ef8139503f5a
The quota sorting was also off.
This is the server: RS 4000 G12
I have about 350 GB on the server.
Note that the time increase didn't happen with the upgrade to Cloudron 9, but only to 9.0.6. It was fine with 9.0.5 and before constantly, and backups take much longer each time since the upgrade.
Hello @archos
I've looked into it and the version you have installed org.tt_rss.cloudronapp:3.0.0 was the final update and was a manual update (which you had to confirm manually) with the following release note:
CHANGELOG.md
[3.0.0]
* **IMPORTANT:** This package uses MySQL and upstream TinyTinyRSS has dropped support for MySQL. This is the last release of this package. We have published a new package which uses PostgreSQL. Please switch to the new package using the [migration guide](https://docs.cloudron.io/apps/tinytinyrss/#migrating-from-mysql-to-postgresql) .
Which looked like this:
[image: 1762770654708-3d35eea5-7b0b-4b90-8d19-5b9aae03f814-image-resized.png]
So you must have not noticed this while applying the manual update back then (~28 April 2025)
I will think about how we can make this more noticeable to users in the future.
Hello @dgtlmoon
Maybe I am understanding the scheduling settings wrong.
The full log since installation can be viewed here: https://file.cloudron.dev/api/v1/shares/sid-0387aa81cfe5d4aa1b40368f38b4004bd7242e862414b781d1fbed7d2d7c8601?type=raw
If you'd like to look at the UI yourself the password is dd6de65db716 and the URL https://io.changedetection.cloudronapp.cloudron.dev/
Here is the replicated setting from this post.
[image: 1762333420989-5b995c86-09c3-4d26-9d0d-5eb9c958d48e-io.changedetection.cloudronapp.cloudron.dev_settings-resized.png]
It is the latest version v0.50.39.
From https://changedetection.io/tutorial/checking-web-pages-changes-according-schedule
For example, if you combine a "Time between recheck" of 1 days, and then click the "BUSINESS HOURS" shortcut, it will automatically configure a time schedule that runs from 09:00 for 8 hours (until 17:00h), and since you have "recheck" time set to 1 days, it means it will only check once per day at 09:00.
So I'd expect these setting to have created a check at 04:00 o'clock.
But the last check was a manual one and no sceduled check at 04:00.
[image: 1762333508223-b9b020c1-b111-476e-91fa-5215628ea144-image.png]
But maybe I am just understanding the setting wrong.
Thanks in advance @dgtlmoon
Honestly, I didn't try. I didn't find evidence that this was possible, so I assumed it wasn't.
For my needs, I have found a different solution for this now, but maybe this could be helpful to clarify, if it works, then in the docs.
[2.23.0]
Update metabase to 0.57.1
Full Changelog
breaking change: Removed support for legacy SQL drivers
feature: Added support for new database connection pooling
feature: Improved dashboard loading performance
feature: Enhanced data visualization options
bug fix: Fixed issue with incorrect data caching
bug fix: Resolved error when exporting large datasets
bug fix: Corrected UI glitch in the settings panel
[2.8.10]
Update cal.com to 5.8.12
Full Changelog
feat: new workflow variable booking title by @dhairyashiil in #24308
refactor: api v2 breaking changes CI check by @supalarry in #24999
refactor: v2 api event-types/:eventTypeId access by @supalarry in #24969