@saphirata if your IP of your ISP connection (local ip) keeps changing, then you need to keep the DNS records in-sync. So for your use-case it means you have to keep adjusting the settings in Cloudflare.
@girish Yes there are definitely more than 20 events, and the Next page still works to load more, it's just that dropdown to change how many records are shown at once which has an issue. I just updated to 7.0.3 so will try soon, unfortunately it seems the email logs were cleared after update, so there's no records in there at all now.
@girish yay! Haha, thank you so much!!! That one was really annoying even though minor. Lol. It happens after a Cloudron migration (not just upgrade) and stuff too FYI but I’m assuming you already knew that.
Edit: actually maybe not… I also had upgraded Cloudron the very next day so I likely just saw the result of that instead. Ignore me.😅 glad it’s fixed though!!
@nebulon thanks, i did get this figured out with zulip's docs on reverse proxying and using certbot on the cloudron host again but I know I'm playing with fire. I get why this isn't a common use case, I can't imagine a lot of people host at home
Is this for your backup? Cloudron does not backup images (and code), just your data. From your screenshot, it's only going to take 1.13G (nextcloud) + 6.5M (bitwarden) + 520K (box) + 212K (email). So, it's way less than 2GB per backup. If you store like 30 full backups, it's still under your object storage.
@scooke yes, you can mix between Cloudron's automation and manual DNS changes. In fact, that's the normal and only mode of operation.
The automation is only adding and removing things that you would have to do normally outside Cloudron. For example, when you install an app, you have to setup A records. When you uninstall an app, you remove the A records. This is all the automation does. If you try to install an app in a location and there is already a DNS entry in your DNS provider, Cloudron will inform you of the same and let you 'overwrite' it or cancel the app installation.
Same goes for email stuff. It sets up things like DKIM/SPF records automatically. These are updated carefully to not collide with existing entries. The MX record is only touch if you enable incoming Cloudron Email. Even in that case, there is a checkbox to not update DNS.
@aziz So, certificate for *.devz.cloud is already there, so if you install apps on subdomain it will work. Cert for devz.cloud (it is not a subdomain, so we have to get a separate cert from the wildcard cert) is getting rate limited.
You can just wait for 2-3 days to install an app on the bare domain and that should work. You should be able to install apps in subdomains in the meantime.