@jodumont from experience I know MX doesn’t work because the mailserver doesn’t respond to IPv6. That way we’ve lost some mails before we discovered that.

@girish I have removed that file. done sudo apt auto clean and rebooted the server. After reboot and runnning the /home/yellowtent/box/setup/start.sh command, everything worked again. That key was the issue.

@girish Thanks, that seems to have taken care of it

I have improved the check now to see if there is atleast 1GB before applying an update.

@girish I went ahead and made the change manually and we are back in business. In case anyone else looks at this, the home/yellowtent/box path is on the server hosting cloudron.

@brutalbirdie You are God level Cloudron user! You must absolutely love Cloudron. Thanks for giving me an idea of what is possible.

@d19dotca yes firehol is very interesting but also very dangerous, especially with IPTables our mind crossed each other, I just mentionned FireHol in a request: https://forum.cloudron.io/topic/6009/firewall-per-domain-container

@kirakodo what is the output of this command that tests IO on your system? dd if=/dev/zero of=/tmp/test1.img bs=1G count=1 oflag=dsync ; rm /tmp/test1.img

@girish I couldn't recover MySQL so I just decided to install Debian on my server and run Cloudron inside of a Ubuntu VM so I can take snapshots incase if that happens to me again. Thanks for the help tho

@girish thanks for the support. Some mails arrive in spam. I will check DKIM, SPF, DMARC, PTR records. but that's my problem

@iamthefij Ok. Just restored matomo from backup again and it's all good.

@archos no worries glad you got that sorted out.

I have pushed a new CLI version v4.12.7 that fixes this.

FYI - something in the Cloudron dashboard went stale, hence when reloading the dash, the FM began to load properly.

@mannyc1701 thanks, I pushed a fix as well for next release - https://git.cloudron.io/cloudron/box/-/commit/fdefc780b4f687ec5ff508b1a37270492612f2a3

@gary-host It was a caching issue. I am able to see the dashboard now!

I've had this come up as well. An app restart fails the first time as well. The retry-task eventually succeeds, so what @girish said is a faster way with less clicks.

@saphirata if your IP of your ISP connection (local ip) keeps changing, then you need to keep the DNS records in-sync. So for your use-case it means you have to keep adjusting the settings in Cloudflare. Maybe for a start you could disable Cloudflare proxying and use it normally as a DNS service, then configuring your domain in Cloudron to use our Cloudflare backend and enable https://docs.cloudron.io/networking/#dynamic-dns

FWIW, a great DNS tool for checking on DNS propagation progress is here: https://dnschecker.org