@p44 It is to a self hosted SAN

@joseph said in Bloated n8n backup: du -hcs . Sorry, I misread this. I navigated to cd app/data/ and it's 906MB. My other post was running that from app/code

@philkunz said in Backups still not verified or what?: But that points to how important the e2e read back step is. absolutely, that is why we are adding the validation in the first place. Having checksums of what we expect is the first step, next then will be the task (can be quite heavy task, so this won't be automatic probably) to read back and recalculate the hashes.

Since we debugged some other issue on that server, was also taking a look at the disk I/O. So basically the mysql service is doing a lot of disk I/O (also as see in the screenshot). It does seem the mysql addon is just queried and written to a lot. So likely one of the many installed apps using it might commit a lot to the database. I didn't want to stop apps, but maybe you can try to stop individual apps which use mysql one-by-one to hopefully find the one which causes the constant writes.

I investigated this on support@ . The issue was that the server had an incredibly slow disk and the iops was really bad (like 30MB/s) . The VPS provider is fixing their raid configuration .

@nebulon said in What's coming in Cloudron 9: Fixed with https://git.cloudron.io/platform/box/-/commit/5160f22d912d7524fff068dcc6efecf818b4f087 to limit the sidebar width to max 300px as some compromise to still display large names (though the are limited to 64 characters anyways, but lots of w will be clipped now) Thank you very much. Perhaps the login page can also be adjusted at some point so that it doesn’t become distorted when displaying a long name like in the example screenshot (red). Many thanks! [image: 1765528547238-99a8ea21-84a7-4fd6-9fba-4f583598df1d-grafik-resized.png]

The schema is documented in this file - https://git.cloudron.io/platform/box/-/blob/master/migrations/schema.sql?ref_type=heads . completed BOOLEAN DEFAULT false The id has to be unique in oidcClients table. Can you check why you have a duplicate? Maybe you can delete the dup entry and run the migration again.

It was already updated yesterday

Apologies, I got hung up on your point about the 'combination of search and filters' since I'm experiencing only getting the amount of entries that's set in the per_page value even when using only the search box without any additional filters active. I'm really looking forward to the rework then because right now even basic stuff like checking if a specific email was delivered or if a specific user logged in is a bit of a pain since I have to unfold the details of the first entries just to make the scrollbar appear to load more.

@joseph oh geez, ok thx ️

I had this happen at a recent upgrade to Cloudron 9. All apps but Vaultwarden were working, and the "Cloudron has no app configured for this domain" message was showing. Indeed, it was just a hard refresh to solve it in Zen / Firefox (how odd!)

We will show the domain, for which the API call failed, in the error message for a start with next release. https://git.cloudron.io/platform/box/-/commit/f421fd771ff0e0550381d012414a6c35c8fd2afe

@girish Thank you, girish for the update!

@girish Thanks ! I replaced the /home/yellowtent/box/src/storage/gcs.js with the patched version and don't get the "old backup not found" error. the backup is listed in System backups. everything seems to be fine ! Thanks a lot for your help !

Fixed in https://git.cloudron.io/platform/box/-/commit/9773c02e7d6fda7a9704ad8866d7e16ba11dcae3

@joseph I guess you are right. I'm trying to figure it out. My son is working a lot but I'll try go get access to his computer through Tailscale so I can reach the local network with a desktop and UI and try to reset the router.

Minio is basically dead for community edition. I rolled back to image: quay.io/minio/minio:RELEASE.2025-04-22T22-12-26Z (last version with all management features - don't expose it publicly for security reasons) Then: Configuration > Region > Restore Defaults That wiped my region entry and now Cloudron connects properly again. Time to consider successor software now.

Success! Thank you!