EN-USSign in
Popular searches:
DDoS
CDN
2FA
error 5xx
slow site
traffic spike
subdomain
CName
522
502
Articles in this section
Troubleshooting Cloudflare 1XXX errors
Troubleshooting Cloudflare 5XX errors
Troubleshooting Cloudflare 1XXX errors
EN-USFollow
Updated 22 days ago
Diagnose and resolve 1XXX errors for Cloudflare proxied sites.
In this article
Overview
The errors described in this document might occur when visiting a website proxied by Cloudflare. For Cloudflare API or dashboard errors, review our Cloudflare API documentation. HTTP 409, 530, 403, 429 errors are the HTTP error codes returned in the HTTP status header for a response. 1XXX errors appear in the HTML body of the response.
Cloudflare Custom Error Pages allows customers to change the appearance of the default error pages discussed in this article.
If the resolutions within each error description below do not resolve the error, contact Cloudflare Support.
Only the site owner may contact Cloudflare for technical support. Lookup contact information for a domain via the Whois database.
Error 1000: DNS points to prohibited IP
Common causes
Cloudflare halted the request for one of the following reasons:
Resolution
Error 1001: DNS resolution error
Common causes
Resolution
A non-Cloudflare domain cannot CNAME to a Cloudflare domain unless the non-Cloudflare domain is added to a Cloudflare account.
Attempting to directly access DNS records used for Cloudflare CNAME setups also causes error 1001 (For example: www.example.com.cdn.cloudflare.net​).
Disable Always Online if using Custom Hostnames (SSL for SaaS).
Error 1002: DNS points to Prohibited IP
Common causes
Resolution
Update your Cloudflare A or CNAME record to point to your origin IP address instead of a Cloudflare IP address:
  1. Contact your hosting provider to confirm your origin IP address or CNAME record target.
  2. Log in to your Cloudflare account.
  3. Select the domain that generates error 1002.
  4. Select the DNS app.
  5. Click Value for the A record to update.
  6. Update the A record.
To ensure your origin web server doesn’t proxy its own requests through Cloudflare, configure your origin webserver to resolve your Cloudflare domain to:
Error 1002: Restricted
Common cause
The Cloudflare domain resolves to a local or disallowed IP address or an IP address not associated with the domain.
Resolution
If you own the website:
  1. Confirm your origin web server IP addresses with your hosting provider,
  2. Log in to your Cloudflare account, and
  3. Update the A records in the Cloudflare DNS app to the IP address confirmed by your hosting provider.
Error 1003 Access Denied: Direct IP Access Not Allowed
Common cause
A client or browser directly accesses a Cloudflare IP address.
Resolution
Browse to the website domain name in your URL instead of the Cloudflare IP address.
Error 1004: Host Not Configured to Serve Web Traffic
Common causes
Resolution
If the issue persists beyond 5 minutes, contact Cloudflare Support.
Errors 1006, 1007, 1008 or 1106 Access Denied: Your IP address has been banned
Common causes
A Cloudflare customer blocked traffic from your client or browser.
Error 1006 also occurs in the Cloudflare Workers app under the Preview tab when a customer uses Zone Lockdown or any other Cloudflare security feature to block the Google Cloud Platform IPs that the Preview tab relies upon.
Resolution
Request the website owner to investigate their Cloudflare security settings or allow your client IP address. Since the website owner blocked your request, Cloudflare support cannot override a customer’s security settings.
Errors 1009 Access Denied: Country or region banned
Common causes
The owner of the website (e.g. example.com) has banned the country or region your IP address in from accessing the website.
Resolution
Ensure your IP address is allowed under the IP Access Rules security feature.
Error 1010: The owner of this website has banned your access based on your browser's signature
Common cause
A website owner blocked your request based on your client's web browser.
Resolution
Notify the website owner of the blocking. If you cannot determine how to contact the website owner, lookup contact information for the domain via the Whois database. Site owners disable Browser Integrity Check via the Settings tab of the Firewall app.
Since the website owner performed the blocking, Cloudflare support cannot override a customer’s security settings.
Error 1011: Access Denied (Hotlinking Denied)
Common cause
A request is made for a resource that uses Cloudflare hotlink protection.
Resolution
Notify the website owner of the blocking. If you cannot determine how to contact the website owner, lookup contact information for the domain via the Whois database.  Hotlink Protection is managed via the Cloudflare Scrape Shield app.
Since the website owner performed the blocking, Cloudflare support cannot override a customer’s security settings.
Error 1012: Access Denied
Common cause
A website owner forbids access based on malicious activity detected from the visitor’s computer or network (ip_address). The most likely cause is a virus or malware infection on the visitor’s computer.
Resolution
Update your antivirus software and run a full system scan. Cloudflare can not override the security settings the site owner has set for the domain. To request website access, contact the site owner to allow your IP address. If you cannot determine how to contact the website owner, lookup contact information for the domain via the Whois database.
Since the website owner performed the blocking, Cloudflare support cannot override a customer’s security settings.
Error 1013: HTTP hostname and TLS SNI hostname mismatch
Common cause
The hostname sent by the client or browser via Server Name Indication (SNI) does not match the request host header.
Resolution
Error 1013 is commonly caused by the following:
Test for an SNI mismatch via an online tool such as: SSL Shopper.
Provide Cloudflare Support the following information:
HAR file captured while duplicating the error.
Error 1014: CNAME Cross-User Banned
Common cause
By default, Cloudflare prohibits a DNS CNAME record between domains in different Cloudflare accounts. CNAME records are permitted within a domain (www.example.com CNAME to api.example.com) and across zones within the same user account (www.example.com CNAME to www.example.net).
Resolution
To allow CNAME record resolution to a domain in a different Cloudflare account, the domain owner of the CNAME target must contact Cloudflare Support and specify the domains allowed to CNAME to their target domain.  A Cloudflare Pro, Business, or Enterprise plan is required on the target domain for Cloudflare Support to change default CNAME restrictions.
Error 1015: You are being rate limited
Common cause
The site owner implemented Rate Limiting that affects your visitor traffic.
Unable to purge is another 1015 error code relating to Cloudflare cache purge. Retry the cache purge and contact Cloudflare support if errors persist.
Resolution
If you expect a new Cloudflare Worker to exceed rate limits, refer to the Workers documentation for guidance.
Error 1016: Origin DNS error
Common cause
Cloudflare cannot resolve the origin web server’s IP address.
Common causes for Error 1016 are:
Resolution
To resolve error 1016:
  1. Verify your Cloudflare DNS settings include an A record that points to a valid IP address that resolves via a DNS lookup tool.
  2. For a CNAME record pointing to a different domain, ensure that the target domain resolves via a DNS lookup tool.
Error 1018: Could not find host
Common causes
Error 1018 is returned via a HTTP 409 response code.
Resolution
Contact Cloudflare Support with the following details:
  1. Your domain name
  2. A screenshot of the 1018 error including the RayID mentioned in the error message
  3. The time and timezone the 1018 error occurred
Error 1019: Compute server error
Common cause
A Cloudflare Worker script recursively references itself.
Resolution
Ensure your Cloudflare Worker does not access a URL that calls the same Workers script.
Error 1020: Access denied
Common cause
A client or browser is blocked by a Cloudflare customer’s Firewall Rules.
Resolution
If you are not the website owner, provide the website owner with a screenshot of the 1020 error message you received.
If you are the website owner:
  1. Retrieve a screenshot of the 1020 error from your customer
  2. Search the Firewall Events Log within the Overview tab of your Cloudflare Firewall app for the RayID or client IP Address from the visitor’s 1020 error message.
Convert the UTC timestamp of the 1020 error to your local timezone when searching in the Firewall Events Log.
3. Assess the cause of the block and either update the Firewall Rule or allow the visitor’s IP address in IP Access Rules.
Error 1023: Could not find host
Common causes
Error 1023 is returned via a HTTP 409 response code.
Resolution
Contact Cloudflare Support with the following details:
  1. Your domain name
  2. A screenshot of the 1023 error including the RayID mentioned in the error message
  3. The time and timezone the 1023 error occurred
Error 1025: Please check back later
Common cause
A request is not serviced because the domain has reached plan limits for Cloudflare Workers.
Resolution:
Purchase the Unlimited Workers plan via the Plans page on the Workers dashboard.
Error 1033: Argo Tunnel error
Common cause
You've requested a page on a website (tunnel.example.com) that is on the Cloudflare network. The host (tunnel.example.com) is configured as an Argo Tunnel, and Cloudflare is currently unable to resolve it.
Resolution
Error 1035: Invalid request rewrite (invalid URI path)
Common cause
The value or expression of your rewritten URI path is not valid.
Resolution
Make sure that the rewritten URI path is not empty and it starts with a / (slash) character.
For example, the following URI path rewrite expression is not valid:
concat(lower(ip.geoip.country), http.request.uri.path)
To fix the expression above, add a / prefix:
concat("/", lower(ip.geoip.country), http.request.uri.path)
Error 1036: Invalid request rewrite (maximum length exceeded)
Common cause
The value or expression of your rewritten URI path or query string is too long.
Resolution
Use a shorter value or expression for the new URI path/query string value.
Error 1037: Invalid rewrite rule (failed to evaluate expression)
Common cause
The expression of the rewrite rule could not be evaluated. There are several causes for this error, but it can mean that one expression element contained an undefined value when it was evaluated.
For example, you get a 1037 error when using the following URL rewrite dynamic expression and the X-Source header is not included in the request:
http.request.headers["x-source"][0]
Resolution
Make sure that all the elements of your rewrite expression are defined. For example, if you are referring to a header value, ensure the header is set.
Error 1040: Invalid request rewrite (header modification not allowed)
Common cause
You are trying to modify an HTTP header that HTTP Request Header Modification Rules cannot change.
Resolution
Make sure you are not trying to modify one of the reserved HTTP request headers.
Error 1041: Invalid request rewrite (invalid header value)
Common causes
The added/modified header value is empty, too long, or it contains characters that are not allowed.
Resolution
Error 1101: Rendering error
Common cause
A Cloudflare Worker throws a runtime JavaScript exception.
Resolution:
Provide appropriate issues details to Cloudflare Support.
Error 1102: Rendering error
Common cause
A Cloudflare Worker exceeds a CPU time limit. CPU time is the time spent executing code (for example, loops, parsing JSON, etc). Time spent on network requests (fetching, responding) does not count towards CPU time.
Resolution
Contact the developer of your Workers code to optimize code for a reduction in CPU usage in the active Workers scripts.
Error 1200: Cache connection limit
Common cause
There are too many requests queued on Cloudflare's edge that are awaiting process by your origin web server.  This limit protects Cloudflare's systems.
Resolution
Tune your origin webserver to accept incoming connections faster.  Adjust your caching settings to improve cache-hit rates so that fewer requests reach your origin web server.  Reach out to your hosting provider or web administrator for assistance.
Related resources
Facebook Twitter LinkedIn
Was this article helpful?
111381 out of 158573 found this helpful
Return to top
Not finding what you need?
Searching can help answer 95% of support questions. This is the quickest way to get answers.
Ask the Community Submit a request
Popular searches:
DDoS
CDN
2FA
error 5xx
slow site
traffic spike
subdomain
cname
522
Related articles
Troubleshooting Cloudflare 5XX errors
Contacting Cloudflare Support
Configuring Custom Pages (Error and Challenge)
Gathering information for troubleshooting sites
Glossary of SSL terms
Sales
Getting Started
Community
Developers
Support
Company
EN-US
© 2021 Cloudflare, Inc.
|
Privacy Policy
|
Terms of Use
|
Trust & Safety
|
Trademark
Minor Service Outage Ask the Community
Cloudflare Help CenterTroubleshootingCloudflare Errors