@sponch I have a question: Were the backups you're trying to restore still in their original location (where they were first created), or had they been moved/copied to a different Hetzner Box before restoring? Same location (only the prefixed changed months ago - should not concern the recent backups) I’m asking because the files I tried to recover (unsuccessfully) had been transferred between Hetzner Boxes, and I’m wondering if that could be the root of the issue. Edit: Were the files you tried to restore from the Hetzner Box originally created by the same specific Cloudron instance? Or were they from a different instance (e.g., after a reinstall)? I’m asking to help trace the root cause of the issue. Same instance. Nextcloud is backed up daily. Last fews days restoring always ends up with same error. @sponch @james Another hypothesis that comes to mind is the use of special characters in the password, which might not be interpreted correctly during the backup recovery process – Eg. a Gui problem Just restored another (unimportant) app from same backup day. Worked perfectly.

if I message support@ then I got the email from somewhere. That page would have also told me to search forums first. Setup intercom with Fin ai or something (chatwoot have ai now I think) so you can do support without having to do support. Ask yourself if you found THIS process more efficient?

I get this: docker inspect 5130e1789e1e | grep Memory "Memory": 5368709120, "MemoryReservation": 0, "MemorySwap": -1, "MemorySwappiness": null,

Have you checked the logs already? Go to Domains -> Renew Certs . That will show the logs for the renewal . Which DNS scheme/provider are you using? Manual/Wildcard or one of the programmatic ones?

@nebulon said in Disk usage update problem: Ah thanks for the clarification. Maybe we can think of some different UI which has an overview and some drilled down info if wanted. This would be awesome

It correctly resolved the issue. Thank you a lot !

Hello @Lomeu Unfortunately I can't provide much support with the Google Workspace LDAP. Just to make sure, you did follow the google guide for LDAP clients? https://support.google.com/a/answer/9048434?sjid=18438745481174821656-EU

solved by adjusting existing DNS A Record entry. Changing from aaaa:bbbb:cccc:dddd:: to aaaa:bbbb:cccc:dddd::1

yes @james I have also thought of using that. but manually running it on all mailboxes sounds like a pain I don't want to go through. I guess the current way I envision it is writing a script for imapsync that uses the api of cloudron to get all mailboxes and impersonates the users of the mailboxes to auto run imapsync on them. but then again maybe a block of the port is the way to go, so I don't have to write that script. the whole backup and recover process should be done quite quickly anyways. I am wondering though if this is not something others have gone through as well?

awesome as always, much obliged

You should do this - https://docs.cloudron.io/troubleshooting/#domain-issues-expiry

With help from Grok: https://grok.com/share/bGVnYWN5_baedbb67-0507-41f0-b26d-29da9f1b7f94 Exported users to delete with mysql --user=${CLOUDRON_MYSQL_USERNAME} --password=${CLOUDRON_MYSQL_PASSWORD} --host=${CLOUDRON_MYSQL_HOST} ${CLOUDRON_MYSQL_DATABASE} -e "SELECT id FROM user WHERE FROM_UNIXTIME(created_unix) > '2025-03-01'" > /app/data/users-to-delete.txt Deleted the header name with vim Switch to git user sudo -u git bash Run a command to use the cli to purge each user in the list: while read -r id; do /home/git/gitea/gitea -c /run/gitea/app.ini admin user delete --id "$id" --purge; done < /app/data/users-to-delete.txt All bad users cleared but one (not sure why), deleted manually. Done!

@d19dotca said in iDrive E2 Backups Failing More Frequently: What I had to do was delete the region hostname and re-enable it, which created my backup buckets somewhere else and allowed me to proceed without issue. The unfortunate part of this though was that it deletes all the files of course in the prior region, so what I did was first download a few important backups from it to my local disk and reloaded afterwards. I had the same rate-limiting issue with IDrive E2, but with a twist: my bucket was originally blazing fast in one region. After I deleted and recreated it (like you did), it became painfully slow—the exact opposite of your experience! I suspect their ‘region reassignment’ doesn’t guarantee consistent performance, maybe due to uneven server loads or hidden throttling. Moral of the story? With IDrive E2, if your bucket works fine, don’t touch it—even if they tempt you with ‘better regions.’

Ok if I switch it to "Direct disk" it fails to boot but "GRUB (Legacy)" kernel option seems to boot fine.

@girish Yes, I no longer got the Gmail issues when I created my own system service to implement the iptables rule. So it seemed to do the trick. The IP tables rule to add is really just this: iptables -t nat -I POSTROUTING -s 172.18.0.0/16 -o enp3s0f0 -j SNAT --to-source {FLOATING_IP} Where FLOATING_IP is really just replaced with whatever the recognized IP address is that’s used in the DNS records for the MX record. I supposed it could be further improved to only be applicable to the mail container rather than all Docker traffic. And of course the interface would have to be dynamic too. I guess an alternative is for me to create additional MX records with the other IP addresses but then it’s manually done and prone to mistakes/issues. In my opinion, I think we really need an option to select the outbound IP interface using Cloudron for the mail component, in order to avoid the Gmail issues (and any other provider who will use FCrDNS for verifying or rejecting emails in the future). I recognize this may not be a common concern as most people probably only have the one IP address of each type and so the DNS records if setup automatically by Cloudron will use both the IPv4 and IPv6 address, but for those of us who use a floating/failover IP addresses that we want to be the one true IP address being used, this becomes an issue without that workaround in place.

Same here (since sending through Brevo (Sendinblue)).

@girish Thanks for this. Access given / mail sent. Appreciate the help.

@nebulon wonderful, thank you for the clarification!

Thanks, I don't use cloudflare, but a good thing to be aware of.