@Jarod In the AWS Marketplace Image (AMI) , route53 is disabled in the setup screen. It is apparently against Marketplace policy to take route53 API credentials (a member of their team had reached out to us and notified us about this). So, if you use the AMI, then the setup screen will not show route53 as an option anymore.

Unfortunately, we ended up breaking https://forum.cloudron.io/topic/11993/backuptask-crashing-after-8-0-update . But yeah, overall the fix is good.

@girish said in WordPress app container stuck on updating from package version 3.7.2 to 3.7.3: This happens with apps which contains files that change their size when the backup is going on. ... Maybe you have some plugin that writes to somewhere periodically? Thank you @girish Great advice and just the clue we needed. We figured out what that was, stopped it and then we could take a WP backup manually; and then we were also able to update to the latest packaged WP version 3.8.0 Thank you once again; your prompt help is much appreciated You can mark this ticket as resolved; cheers!

Hey @girish, @nebulon, thanks for coming back to me so quickly! Happy to report that the fix worked wonders, and the backup completed successfully. As for our setup, we set up the backup server a while ago now, my memories are not the freshest. But IIRC we are using OpenSSH Server for Windows Server. And from what I can see Windows shell uses mklink to create hard links. But I have never used it.

Hello, correct, it is the subdomain. This all seems to have been solved by restarting the app

@shrey The fix didn't make it to Cloudron 8, but will be in Cloudron 9 (2 months or so from now). I can post a link to the patch when I push it and you can give it a try.

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.