Closed due to inactivity

Since 2022 a lot has changed for backups and will change even further with Cloudron 9. Closing this topic for now.

I have responded from support.

@necrevistonnezr Thanks a lot, it seems to be a very good strategy, but implementation is out of my personal knowledge.

@jdaviescoates Yes, with encryption. Me too, I never had issues with Hetzner Storage Boxes but since few months various problem happens...

It worked! Thank you so much!

@andirahmat you should remove it once the DNS has propagated. Otherwise, you can only access your dashboard from your laptop and nowhere else!

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