Bunny resynced the DNS. I restarted the VPS and retested. It's fetching fine now. Fingers crossed it stays that way.

@TheMoodBoardz YW dude

I enabled Dynamic DNS in Cloudron. Then, I turned off the VPS, deleted its IP's (ipv4 and ipv6) and reassigned new ones. Manually updated DNS record of my. to point to the new domain and it came up in 2 mins. Resynced DNS and it looks like the SMTP issue is fixed.

yes, the snapshot folder is the folder where the backup is initially made and then from there it is rotated. In your case it was also part of the previous config.

Yes, this was a bug. I have fixed this for the next release (8.0.1).

@tenacioustech interesting fix Cloudron.io does have IPv6 support. Is the issue that IPv6 is not working on your network ? $ host cloudron.io cloudron.io has address 165.227.67.76 cloudron.io has IPv6 address 2604:a880:800:10::b66:f001

Yep, as usual. It's user error. I was using the box config backup. I just had to adjust the backup path to point to the app. I figured out the correct path by logging into my Backblaze dashboard, browsed through the bucket (by date) and the file "name" is your path. Copy/paste into the import box along with the box settings and voila!

@samuelandert-eth the way it works is that Haraka (the mail server) parses the HTML and injects HTML signature. Maybe it's failing to parse apple mail content properly. Do you think you can paste the source of a sample apple email at https://paste.cloudron.io ? This will help us debug further and fix the issue.

@mmtrade yeah, that's the problem. IPv6 is not working on the server. Can you also try ping6? $ ping6 ipv6.api.cloudron.io PING ipv6.api.cloudron.io (2604:a880:800:10::b66:f001) 56 data bytes 64 bytes from prod.cloudron.io (2604:a880:800:10::b66:f001): icmp_seq=1 ttl=45 time=122 ms 64 bytes from prod.cloudron.io (2604:a880:800:10::b66:f001): icmp_seq=2 ttl=45 time=235 ms

Fixed with next release

Fixed! Thank You!

If you relocate an app (changing app data directory) all data will be copied over. See https://docs.cloudron.io/apps/#data-directory Please note that not all filesystems are suiteable for this. The docs link has some info on that.

The process is described at https://docs.cloudron.io/backups/#clone-app

nevermind, i found my mistake, i copied my public key in, not the private key -.-

@nebulon Thank you for your response. Yes, it seems the issue is indeed with hardlinks. I have them enabled. I will try to wait for the Cloudron update, or I might consider using Borg for backups to the Storage Box. That should probably resolve the issue. Another option is using rsync with the -H switch, but I haven't tested it yet. Thank you very much for your help.

@joseph Thank you and yes, did all those, and was in communication with tech support. The issue is actually mysteriously resolved and I'm just trying to figure out what happened so I can share that in this thread and hopefully avoid repeating this issue in the future.

Hi guys, A quick update for anyone who may run into this in the future. Yes, that did the trick, I was able to create a /mnt/sync/ directory under Volume, and executed "Retry Task." One thing that I did notice was that I couldn't restore from the last version of the backup, but the one previous to that went through just fine. Really glad for such such a smooth migration process!

Ah the Cloudron is on version 7.5.2 which had a bug here. This is fixed with v8.0 already