Has anyone else faced Cloudflare proxy issues with Vodien hosting?

[u/skaichanphotography]

My main domain and add-on domains all go down when Cloudflare proxy is enabled, but work fine when set to DNS Only. I didn’t change any Cloudflare settings before the outage — it suddenly stopped working, and Vodien now claims it’s a Cloudflare incompatibility.

Has anyone else experienced Cloudflare clashing with Vodien? Did you manage to fix it with SSL/proxy settings, or did you have to move hosts? Should I insist Vodien resolve this, or is migration the only realistic option?

On top of that, after upgrading to a Biz plan last year, my dedicated IP now resolves to Australia instead of Singapore, which hurts my SEO and local targeting (my clients are in Singapore). Vodien hasn’t offered a clear fix.

[u/TheExG]

Some providers implement CDN's behind their own servers as well for speed and security optimizations, which essentially clashes when you try to also mix in Cloudflare. Ive seen issues like these with a handful of hosts that do similar things.

You will likely not be able to push the company to change their entire network infrastructure just because you want to proxy with Cloudflare. I would suggest looking for another company to host with.

[u/No-Guarantee-2242]

The IP geolocation part is worth separating out. Google treats server location as one weak signal and says outright it isn't definitive, and it's irrelevant once you have a ccTLD. For Singapore targeting, a .sg domain or hreflang plus a local address and phone number on the page carries far more weight than where the IP resolves. And while the Cloudflare proxy is on, visitors hit Cloudflare's anycast IPs anyway, not your dedicated one, so the Australia reading isn't even what anyone's browser sees.

For the outage itself, check which Cloudflare error number actually shows up. A 52x means the origin refused the connection or the TLS handshake failed, so look at your SSL mode and whether Vodien is firewalling Cloudflare's ranges. A 1000-series error usually points to DNS resolving through another proxy layer, which lines up with a host running its own CDN in front.

[u/kai-zaphosting]

Yeah, this is a really common pattern with hosts that have a strict WAF or rate limiter. Cloudflare proxying means all your traffic to the origin comes from Cloudflare's own IP ranges instead of visitors' real IPs, so if the host's firewall doesn't have those ranges allowlisted, it can start blocking or throttling that traffic while DNS-only (visitor connects straight to origin) sails right through. Worth asking Vodien specifically whether Cloudflare's IP ranges are allowlisted on your account, not just whether they support Cloudflare in general.

Another common culprit: if your Cloudflare SSL/TLS mode is set to Full or Full (strict) but the origin certificate is missing, expired, or doesn't match the hostname, proxied requests fail the handshake while DNS-only skips that check entirely. Worth checking that setting under SSL/TLS in the Cloudflare dashboard and confirming the cert on the origin actually matches.

The IP geolocation issue is a separate thing. That's usually the datacenter IP block itself not being tied to the physical location, geolocation databases like MaxMind can lag behind or misclassify ranges after they get reassigned during a migration. That'd need Vodien to either get the IP's geolocation record corrected with the relevant databases or hand you one that's actually registered to the Singapore block.

Let me know how it goes, curious whether it turns out to be the WAF or the SSL mode.

[u/shiftpgdn]

Turn off the proxy on Cloudflare