Cloudflare ошибка подключения

Troubleshooting Cloudflare 5XX errors – Cloudflare Help Center

Error analytics

Error Analytics per domain are available within Zone Analytics. Error Analytics allows insight into overall errors by HTTP error code and provides the URLs, source IP addresses, and Cloudflare data centers needed to diagnose and resolve the issue.  Error Analytics are based on a 1% traffic sample.

To view Error Analytics:

• Log in to the Cloudflare dashboard.
• Click the appropriate Cloudflare account for your site, then pick the domain.
• Next, click the Analytics & Logs app icon.
• Click Add filter, select Edge status code or Origin status code and choose any 5xx error code that you want to diagnose.

Error 500: internal server error

Error 500 generally indicates an issue with your origin web server.  Error establishing database connection is a common HTTP 500 error message generated by your origin web server.  Contact your hosting provider to resolve.

Resolution

Provide details to your hosting provider to assist troubleshooting the issue.

However, if the 500 error contains “cloudflare” or “cloudflare-nginx” in the HTML response body, provide Cloudflare support with the following information:

1. Your domain name
2. The time and timezone of the 500 error occurrence
3. The output of www.example.com/cdn-cgi/trace from the browser where the 500 error was observed (replace www.example.com with your actual domain and host name)

{{

}}
If you observe blank or white pages when visiting your website, confirm
whether the issue occurs when temporarily pausing
Cloudflare
and contact your hosting provider for assistance.
{{}}

Error 502 bad gateway or error 504 gateway timeout

An HTTP 502 or 504 error occurs when Cloudflare is unable to establish contact with your origin web server.

There are two possible causes:

• (Most common cause) 502/504 from your origin web server
• 502/504 from Cloudflare

502/504 from your origin web server

Cloudflare returns an Cloudflare-branded HTTP 502 or 504 error when your origin web server responds with a standard HTTP 502 bad gateway or 504 gateway timeout error:

Resolution

Contact your hosting provider to troubleshoot these common causes at your origin web server:

• Ensure the origin server responds to requests for the hostname and domain within the visitor’s URL that generated the 502 or 504 error.
• Investigate excessive server loads, crashes, or network failures.
• Identify applications or services that timed out or were blocked.

502/504 from Cloudflare

A 502 or 504 error originating from Cloudflare appears as follows:

If the error does not mention “cloudflare,” contact your hosting provider for assistance on 502/504 errors from your origin.

Resolution

To avoid delays processing your inquiry, provide these required details to Cloudflare Support:

1. Time and timezone the issue occurred.
2. URL that resulted in the HTTP 502 or 504 response (for example: https://www.example.com/images/icons/image1.png)
3. Output from browsing to _www.example.com/cdn-cgi/trace_ (replace _www.example.com_ with the domain and host name that caused the HTTP 502 or 504 error)

Error 503: service temporarily unavailable

HTTP error 503 occurs when your origin web server is overloaded. There are two possible causes discernible by error message:

• Error doesn’t contain “cloudflare” or “cloudflare-nginx” in the HTML response body.

Resolution: Contact your hosting provider to verify if they rate limit requests to your origin web server.

• Error contains “cloudflare” or “cloudflare-nginx” in the HTML response body.

Resolution: A connectivity issue occured in a Cloudflare data center. Provide Cloudflare support with the following information:

1. Your domain name
2. The time and timezone of the 503 error occurrence
3. The output of _www.example.com/cdn-cgi/trace_ from the browser where the 503 error was observed (replace www.example.com with your actual domain and host name)

Error 520: web server returns an unknown error

Error 520 occurs when the origin server returns an empty, unknown, or unexpected response to Cloudflare.

Resolution

{{

}}
A quick workaround while further investigating 520 errors is to either
make the record
DNS-only
in the Cloudflare DNS app or temporarily pause
Cloudflare.
{{}}

Contact your hosting provider or site administrator and request a review of your origin web server error logs for crashes and to check for these common causes:

• Origin web server application crashes
• Cloudflare IPs not allowed at your origin
• Headers exceeding 16 KB (typically due to too many cookies)
• An empty response from the origin web server that lacks an HTTP status code or response body
• Missing response headers or origin web server not returning proper HTTP error responses.
  • upstream prematurely closed connection while reading response header from upstream is a common error we may notice in our logs. This indicates the origin web server was having issues which caused Cloudflare to generate 520 errors.

{{

}}
520 errors are prevalent with certain PHP applications that crash the
origin web server.
{{}}

If 520 errors continue after contacting your hosting provider or site administrator, provide the following information to Cloudflare Support:

• Full URL(s) of the resource requested when the error occurred
• Cloudflare cf-ray from the 520 error message
• Output from _http://www.example.com/cdn-cgi/trace_ (replace _www.example.com_ with your hostname and domain where the 520 error occurred)
• Two HAR files:
  • one with Cloudflare enabled on your website, and
  • the other with Cloudflare temporarily disabled.

Error 521: web server is down

Error 521 occurs when the origin web server refuses connections from Cloudflare. Security solutions at your origin may block legitimate connections from certain Cloudflare IP addresses.

The two most common causes of 521 errors are:

• Offlined origin web server application
• Blocked Cloudflare requests

Resolution

Contact your site administrator or hosting provider to eliminate these common causes:

• Ensure your origin web server is responsive
• Review origin web server error logs to identify web server application crashes or outages.
• Confirm Cloudflare IP addresses are not blocked or rate limited
• Allow all Cloudflare IP ranges in your origin web server’s firewall or other security software
• Confirm that — if you have your SSL/TLS mode set to Full or Full (Strict) — you have installed a Cloudflare Origin Certificate
• Find additional troubleshooting information on the Cloudflare Community.

Error 522: connection timed out

Error 522 occurs when Cloudflare times out contacting the origin web server. Two different timeouts cause HTTP error 522 depending on when they occur between Cloudflare and the origin web server:

1. Before a connection is established, the origin web server does not return a SYN+ACK to Cloudflare within 15 seconds of Cloudflare sending a SYN.
2. After a connection is established, the origin web server doesn’t acknowledge (ACK) Cloudflare’s resource request within 90 seconds.

Resolution

Contact your hosting provider to check the following common causes at your origin web server:

• (Most common cause) Cloudflare IP addresses are rate limited or blocked in .htaccess, iptables, or firewalls. Confirm your hosting provider allows Cloudflare IP addresses.
• An overloaded or offline origin web server drops incoming requests.
• Keepalives are disabled at the origin web server.
• The origin IP address in your Cloudflare DNS app does not match the IP address currently provisioned to your origin web server by your hosting provider.
• Packets were dropped at your origin web server.

If you are using Cloudflare Pages, verify that you have a custom domain set up and that your CNAME record is pointed to your custom Pages domain. Instructions on how to set up a custom Pages domain can be found here.

If none of the above leads to a resolution, request the following information from your hosting provider or site administrator before contacting Cloudflare support:

• An MTR or traceroute from your origin web server to a Cloudflare IP address that most commonly connected to your origin web server before the issue occurred. Identify a connecting Cloudflare IP recorded in the origin web server logs.
• Details from the hosting provider’s investigation such as pertinent logs or conversations with the hosting provider.

Error 523: origin is unreachable

Error 523 occurs when Cloudflare cannot contact your origin web server. This typically occurs when a network device between Cloudflare and the origin web server doesn’t have a route to the origin’s IP address.

Resolution Contact your hosting provider to exclude the following common causes at your origin web server:

• Confirm the correct origin IP address is listed for A or AAAA records within your Cloudflare DNS app.
• Troubleshoot Internet routing issues between your origin and Cloudflare, or with the origin itself.

If none of the above leads to a resolution, request the following information from your hosting provider or site administrator:

• An MTR or traceroute from your origin web server to a Cloudflare IP address that most commonly connected to your origin web server before the issue occurred. Identify a connecting Cloudflare IP from the logs of the origin web server.
• If you use Railgun (deprecated) via a Cloudflare Hosting Partner, contact your hosting provider to troubleshoot the 523 errors.
• If you manage your Railgun (deprecated) installation, provide the following:
  • A traceroute to your origin web server from your Railgun server.
  • The most recent syslog file from your Railgun server.

Error 524: a timeout occurred

Error 524 indicates that Cloudflare successfully connected to the origin web server, but the origin did not provide an HTTP response before the default 100 second connection timed out. This can happen if the origin server is simply taking too long because it has too much work to do — e.g. a large data query, or because the server is struggling for resources and cannot return any data in time.

{{

}}
A 522 occurs if the origin web server
acknowledges (ACK) the resource request after the connection has been
established, but does not send a timely response.
{{}}

Resolution

Here are the options we’d suggest to work around this issue:

• Implement status polling of large HTTP processes to avoid hitting this error.
• Contact your hosting provider to exclude the following common causes at your origin web server:
  • A long-running process on the origin web server.
  • An overloaded origin web server.

{{

}}
Logging request response time at your origin web server helps identify
the cause of resource slowness. Contact your hosting provider or site
administrator for assistance in adjusting log formats or search for
related logging documentation for your brand of web server such as
Apache
or
Nginx.
{{}}

• Enterprise customers can increase the 524 timeout up to 6000 seconds using the proxy_read_timeout API endpoint.
• If you regularly run HTTP requests that take over 100 seconds to complete (for example large data exports), move those processes behind a subdomain not proxied (grey clouded) in the Cloudflare DNS app.
• If error 524 occurs for a domain using Cloudflare Railgun (deprecated), ensure the lan.timeout is set higher than the default of 30 seconds and restart the railgun service.

Error 525: SSL handshake failed

525 errors indicate that the SSL handshake between Cloudflare and the origin web server failed. Error 525 occurs when these two conditions are true:

1. The SSL handshake fails between Cloudflare and the origin web server, and
2. Full or Full (Strict) SSL is set in the Overview tab of your Cloudflare SSL/TLS app.

{{

}}
If your hosting provider frequently changes your origin web server’s IP
address, refer to Cloudflare’s documentation on dynamic DNS
updates.
{{}}

Resolution

Contact your hosting provider to exclude the following common causes at your origin web server:

• No valid SSL certificate installed
• Port 443 (or other custom secure port) is not open
• No SNI support
• The cipher suites accepted by Cloudflare does not match the cipher suites supported by the origin web server

{{

}}
If 525 errors occur intermittently, review the origin web server error
logs to determine the cause. Configure Apache to log mod_ssl
errors.
Also, nginx includes SSL errors in its standard error log, but may
possibly require an increased log
level.
{{}}

Additional checks

• Check if you have a certificate installed on your origin server. You can check this article for more details on how to run some tests. In case you don’t have any certificate, you can create and install our free Cloudflare origin CA certificate. Using Origin CA certificates allows you to encrypt traffic between Cloudflare and your origin web server.
• Review the cipher suites your server is using to ensure they match what is supported by Cloudflare.
• Check your server’s error logs from the timestamps you see 525s to ensure there are errors that could be causing the connection to be reset during the SSL handshake.

Error 526: invalid SSL certificate

Error 526 occurs when these two conditions are true:

1. Cloudflare cannot validate the SSL certificate at your origin web server, and
2. Full SSL (Strict) SSL is set in the Overview tab of your Cloudflare SSL/TLS app.

Resolution

{{

}}
For a potential quick fix, set SSL to Full instead of Full
(strict) in the Overview tab of your Cloudflare SSL/TLS app for
the domain.
{{}}

Request your server administrator or hosting provider to review the origin web server’s SSL certificates and verify that:

• Certificate is not expired
• Certificate is not revoked
• Certificate is signed by a Certificate Authority (not self-signed)
• The requested or target domain name and hostname are in the certificate’s Common Name or Subject Alternative Name
• Your origin web server accepts connections over port SSL port 443
• Temporarily pause Cloudflare and visit https://www.sslshopper.com/ssl-checker.html#hostname=www.example.com (replace www.example.com with your hostname and domain) to verify no issues exists with the origin SSL certificate:

If the origin server uses a self-signed certificate, configure the domain to use Full SSL instead of Full SSL (Strict). Refer to recommended SSL settings for your origin.

527 Error: Railgun Listener to origin error

{{}}

A 527 error indicates an interrupted connection between Cloudflare and your origin’s Railgun server (rg-listener). Common causes include:

• Firewall interference
• Network incidents or packet loss between the Railgun server and Cloudflare

{{

}}
For additional details to aid troubleshooting, increase Railgun
logging.
{{}}

Common causes of 527 errors include:

• Connection timeouts
• LAN timeout exceeded
• Connection refusals
• TLS/SSL related errors

If contacting Cloudflare support, provide the following information from the Railgun Listener:

• The full content of the railgun.conf file
• The full content of the railgun-nat.conf file
• Railgun log files that detail the observed errors

Connection timeouts

The following Railgun log errors indicate a connection failure between the Railgun Listener and your origin web server:

connection failed 0.0.0.0:443/example.com: dial tcp 0.0.0.0:443: i/o timeout
no response from origin (timeout) 0.0.0.0:80/example.com

Resolution

Contact your hosting provider for assistance to test for connectivity issues between your origin web server and your Railgun Listener. For example, a netcat command tests connectivity when run from the Railgun Listener to the origin web server’s SERVERIP and PORT (80 for HTTP or 443 for HTTPS):

LAN timeout exceeded

The following Railgun Listener log error is generated if the origin web server does not send an HTTP response to the Railgun Listener within the 30 second default timeout:

connection failed 0.0.0.0:443/example.com: dial tcp 0.0.0.0:443: i/o timeout

The time is adjusted by the lan.timeout parameter of the railgun.conf file.

Resolution

Either increase the lan.timeout limit in railgun.conf, or review the web server configuration. Contact your hosting provider to confirm if the origin web server is overloaded.

Connection refusals

The following errors appear in the Railgun logs when requests from the Railgun Listener are refused:

Error getting page: dial tcp 0.0.0.0:80:connection refused

Resolution

Allow the IP of your Railgun Listener at your origin web server’s firewall.

TLS/SSL related errors

The following errors appear in the Railgun logs if TLS connections fail:

connection failed 0.0.0.0:443/example.com: remote error: handshake failure
connection failed 0.0.0.0:443/example.com: dial tcp 0.0.0.0:443:connection refused
connection failed 127.0.0.1:443/www.example.com: x509: certificate is valid for
example.com, not www.example.com

Resolution

If TLS/SSL errors occur, check the following on the origin web server and ensure that:

• Port 443 is open
• An SSL certificate is presented by the origin web server
• the SAN or Common Name of the origin web server’s SSL certificate contains the requested or target hostname
• SSL is set to Full or Full (Strict) in the Overview tab of the Cloudflare SSL/TLS app

{{

}}
If your origin web server SSL certificate is self-signed, set
validate.cert=0 in
railgun.conf.
{{}}

Error 530

HTTP error 530 is returned with an accompanying 1XXX error displayed. Search for the specific 1XXX error within the Cloudflare Help Center for troubleshooting information.

Related resources

• Gathering information to troubleshoot site issues
• Contacting Cloudflare Support
• Customizing Cloudflare error pages
• MTR/Traceroute Diagnosis and Usage
• Cloudflare Community Tips

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.

If the resolutions within each error description below do not resolve the error, 
contact Cloudflare Support.

Error 1000: DNS points to prohibited IP

Common causes

Cloudflare halted the request for one of the following reasons:

• An A record within your Cloudflare DNS app points to a Cloudflare IP address, or a Load Balancer Origin points to a proxied record.
• Your Cloudflare DNS A or CNAME record references another reverse proxy (such as an nginx web server that uses the proxy_pass function) that then proxies the request to Cloudflare a second time.
• The request X-Forwarded-For header is longer than 100 characters.
• The request includes two X-Forwarded-For headers.
• A Server Name Indication (SNI) issue or mismatch at the origin.

Resolution

• If an A record within your Cloudflare DNS app points to a Cloudflare IP address, update the IP address to your origin web server IP address.
• There is a reverse-proxy at your origin that sends the request back through the Cloudflare proxy. Instead of using a reverse-proxy, contact your hosting provider or site administrator to configure an HTTP redirect at your origin.

Error 1001: DNS resolution error

Common causes

• A web request was sent to a Cloudflare IP address for a non-existent Cloudflare domain.
• An external domain that is not on using Cloudflare has a CNAME record to a domain active on Cloudflare
• The target of the DNS CNAME record does not resolve.
• A CNAME record in your Cloudflare DNS app requires resolution via a DNS provider that is currently offline.
• Always Online is enabled for a Custom Hostname (Cloudflare for SaaS) domain.

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 Hostname (Cloudflare for SaaS) domain.

Error 1002: DNS points to Prohibited IP

Common causes

• A DNS record in your Cloudflare DNS app points to one of Cloudflare’s IP addresses.
• An incorrect target is specified for a CNAME record in your Cloudflare DNS app.
• Your domain is not on Cloudflare but has a CNAME that refers to a Cloudflare domain.

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:

• The internal NAT’d IP address, or
• The public IP address of the origin web server.

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

• Cloudflare staff disabled proxying for the domain due to abuse or terms of service violations.
• DNS changes have not yet propagated or the site owner’s DNS A records point to Cloudflare IP addresses.

Resolution

If the issue persists beyond 5 minutes, 
contact Cloudflare Support.

Errors 1005 Access Denied: Autonomous System Number (ASN) banned

Common causes

The owner of the website (e.g. example.com) has banned the autonomous system number (ASN) from accessing the website.

Resolution

If you are not the website owner, provide the website owner with a screenshot of the 1005 error message you received.

If you are the website owner:

1. Retrieve a screenshot of the 1005 error from your customer
2. Search the Security Events log (available at Security > Events) for the RayID, or client IP Address from the visitor’s 1005 error message.

3. Assess the cause of the block and ensure the ASN is allowed under the 
IP Access Rules security feature.

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.

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 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 Security app.

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.

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.

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:

• your local browser setting the incorrect SNI host header, or
• a network proxying SSL traffic caused a mismatch between SNI and the Host header of the request.

Test for an SNI mismatch via an online tool such as: 
SSL Shopper.

Provide Cloudflare Support the following information:

1. A 
   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) or using our Cloudflare for SaaS solution.

Resolution

To allow CNAME record resolution to a domain in a different Cloudflare account, the domain owner of the CNAME target must use Cloudflare for SaaS.

Error 1015: You are being rate limited

Common cause

The site owner implemented 
Rate Limiting that affects your visitor traffic.

Resolution

• If you are a site visitor, contact the site owner to request exclusion of your IP from rate limiting.
• If you are the site owner, review Cloudflare Rate Limiting thresholds and adjust your Rate Limiting configuration.
• If your Rate Limiting blocks requests in a short time period (i.e. 1 second) try increasing the time period to 10 seconds.

Error 1016: Origin DNS error

Common cause

Cloudflare cannot resolve the origin web server’s IP address.

Common causes for Error 1016 are:

• A missing DNS A record that mentions origin IP address.
• A CNAME record in the Cloudflare DNS points to an unresolvable external domain.
• The origin host names (CNAMEs) in your Cloudflare Load Balancer default, region, and fallback pools are unresolvable. Use a fallback pool configured with an origin IP as a backup in case all other pools are unavailable.
• When creating a Spectrum app with a CNAME origin, you need first to create a CNAME on the Cloudflare DNS side that points to the origin. Please see Spectrum CNAME origins for more details

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

• The Cloudflare domain was recently activated and there is a delay propagating the domain’s settings to the Cloudflare edge network.
• The Cloudflare domain was created via a Cloudflare partner (e.g., a hosting provider) and the provider’s DNS failed.

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 Security Events log (available at Security > Events) for the RayID or client IP Address from the visitor’s 1020 error message.

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

• If the owner just signed up for Cloudflare it can take a few minutes for the website’s information to be distributed to our global network. Something is wrong with the site’s configuration.
• Usually, this happens when accounts have been signed up with a partner organization (e.g., hosting provider) and the provider’s DNS fails.

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

• If you are a visitor of this website: Please try again in a few minutes.
• If you are the owner of this website: Ensure that cloudflared is running and can reach the network. You may wish to enable load balancing for your tunnel.

Error 1034: Edge IP Restricted

Common cause

Customers who previously pointed their domains to 1.1.1.1 will now encounter 1034 error. This is due to a new edge validation check in Cloudflare’s systems to prevent misconfiguration and/or potential abuse.

Resolution

Ensure DNS records are pointed to IP addresses you control, and in the case a placeholder IP address is needed for “originless” setups, use the IPv6 reserved address 100:: or the IPv4 reserved address 192.0.2.0.

Error 1035: Invalid request rewrite (invalid URI path)

Common cause

The value or expression of your rewritten URI path is not valid.

This error also occurs when the destination of the URL rewrite is a path under /cdn-cgi/.

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.

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.

Common causes

The added/modified header value is too long or it contains characters that are not allowed.

Resolution

• Use a shorter value or expression to define the header value.
• Remove the characters that are not allowed. See Format of HTTP request header names and values in Developer Docs for more information on the allowed characters.

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 1104: A variation of this email address is already taken in our system. Only one variation is allowed.

Common cause

This error can occur if an email has been added with some variation of the email you’re trying to add. For example, [email protected] and [email protected] will be treated the same in our system.

Resolution

Log in as the old user and change email to a “throwaway” address, which will free up the new email.

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.

• Contacting Cloudflare Support
• Customizing Cloudflare error pages