Thanks for the fast response, @girish and cool to hear that you consider to implement it.

For future reference, you have to use resize2fs to grow the ext4 partition when you expand the disk size. This is atleast the case for most public cloud block storage and is a manual operation. Cloudron could potentially do this but I am guessing there is a good reason to not do this automatically, otherwise public cloud folks would have done this already

Thanks, investigating this. I suspect the node module is unable to parse the output because of something in the output. I will keep you posted here.

@girish I've never changed backup method no there should not be any remains from that. I did have a directory from april sitting around at 8.6 GB though . Removing that still leaves Other quite large though, so I'll appreciate more hints if you have any.

@nebulon Hi. Yes, indeed, the instance has 20gb. I deleted files from trash in Nextcloud and got back to normal with 6gb of free space.

Thank you @nebulon for solving this issue off-forums. For future reference: problem was caused by the external storage being unmounted after a reboot. Remounting the storage drive (I use a netcup VPS) and then repairing in the Cloudron dashboard solved the problem. Including the mounting in /etc/fstab solved this issue for following updates/reboots.

We have wasabi support coming up in the next release.

This was resolved offline - most issues where related to unbound (the internal DNS server) being down. Fixed by System -> restart unbound.

@doomilation Yes, what you have done should work. You don't have to move out appsdata and platformdata.

@nebulon Okay. Thanks for clarification!