Cloudron Forum

Ok, I solved it. I had to delete all my DNS settings that previously existed and then reset them. Once I did this within milliseconds Cloudron started working.

Whew, I was sweating bullets there for a minute.

@nebulon I find the solution taking infos from this forum .

In fact, I opened port 53 TCP and UDP and Cloudron can resolve domain names.

Configuration now is:

firewall template.png

All seems to working fine... I marked this thread as "Solved" 🙂

@nebulon Yes before rebooting I tried to umount-remount but it seems it has been impossible due to an error... So I decided to restart.

About auto-remounting it will be an amazing feature

This will be part of 7.2.1

@mehdi Not sure I know enough yet about handling updates, patches & security so just running in good faith on all that at the mo.

Happy? Yes.

Confident? Sure - until something goes wrong 🙂

Just always thinking about prevention being better than cure.

Ok I gotcha myself because anyway I create my own pain 😉

so from what I understand
to being able to restore Cloudron verify the DNS first than app/data

I forgot to authorize my new IP in my Cloudflare API

code 9109 is probably related to the fact it was unable to edit the DNS.

correct in your case this should not be any issue as this is mounted like a regular ext4 which supports hardlinks just fine.

To know the backup scope, you can sum up all the apps listed there + email data + box data. Then you would have to multiple that by the number of backups which are stored (eg. once every day for 1 week or so) This would be the maximum of storage required using the tarball method. For rsync, it would be much less since it would do incremental backups.