Cloudflare Error 1004: Host Not Configured to Serve Web Traffic

Error 1004, "Host Not Configured to Serve Web Traffic," is one of the less common Cloudflare errors, and its documentation is short. Cloudflare says it indicates that the host is not configured to serve web traffic, and names two common causes. This page expands on how to tell them apart and what to do.

The visitor sees a Cloudflare error page with code 1004 and a Ray ID. The people who can act are the domain owner and, in one scenario, Cloudflare Support.

The two documented causes

1. Cloudflare staff disabled proxying for the domain because of abuse or a terms-of-service violation.
2. DNS changes have not propagated yet, or the site owner's A records point to Cloudflare IP addresses.

Cloudflare's guidance: if the problem lasts more than about five minutes, contact Cloudflare Support. Because the page lists the causes without a way to distinguish them, use the checks below.

If you are a visitor

You cannot resolve it. Wait a few minutes and reload, since a recent DNS change is the most common reason. If it persists, tell the site owner you saw "Error 1004" with the Ray ID. If you cannot find a contact, domain registration details are available through a WHOIS search; the WHOIS Lookup shows registrar and often an abuse or contact email.

If you are the site owner

Step 1: did you just change DNS or onboard the site?

If you recently added the domain to Cloudflare, changed nameservers, or edited records, wait and retest. Cloudflare's own suggestion is to give it a few minutes. Compare answers from several resolvers:

dig +short NS example.com
dig +short A example.com @1.1.1.1
dig +short A example.com @8.8.8.8

The Nameserver Lookup and DNS Checker show whether the world agrees. Disagreement between resolvers points to propagation; see how long DNS propagation takes.

Step 2: look for Cloudflare IPs in your A records

This is the cause you can fix. In the Cloudflare DNS page, view the stored A and AAAA values for the failing hostname. If a value is a Cloudflare address, Cloudflare is being told to use itself as the server. Replace it with your real origin IP, available from your host. Use the IP Lookup to confirm who owns an address: Cloudflare's network is AS13335.

Related errors cover the same trap with different wording: 1000 and 1002.

Step 3: check the domain and nameserver state

Confirm the zone is active in your account, that nameservers at the registrar match the two Cloudflare assigned, and that the domain has not expired. A pending or moved zone can leave a hostname half-configured.

whois example.com | grep -i -E "name server|expir|status"

Step 4: consider that Cloudflare disabled proxying

If DNS is correct and the error remains beyond a few minutes, the second cause may apply. Cloudflare documents that staff can turn off proxying for abuse or terms violations. Check the account's email for notices, look in the dashboard for warnings, and then open a support ticket that includes:

• The domain and affected hostnames.
• The Ray ID and time of a failing request.
• What you changed and when.

Support plans differ. Cloudflare's docs note email support is for Pro, Business and Enterprise plans, with chat for Business and Enterprise; Free plan users rely on the community and documentation. Check current plan details.

Step 5: if the site is hacked

Abuse flags often follow a compromise: phishing pages, malware, or spam relays. Clean the site first, then ask Cloudflare to review. The website hosting checker and your server logs help you see what is being served. If you run WordPress, site hacked recovery lists the steps.

Verify the fix

Load the site, then run the Cloudflare Error Checker and the CDN Detector to see whether Cloudflare is serving it normally. If you want early warning next time, add a monitor with the Uptime Monitor.

Next steps

• Detect the code with the Cloudflare Error Checker.
• Review records in the DNS Checker.
• Read Cloudflare DNS and SSL modes.
• Compare with error 1016.

FAQ

How long should I wait before contacting support?

Cloudflare suggests that if the issue lasts more than about five minutes, you should contact support. For a brand-new setup, five minutes is the guideline, not a guarantee.

Is error 1004 my hosting provider's fault?

Not normally. It comes from Cloudflare's view of your DNS and proxy configuration, not from your web server.

Can Cloudflare really switch off my proxy?

The documentation lists abuse or terms violations as a cause. If that is not your situation, ask support to confirm.

Why would my own A record cause it?

If it holds a Cloudflare IP, Cloudflare has no real server to forward traffic to. Put your origin IP in the record.

This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.