Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Cloudflare blocking my new VPS IPv4 range – HestiaCP and SSL issues

vpscpvpscp Member

Hi everyone,

I recently moved my VPS to a new dedicated server from my hosting provider.
The old one worked perfectly fine — no IPv6, no SSL issues.

After the migration, I was assigned a new IPv4 and IPv6 range, and ever since then:


🧩 Issues:

  1. Cloudflare Error 1000 – DNS points to prohibited IP

    • This happens when Cloudflare Proxy is ON.
    • If I turn the proxy OFF, the site loads fine.
    • The error appears as:
      Error 1000: DNS points to prohibited IP
  2. Let's Encrypt SSL Timeout (HestiaCP)

    • When I try to issue SSL via Let's Encrypt from HestiaCP, I get:

      Error: Let's Encrypt validation status 400 (Timeout during connect)
      
    • Happens only with Cloudflare-protected domains.

    • Non-Cloudflare domains work fine.
    • When IPv6 is enabled, the SSL sometimes works; with IPv4 only, it fails.
  3. HestiaCP installation

    • HestiaCP installer only works when IPv6 is enabled.
    • When I disable IPv6, installation hangs during "Installing dependencies...".
    • Seems like all IPv4 requests to Cloudflare-hosted mirrors (apt.hestiacp.com, deb.nodesource.com, etc.) time out.

🔍 What I think:

  • It looks like the new IPv4 range from my hosting provider is blocked or filtered by Cloudflare.
  • Cloudflare Radar scan shows Network connection closed.
  • IPv6 works fine, IPv4 doesn’t.

❓ What I want to confirm:

  • Has anyone else seen Cloudflare blocking a whole IPv4 subnet or ASN like this?
  • If yes, is there any workaround other than asking the provider for a new IP range?
  • Could this be fixed by Cloudflare support if the hosting provider contacts them?

Thanks for any insights!

Comments

Sign In or Register to comment.