Cloudflare error 1000 is labeled as a prohibited-IP error, but its documented causes also include a repeated proxy path, forwarding-header conditions and origin hostname issues. Compare the configured destination with the actual path to WordPress. A recent hosting move and a new reverse proxy require different evidence.
Guide reviewed: October 8, 2026. Interface labels may vary by version, account and device.
Map the complete proxy and origin request path
| Setup or change | Inspect | Useful evidence |
|---|---|---|
| DNS or hosting migration | Record versus provider-confirmed origin | Actual destination and previous value |
| Reverse proxy added | Its onward destination | Whether traffic returns through Cloudflare |
| Proxy adds headers | Forwarding-header structure | Which component creates or duplicates fields |
| Managed SaaS destination | Custom hostname registration | Provider-confirmed domain association |
Confirm the real hosting destination
Compare the affected hostname’s record with the origin address supplied by your current host. Cloudflare documents 1000 when an A record points to a Cloudflare IP or a load-balancer origin points to a proxied record.
For example, a public DNS lookup of a proxied site can return Cloudflare’s edge address. Copying that into the ordinary origin record sends the configuration toward the wrong part of the network. Ask the host for the verified destination rather than assuming a successful lookup revealed the WordPress server.
If a provider uses a managed custom-domain arrangement, follow its instructions. A conventional origin IP and a provider-managed hostname are different setups, and the provider should confirm which belongs to this installation.
Look for a request that returns to Cloudflare
Trace each hop: public hostname → Cloudflare → configured origin → proxy destination → application. If the proxy returns to the public hostname, have the administrator compare that path with the intended design. Include any redirect and separately changed proxy configuration in the incident record.
A reverse proxy at the origin may forward a request back through Cloudflare instead of serving the intended destination. Cloudflare lists that repeated proxy path as another cause of 1000.
Draw the intended connection in plain language: visitor to Cloudflare, Cloudflare to the hosting service, and the hosting service to the application it should serve. Compare that with the destination used by any reverse-proxy configuration.
If the proxy points to the public Cloudflare-proxied hostname, have the administrator review whether that arrangement sends the request back toward the beginning. Changing WordPress plugins does not explain that routing choice.
Cloudflare’s support guidance directs owners to work with the host or administrator on the origin arrangement. Keep the repair focused on the intended destination rather than adding another proxy layer without understanding the existing path.
Review forwarded headers with the server administrator
Record header names, duplication and relevant lengths in a sanitized diagnostic note. Identify where a proxy appends values. The administrator should correct the component responsible while preserving the forwarding information legitimately used by logging and application behavior.
Cloudflare documents certain forwarding-header conditions among the causes, including duplicate X-Forwarded-For fields and a value longer than 100 characters. Its reference also includes a request carrying CF-Connecting-IP.
If a proxy or application adds these fields, give the administrator the sanitized header structure from the failing request. Avoid posting private client addresses or session information in a public troubleshooting thread.
The relevant question is which component creates or appends the field and what should arrive at the next stage. Removing all forwarding information blindly can affect logging or application behavior. A reviewed correction should preserve the information the setup legitimately needs.
Keep provider and hostname issues in view
The official reference also includes an origin SNI issue and a SaaS provider using Cloudflare infrastructure without the required custom hostname. If either matches your architecture, the responsible provider or administrator needs to review that part of the connection.
For a platform-managed site, provide the domain and ask the provider to confirm its custom-domain configuration. An error originating in the provider’s account may not be fixable from your own Cloudflare dashboard.
A recent provider move is useful context. Keep the former and current connection details together so support can identify a destination or association that was not updated.
Verify each stage after a supported correction
Open the exact hostname and page that originally failed. Confirm the expected WordPress content, then test another relevant page or harmless workflow. A different hostname loading is not proof that the affected connection works.
If a new error appears, keep its message and time. The request may now reach a stage that was hidden by the original proxy or DNS problem. Investigate the new evidence rather than restoring a known incorrect destination.
For a continuing 1000, prepare the relevant record, provider-confirmed origin, proxy destination, recent changes, and sanitized header evidence where applicable. This gives support a request path to examine instead of an unsupported conclusion that every 1000 has the same DNS fix.
Reference: Cloudflare error 1000 documentation.
Document the final origin proxy and header path
Open the original hostname and page, then a relevant harmless workflow. Confirm the intended content and review the path implicated by the evidence. If another error appears, retain its message and time as the next stage. Keep the final origin and proxy arrangement with hosting notes.