When your website is proxied through Cloudflare and you see Error 1000: DNS Points to Prohibited IP, it means the domain's DNS settings are pointing to a restricted IP address—typically a Cloudflare IP. This misconfiguration prevents the domain from being properly accessed.
10Web’s Cloudflare Enterprise CDN integration is available with the Speed Booster plans and as an add-on for Platform plans. If you're using the integration, this guide will help you identify and fix the issue.
Common causes
The most common cause of this error in the context of 10Web’s Cloudflare Enterprise Integration is when the Original Server IP you input in the CDN settings differs from the actual origin server IP your domain is pointed to. Therefore, the first troubleshooting step to take would be this:
- Enter your 10Web dashboard at my.10web.io and click Manage under your Cloudflare-connected site.
- Go to the Website Booster > Cloudflare CDN menu and proceed to the Settings tab
- You will see the Original server IP field there. Please make sure that it matches the actual origin server IP your domain is pointed to.
Other common triggers include:
- An A record in your Cloudflare DNS pointing to a Cloudflare IP address
- A Load Balancer Origin pointing to a proxied record
- An A or CNAME record targeting another reverse proxy (e.g., nginx using proxy_pass) that forwards the request back to Cloudflare
- An X-Forwarded-For header exceeding 100 characters
- Multiple X-Forwarded-For headers in a single request
- A CF-Connecting-IP header present in the request
- A mismatch in Server Name Indication (SNI) at the origin server
How to fix Error 1000
In most cases, the error is caused by having more than one proxy in place. Since Cloudflare acts as a reverse proxy, stacking it with other proxy services can result in conflicts.
To resolve the issue:
- Check for additional proxy layers: Identify whether your domain is also routed through another proxy (e.g., Sucuri, or a reverse proxy configured on your hosting server if you're not using 10Web platform hosting).
- Locate the source of the conflict: Examine your hosting setup or third-party services to find any active proxy configurations that could be overlapping with Cloudflare.
Disable the conflicting proxy Once you've identified an additional proxy, disable it so that only Cloudflare's proxy IPs—assigned during the 10Web CDN setup—remain active.