@girish said in Use floating IP address only for outbound Cloudron Docker container communication: Thanks for sharing! I think if this works. But maybe the systemd service needs to be adjusted to run after cloudron-firewall.service (which also after docker.service) ? Oh that’s interesting, I can definitely make that change then just to be safe. I haven’t noticed any issues so far but I’ll adjust it regardless to test that out. Hoping something like this can be added to Cloudron more formally down the road so we don’t have to manually set these scripts up.

@ccfu great suggestion. I have put added your idea to the auto-reply now.

thank you for the help. I can mark this as resolved.

Here's a workaround via terminal: https://docs.cloudron.io/packaging/cheat-sheet/#file-ownership

I've also tried to create a mailbox (test@mydomain.coop) and set-up a redirect with roundcube to three "external" email addressed (@gmail / @posteo), delivery fails with all of them. So it is not specifically with Cloudron mailing lists but a bigger issue with redirects in general. @staff any clues?

@task Totally agree with you: "I'm grateful this happened early". If something has to happen, better sooner than later... I had the same issue with iDrive e2 (and ended up switching). Keep us updated on your Cloudflare R2 experience, okay?

@eddowding said in Can I move from yearly to monthly subscription?: Setup intercom with Fin ai or something (chatwoot have ai now I think) so you can do support without having to do support. Unfortunately, we cannot use AI for Support. The company's GDPR and privacy policy prevents us sending customer information and customer tickets into any AI or in fact any 3rd party service. It would be a big change to hand out data, and we have to inform all our existing users of this change as well. By design, we don't track anything about our users other than credit card via Stripe . The issue is not technical but mostly business related (as I understand).

@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 !

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

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.

@nebulon wonderful, thank you for the clarification!

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

Just tried this on the demo server. https://my.demo.cloudron.io (username/password is cloudron) [image: 1751631070055-fffc8926-44d5-49c4-af87-f77371ab2e98-image-resized.png]

Hello @shrey This is expected. Each Cloudron release and update has to treat every system the same and can not respect changes made by the user. Changes made to the core services need to be managed by the user manually.

Are you saying you are getting SPF_SOFTFAIL for all your emails? Note that the SPF fail here is for the domain of the incoming mail and not your domain itself.