@alexsunny123 ok there are quite a few variables in the mix here it seems. For a start, can you connect to the Cloudron setup view using the public IP address from your ISP on port 80 and 443?

To rule out some other maybe interfering parts, disable the Cloudflare proxying.

Since you mentioned email, on a residential connection you will most likely require a mail relay to work properly, anyways port 25 will most likely be blocked by your ISP. Cloudron as mail relay support for various providers though.

Lastly for Cloudron it doesn't really matter if bare-metal or VM, so there are no special docs about this. You should be fine as long as you have vanilla Ubuntu 20.04 server installed.

@girish yep, it loads, awesome, thank you👍 😊

@guyds Ah, good to know. Did not know this limitation!

Makes a lot of sense.

@theciscogeek When using Cloudflare, we have a check as to whether it's proxying and we skip the DNS propagation checks - https://git.cloudron.io/cloudron/box/-/blob/master/src/dns/cloudflare.js#L274

@robi yeah, with ecommerce being our primary business, we're invested in this. We have 12 very experienced devs on the team but just a few of them have had time to start looking at Cloudron this week. In this for the long-term though so I'm sure you'll start to see our work filtering through very soon.

@Lonk Yup, that sounds right. In fact, it seems that Cloudflare made the nginx+http3 patch (but not sure if nginx itself ended up using that).

Thanks, now I understand

Truly heroic support! 🙌 Happy to know this is covered and tested 🙂

@girish

This is intentional because the root domain record can be in use on another server/app/website.

Right, that makes sense.

I added a redirect from the root domain and it solved all my problems. Thanks for the quick help.

@girish Done - https://forum.cloudron.io/topic/3777/support-optional-cloudflare-proxied-record-creation

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

af9fe70e-4e52-450f-8527-72561927c428-image.png

unless it will not work with only Zone -> DNS -> Edit permissions at Cloudflare
ab12edf9-baea-4e95-8941-1268a7cb5a96-image.png