How to Fix Cloudflare Error 1004 (Host Not Configured to Serve Web Traffic)
What Error 1004 means
Error 1004 is one of Cloudflare's 1xxx family of configuration errors, and its message — "Host Not Configured to Serve Web Traffic" — is unusually honest. Your browser did everything right: it resolved the domain, connected to Cloudflare's edge, and delivered the request. Cloudflare then looked at where that request was supposed to go and found nothing — no active zone, no valid origin mapping, or a configuration that was removed. So it answered with a 1004 page instead of the site.
That makes a 1004 different from the errors people confuse it with. Error 1001 means the DNS record itself is missing or unusable, and Error 1016 means the record points at something that cannot be resolved. A 1004 is one step further along: the request landed inside Cloudflare's network, but the host it asked for simply is not configured there. For visitors, that distinction matters less than the practical upshot — only the site owner can truly fix a persistent 1004 — but it tells the owner exactly where to look: the zone and the DNS records, not the server.
Common causes
- A record points to a Cloudflare IP instead of the origin IP: the classic trigger. If the DNS A record's content is a Cloudflare address, traffic loops back into Cloudflare, which has no host configured for it.
- The zone was deleted, moved, or is not active: the domain was removed from Cloudflare, transferred to a different Cloudflare account, or the nameserver change never completed — so Cloudflare has no zone to route traffic to.
- DNS changes have not finished propagating: right after adding a domain or editing records, some visitors hit Cloudflare before the new configuration is live everywhere, producing a temporary 1004.
- Fresh activation through a hosting partner: Cloudflare notes that a 1004 often appears on the very first request after partner activation and then disappears within minutes as the setup completes.
- Proxying disabled by Cloudflare staff: if proxying was turned off for the domain because of abuse or terms-of-service violations, requests to the configured host stop being served until support restores it.
How to fix Error 1004 — step by step
Steps 1 through 3 are for visitors. Steps 4 through 6 are for site owners.
- Visitor: wait a few minutes and retry — this error often clears on its own. Error 1004 is frequently temporary. Cloudflare's own documentation notes it can appear when DNS changes have not yet propagated, and after activating Cloudflare through a hosting partner the error often shows on the very first request and then disappears within a few minutes. Close the tab, wait at least five to ten minutes, and try again before assuming anything is broken. Do not hammer refresh: a short wait is the fastest fix for propagation-related 1004s.
- Visitor: rule out your own network and cached DNS. Open a private or incognito window and reload the page — if it loads there, your browser cache or an old DNS answer was the problem. On Windows, open Command Prompt and run ipconfig /flushdns; on a Mac, open Terminal and run sudo dscacheutil -flushcache followed by sudo killall -HUP mDNSResponder. Then try the site on a different network, such as your phone's mobile data, to confirm the error is not tied to your connection or your ISP's cached DNS.
- Visitor: check whether the error is site-wide — only the owner can fix a real 1004. If the 1004 persists after waiting and trying other networks, the cause is almost certainly on the site owner's side: Cloudflare has no host configured for that domain, and nothing you change on your device can create one. Confirm the site is down for everyone, then report it to the site owner through their contact page, social channels, or support email. Tell them you are seeing 'Error 1004: Host Not Configured to Serve Web Traffic' and ask them to check their Cloudflare DNS setup.
- Site owner: confirm the domain is still active in your Cloudflare account. Log in to Cloudflare and check that the domain is listed under Websites with an active plan. If the zone was deleted, moved to a different Cloudflare account, or the domain recently expired and was re-registered, Cloudflare has nothing to route traffic to — which is exactly what a 1004 says. Re-add the domain to Cloudflare if it is missing, complete the nameserver change at your registrar, and wait for the zone to show as active before expecting the error to clear.
- Site owner: fix the DNS A record so it points at your real origin server IP. Go to DNS, then Records for the domain and inspect the A record for the failing hostname. The most common cause of a 1004 is an A record whose content is a Cloudflare IP address instead of your actual server's IP — a record pointing at Cloudflare just loops traffic back into Cloudflare, which has no host configured for it. Replace the content with the IPv4 address your hosting provider gave you for the origin server, keep the proxy status as you intend it, and save. Verify with a lookup tool that the hostname now resolves to your origin IP.
- Site owner: handle propagation, partner activation, or disabled proxying. If you just changed DNS, wait — full propagation can take several hours, and Cloudflare says to contact support only if the 1004 persists beyond five minutes after a fresh activation. If you activated Cloudflare through a hosting partner, the first-request 1004 normally clears within about ten minutes; if it lasts longer, contact your hosting provider. And if Cloudflare staff disabled proxying for the domain because of abuse or terms-of-service issues, only Cloudflare Support can restore it — open a support ticket and resolve whatever triggered the suspension.
Did this fix it? Quick checklist
- The page loads after waiting a few minutes with no new 1004
- Owner-side: the A record points to the real origin IP, not a Cloudflare IP
- Owner-side: the domain is active in the Cloudflare dashboard (not deleted or moved)
- Owner-side: DNS changes have fully propagated — verified with a DNS lookup
If you are a visitor and the 1004 is still there after a day, it is not propagation — the owner's configuration is genuinely broken, and the best thing you can do is tell them the exact error text so they check their zone and DNS records. If you are an owner and the 1004 survives a correct A record and a full propagation window, stop guessing and open a Cloudflare support ticket: at that point the cause is usually zone-level (a deleted zone, an account mismatch, or disabled proxying), and only their side can see it.
Frequently asked questions
What does Cloudflare Error 1004 mean?
Error 1004, 'Host Not Configured to Serve Web Traffic,' means your request reached Cloudflare, but Cloudflare has no configured host for that domain — the DNS record points traffic into Cloudflare, yet there is no active zone, no valid origin mapping, or the proxying configuration was removed. It is an owner-side configuration problem, not a bug on your device or a downed server.
Why did Error 1004 appear right after I activated Cloudflare?
After activating Cloudflare through a hosting partner, a 1004 commonly appears on the very first request while the configuration finishes, and it usually goes away within a few minutes. If it lasts more than about ten minutes, contact your hosting provider — the activation did not complete. For direct Cloudflare signups, a 1004 after adding a domain usually means the zone is not active yet or the nameserver change has not propagated.
Can I fix Error 1004 as a visitor?
Only in the temporary cases: waiting five to ten minutes, flushing your DNS cache, and trying another network can clear a 1004 caused by propagation or a fresh activation. If the error persists, you cannot fix it — the site owner must correct their Cloudflare zone or DNS records. Report it to the site owner and include the exact 'Error 1004: Host Not Configured to Serve Web Traffic' wording.
How long should I wait before assuming Error 1004 is a real configuration problem?
For a fresh activation or recent DNS change, give it at least five to ten minutes, and Cloudflare's documentation says to contact support if it persists beyond five minutes. For DNS propagation after record edits, allow up to a few hours. If the error is still there the next day with no recent changes, it is a genuine misconfiguration — typically an A record pointing at a Cloudflare IP or a deleted zone — and needs the owner to act.
What is the difference between Error 1004, 1001, and 1016?
All three are DNS-layer Cloudflare errors, but they fail at different points. Error 1004 means Cloudflare received the request but has no host configured to serve that domain. Error 1001 means the DNS record exists but is missing or points nowhere Cloudflare can use. Error 1016 means the record points to a hostname or CNAME chain that cannot be resolved. In short: 1004 is 'no host configured,' 1001 is 'record missing,' and 1016 is 'record points somewhere unresolvable.'