Diagnose and resolve 1XXX errors for Cloudflare proxied sites.
- Overview
- Error 1000: DNS points to prohibited IP
- Error 1001: DNS resolution error
- Error 1002: DNS points to Prohibited IP
- Error 1002: Restricted
- Error 1003 Access Denied: Direct IP Access Not Allowed
- Error 1004: Host Not Configured to Serve Web Traffic
- Errors 1006, 1007 or 1008 Access Denied: Your IP address has been banned
- Error 1010: The owner of this website has banned your access based on your browser's signature
- Error 1011: Access Denied (Hotlinking Denied)
- Error 1012: Access Denied
- Error 1013: HTTP hostname and TLS SNI hostname mismatch
- Error 1014: CNAME Cross-User Banned
- Error 1015: You are being rate limited
- Error 1016: Origin DNS error
- Error 1018: Could not find host
- Error 1019: Compute server error
- Error 1020: Access denied
- Error 1023: Could not find host
- Error 1025: Please check back later
- Error 1033: Argo Tunnel error
- Error 1101: Rendering error
- Error 1102: Rendering error
- Error 1200: Cache connection limit
- Related resources
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.
- 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.
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 (SSL 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.
Intentar acceder directamente a los registros DNS utilizados para las configuraciones CNAME de Cloudflare también provoca un error 1001 (por ejemplo: www.ejemplo.com.cdn.cloudflare.net).
Disable Always Online if using Custom Hostnames (SSL for SaaS).
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
Actualizar tu registro A o CNAME de Cloudflare para que apunte a tu dirección IP de origen en lugar de a una dirección IP de Cloudflare:
- Contact your hosting provider to confirm your origin IP address or CNAME record target.
- Log in to your Cloudflare account.
- Select the domain that generates error 1002.
- Selecciona la aplicación de DNS.
- Haz clic en Valor para que se actualice el registro A.
- Actualiza el registro A.
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:
- Confirm your origin web server IP addresses with your hosting provider,
- Log in to your Cloudflare account, and
- 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.
- Los cambios del DNS aún no se han propagado o los registros A del propietario del sitio apuntan a direcciones IP de Cloudflare.
Resolution
If the issue persists beyond 5 minutes, contact Cloudflare Support.
Errors 1006, 1007 or 1008 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.
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
Notifica al propietario del sitio web del bloqueo. Si no encuentras información para contactar con el propietario del sitio web, busca los datos de contacto del dominio en la base de datos Whois. Los propietarios de sitios desactivan la comprobación de integridad del explorador a través de la pestaña Configuración de la aplicación de firewall.
Error 1011: Access Denied (Hotlinking Denied)
Common cause
A request is made for a resource that uses Cloudflare hotlink protection.
Resolution
Notifica al propietario del sitio web del bloqueo. Si no encuentras información para contactar con el propietario del sitio web, busca los datos de contacto del dominio en la base de datos Whois. La protección Hotlink se administra a través de la aplicación Scrape Shield de Cloudflare.
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:
- A HAR file captured while duplicating the error.
Error 1014: CNAME Cross-User Banned
Common cause
Por defecto, Cloudflare prohíbe un registro CNAME de DNS entre dominios en diferentes cuentas de Cloudflare. Los registros CNAME se permiten dentro de un dominio (www.ejemplo.com con CNAME a api.ejemplo.com) y entre zonas en la misma cuenta de usuario (www.ejemplo.com con CNAME a www.ejemplo.net).
Resolution
Para permitir la resolución de registro CNAME a un dominio en otra cuenta de Cloudflare, el propietario del dominio al que dirige el CNAME debe contactar con el servicio de asistencia de Cloudflare y especificar los dominios que pueden dirigir el CNAME a su dominio. Se requiere un plan Pro, Business o Enterprise de Cloudflare en el dominio de destino para que el servicio de asistencia de Cloudflare pueda cambiar las restricciones CNAME predeterminadas.
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:
- Falta el registro A de DNS que menciona la dirección IP de origen.
- Un registro CNAME en el DNS de Cloudflare apunta a un dominio externo irrecuperable.
- 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:
- Comprueba que tu configuración de DNS de Cloudflare incluye un registro A que apunta a una dirección IP válida que se resuelve a través de una herramienta de búsqueda de DNS.
- 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:
- Your domain name
- Una captura de pantalla del error 1018, incluido el RayID mencionado en el mensaje de error.
- 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:
- Retrieve a screenshot of the 1020 error from your customer
- Busca en el Registro de eventos de firewall en la pestaña Descripción general de tu aplicación de firewall de Cloudflare para ver el RayID o la dirección IP del cliente en el mensaje de error 1020 del visitante.
3. Evalúa la causa del bloqueo y actualiza la Regla de firewall o permite la dirección IP del visitante en las Reglas de acceso IP.
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:
- Your domain name
- Una captura de pantalla del error 1023, incluido el RayID mencionado en el mensaje de error.
- 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
Has solicitado una página en un sitio web (tunnel.ejemplo.com) que está en la red de Cloudflare. El servidor (tunnel.ejemplo.com) está configurado como un Argo Tunnel y Cloudflare no puede resolverlo actualmente.
Resolution
- Si eres un visitante del sitio web: por favor, inténtalo de nuevo en unos minutos.
- Si eres el propietario del sitio web: comprueba que cloudflared está funcionando y puede llegar a la red. Si lo deseas, puedes habilitar el equilibrio de carga para tu túnel.
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.