Cloudron Forum

Hello @reesskennedy We are already aware of the issue and are pushing an update tomorrow.

Hello @mononym Valid point and done. https://forum.cloudron.io/post/125498

I guess I have more questions around the integrity check: What is the exact criteria for "green" or "red"? Here's why I'm asking: After recovering my Cloudron, I noticed that one backup location, an external drive, is still present in the configuration. BUT: that external drive is no longer mounted (or even connected, for that matter). I haven't disabled the location in Cloudron yet. Now here's the surprising part for me: Cloudron still claims it performed a backup to that location. And when I run the integrity check on that backup, it shows up as green. For a backup that, as far as I can tell, doesn't actually exist on accessible hardware. I realise I might not fully understand how ext4 mounts work behind the scenes, but I do know that the physical hardware isn't connected. So this makes me wonder: how does the integrity check actually work under the hood? Does it only check metadata or local records, rather than verifying the actual remote files? Would love to understand this better, because right now a "green" integrity result feels less reliable than I initially thought. Thanks for bearing with me.

Grist now has enterprise options again. https://forum.cloudron.io/post/125494

I figured it out now, see below. At apptask.js:693, updateCommand calls omit() on the old manifest's addons field without guarding against it being absent. When the installed manifest has no addons key, addons is undefined, causing Object.entries(undefined) to throw: TypeError: Cannot convert undefined or null to object at Object.entries (<anonymous>) at Object.omit (file:///home/yellowtent/box/src/underscore.js:17:38) at updateCommand (file:///home/yellowtent/box/src/apptask.js:693:28) Because this is a plain TypeError rather than a BoxError, the catch block in run passes it to makeTaskError, which asserts error instanceof BoxError and crashes — surfacing a secondary assertion error to the user instead of the real one. To reproduce: Install an app whose CloudronManifest.json has no addons field Add "addons": {} to the manifest and push a new image Trigger an update from the dashboard Expected: Update succeeds, or fails with a descriptive error about the manifest change. Actual: Task crashes immediately with AssertionError: assert(error instanceof BoxError), hiding the real cause. I re-installed the app, which solved the issue. I still believe the views should be consistent in error handling though.

Hello @crush33 Thanks for the details.

Hi @james thanks for your reply. I just removed and reinstalled the Onlyoffice app in my Cloudron, I checked and it's correctly running, so I changed the secret key in the production-linux.json on both places and then added the key in Nextcloud ONLYOFFICE app, and tried again in both Firefox and chromium without blocking app enabled but still get an error. I switched to Collabora and it seems to work fine, which is a good workaround so problem solved

Can you check the logs for any error? Regarding the e-mail, the issue could be a wrong email setup. Have you installed it as a Cloudron community app?

Hello @dark The team has send you a reply.