@girish I seeeeee! You've thought all this through before! OK, I learned new things from your explanation. Prob one just for the documentations then unless you think a per-App setting would be easy enough? It's only saving going into Cloudflare to delete and re-add the records but then my next research is going to be into https://dnsmadeeasy.com. TBH as I think Cloudflare is more a pied-piper following for their good marketing than for the essentials that are often better handled at the host (like Anti-DDoS, for which I do like Hetzner covering on the network level).

So, it seems like giving the app a "relocation" by pressing the save button under the Location config tab & a quick Cloudflare proxy off-on, and then some time is the fix. EDIT So it is Cloudflare that is the problem and not Cloudron. Specifically their proxy

OK, @Trankery informed that this happens more most/all freenom domains. This includes .tech as well.

@bangden07 Ah, that's a smart work around! I just noticed that you had SSL issues on the root domain. The wildcard cert only covers subdomains i.e *.foo.com but not foo.com. Cloudron still has to get normal certs for foo.com. I guess after a week, you can remove the cloudflare proxy.

THANK YOU. I use Cloudflare as my DNS provider. Looks like they have some sort of caching feature called Cloudflare Rocketloader which caused this conflict. I Turned it off and it worked now. Much appreciated! @nebulon https://community.cloudflare.com/t/how-can-i-remove-the-rocket-loader-script-from-the-header-tag-on-my-website/4229

@girish said in Using Cloudflare without Global API Key: Can confirm that all zones access is not required in cloudflare anymore. Will update docs. I just added a domain than, just to be more concise we have to specify the Zone Name unless it will not work with only Zone -> DNS -> Edit permissions at Cloudflare