Strange Behaviour DNS Server Sync with Cloudflare

[firmansi]

I experience the issue with Cloudron when I sync the the DNS regarding to my IP Server changing, it happens to Cloudron version 8 and above. The Issue is the website can'be reached if I don't tick proxied in Cloudflare, but when I tick proxied, then everything back to normal, I don't know if i should report this issue with Cloudflare or Cloudron, but I think i need to tell this first in the forum in a hope I can get input from someone who might experience the same way I did

[nebulon]

So if you disable the proxying in Cloudflare, then you can access your Cloudron dashboard fine and also it has valid SSL certificates?

If that is the case, then there is something with the Cloudflare proxying. Otherwise it may be Cloudron related, for example maybe it fails to get LetsEncrypt SSL certificates or so.

[firmansi]

@nebulon I don't turn any proxy on for Cloudron Dashboard subdomain like my.abc.name.com, this left untouched, but the funny thing is, even it's not proxied, the website can't be accessed by using any internet service providers unless i turn on warp zerotrust vpn tunnel of cloudflare in our modem router. This issue also apply to website with regular subdomain with domain like abc.company.com which can be proxied enable, but when i unproxy the website then i can not access the website without turning on the cloudflare vpn. Because i dont want to use cloudflare proxy with nextcloud, but this issue makes me enable cloudflare proxy, otherwise the nextclud app can't be accessed

[joseph]

@firmansi cannot be reached can mean many things - dns error, network error, http error, certs error. I think we need more info on what exactly happens when you turn off proxying. Is there something special about your server we should know? Does it have a public IP or some private intranet server?

[firmansi]

@joseph It works fine by now, I have no idea what cause this, it just happens strangely sometimes

[joseph]

Mm, ok thanks, but I think we need more information to debug. Hopefully, it doesn't happen again!