If the apps were still reachable, then possibly the healthcheck just got stuck, we have seen this in the past Cloudron 9 has some improvements in that area, so hopefully this will not be happening then.

@CaeruleusAqua which S3 provider are you using?

Mystery solved! https://forum.cloudron.io/post/35426

Incidentally, I was just looking into this and fixed a race in our code - https://git.cloudron.io/platform/box/-/commit/084050bb2fa8e2ccdf4ba72f89b48fb089628e5c . But the original issue is still that hetzner dedis periodically lose IPv6 connectivity, I am not sure if this is just specific to our demo server or not . But as @james said, a retry fixes it usually. But there is a bug which was breaking retry ! I have patched the demo server but let us know if you see this again!

@OrezBodajoy wow, great find

Thanks @james -- yes, this is solved.

I was using ChatGPT for some assistance on this, as I'm still struggling with this issue off-and-on-again, and it recommended applying this to the Haraka configuration: [outbound.limits] gmail.com=1/30s Essentially rate limiting delivery to Gmail which should lessen the likelihood of being rate limited by Gmail. Is there a way for us to configure this at all for testing purposes? I can't seem to create the outbound.limits file due to the read-only file system in the mail container, so I'm not sure how I can try this. Interestingly though, I noticed today that this issue only seems to happen if sending from a hotmail.com / outlook.com address to the hosted Cloudron domain name which then forwards to the gmail.com address will this issue be triggered. If I send to the same distribution list from my other email addresses, it seems to not trigger the rate limiting response. So it seems possibly related to the sending domain originally before the hosted domain itself, which Gmail occasionally seems to have problems with. Since the error is also sometimes Gmail has detected this message exceeded its quota for sending 4.7.28 messages with the same Message-ID, is there any possibility that Cloudron's mailing list feature could rotate the message-ID to avoid Gmail flagging it?

Issue was resolved with support@cloudron.io

Hello @rene-dhemant and welcome to the Cloudron forum This question should be targeted at your hosting provider, and they should have a guide for that. Example guide from some DigitalOcean: https://docs.digitalocean.com/products/volumes/how-to/increase-size/ WARNING Always make sure you have a valid backup before doing anything like this. To boil it down, it should be very simple. ssh into your server run the following command:resize2fs /dev/sda3 confirm the size of your partition with the following command:df -h /dev/sda3 But please check with your hosting provider if he offers a guide specific to their platform.

I have updated https://docs.cloudron.io/backups/#restore-cloudron and https://docs.cloudron.io/guides/download-backups/#backup-file-names . Bit of a hasty edit but time is really right these days!

James, Thanks, that's useful, I can use that as a workaround. I will need a 20GB pool size to keep things running the way I want. Thank you. Lee

Nevermind, it was just a matter of being patient. Everything was set up correctly. For anyone else using Namecheap, it takes a minute for the DNS to sync. Give it some time (quite a bit more than you think) and it'll work.

Maybe https://forum.cloudron.io/topic/1579/var-lib-docker-overlay2-getting-full?_=1760112116784 is helpful: @nebulon said in /var/lib/docker/overlay2 getting full: For a start, docker images are often quite large, composed of a multitude of filesystem layers on top of each other. To mitigate the problem a bit, all Cloudron apps share the same base image, that helps a bit. The appsdata folder really only contains the data from within the apps, so that heavily depends on your own usage. The application code, so to speak, is inside those docker images.

I updated redis to 8.2.2 - https://git.cloudron.io/platform/box/-/commit/3547be34010a737d9fbd5aed5bb9e787eeff5456

@girish Thank you for addressing this annoyance in 9.0.0.

Cloudron 9 has pretty much the same flow here. Maybe we have to revisit what the main app cloning use-case is, to figure out a better flow there.

Hello @dffla For the Appstore you need to create a Cloudron.io account and use that for the login. Your own server/cloudron account is not the same as the Cloudron.io account.

@andreasdueren you're welcome, I forgot to post the Hetzner docs, they also have a bit of information on that. Speeds are fine, never had any issues with various kinds of media.

This should be fixed in Cloudron 9, where a backup failure notification email can be configured per user.