Error map

1035 Cloudflare Error 1035 / 1036: Invalid request rewrite (invalid URI path / query string)

Cloudflare · layer 3, Edge & web server

Open the full error page →

Centre: this error. First ring: errors it is linked with (7). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.

1035 — Cloudflare Error 1035 / 1036: Invalid request rewrite (invalid URI path / query string) (Cloudflare)10351002 — Cloudflare Error 1002: DNS points to Prohibited IP / Restricted (Cloudflare)10021003 — Cloudflare Error 1003: Direct IP access not allowed (Cloudflare)10031000 — Cloudflare Error 1000: DNS points to prohibited IP (Cloudflare)10001040 — Cloudflare Error 1040 / 1041: Invalid request header modification (Cloudflare)10401004 — Cloudflare Error 1004: Host Not Configured to Serve Web Traffic (Cloudflare)10041037 — Cloudflare Error 1037: Invalid rewrite rule (failed to evaluate expression) (Cloudflare)10371001 — Cloudflare Error 1001: DNS resolution error (Cloudflare)1001ERR_NAME_NOT_RESOLVED — net::ERR_NAME_NOT_RESOLVED (This site can't be reached — server IP address could not be found) (JavaScript)ERR_NAME_NOT_RESOLV…cURL error 6 — cURL error 6: Could not resolve host: api.example.com (PHP)cURL error 6Pending validation — ACM certificate stuck in Pending validation (AWS)Pending validation530 — Cloudflare HTTP 530 (with Error 1016 Origin DNS error / 1033 tunnel error) (Cloudflare)5301013 — Cloudflare Error 1013: HTTP hostname and TLS SNI hostname mismatch (Cloudflare)10131014 — Cloudflare Error 1014: CNAME Cross-User Banned (Cloudflare)1014413 — HTTP 413 Content Too Large (Request Entity Too Large) (HTTP)413DB connection — WordPress: Error Establishing a Database Connection (WordPress)DB connectionENOTFOUND — Error: getaddrinfo ENOTFOUND host / Name or service not known (API)ENOTFOUNDHeaders already sent — Warning: Cannot modify header information - headers already sent (PHP)Headers already sentCORS — CORS Error: No 'Access-Control-Allow-Origin' header is present (API)CORS411 — HTTP 411 Length Required (HTTP)411sudo: unable to resolve host — sudo: unable to resolve host <hostname>: Name or service not known (Linux)sudo: unable to res…1016 — Cloudflare Error 1016: Origin DNS error (Cloudflare)10161018 — Cloudflare Error 1018: Could not find host (Cloudflare)1018Could not resolve host — fatal: unable to access 'https://github.com/…': Could not resolve host: github.com (Git)Could not resolve h…UnknownHostException — java.net.UnknownHostException: api.example.com (Java)UnknownHostExceptionENOTFOUND — npm ERR! code ENOTFOUND — request to https://registry.npmjs.org/x failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org (npm)ENOTFOUND

Directly related (7)

Two steps away (18)

ERR_NAME_NOT_RESOLVEDJavaScript

net::ERR_NAME_NOT_RESOLVED (This site can't be reached — server IP address could not be found)

DNS couldn’t resolve the hostname in the browser.

cURL error 6PHP

cURL error 6: Could not resolve host: api.example.com

PHP cURL couldn’t resolve the hostname via DNS.

Pending validationAWS

ACM certificate stuck in Pending validation

ACM is waiting to see the DNS (or email) validation record — it wasn’t created, was created in the wrong DNS zone, or has a typo.

530Cloudflare

Cloudflare HTTP 530 (with Error 1016 Origin DNS error / 1033 tunnel error)

Cloudflare returns 530 together with a 1xxx error; the 1xxx code (usually 1016 or 1033) tells you the real cause.

1013Cloudflare

Cloudflare Error 1013: HTTP hostname and TLS SNI hostname mismatch

The TLS SNI (the hostname used for the certificate) differs from the HTTP Host header in the same request.

1014Cloudflare

Cloudflare Error 1014: CNAME Cross-User Banned

Your DNS CNAME points to a hostname in another Cloudflare account, which Cloudflare blocks by default for security.

413HTTP

HTTP 413 Content Too Large (Request Entity Too Large)

The request body is bigger than the server is willing to accept — usually a file upload over the configured limit.

DB connectionWordPress

WordPress: Error Establishing a Database Connection

WordPress can’t connect to its MySQL/MariaDB database with the credentials in wp-config.php, or the database server is down.

ENOTFOUNDAPI

Error: getaddrinfo ENOTFOUND host / Name or service not known

DNS lookup for the hostname failed — the name is wrong, doesn’t exist, or this machine can’t resolve it.

Headers already sentPHP

Warning: Cannot modify header information - headers already sent

You called `header()`, `setcookie()` or `session_start()` after output had already been sent to the browser.

CORSAPI

CORS Error: No 'Access-Control-Allow-Origin' header is present

The browser blocked a cross-origin request because the server’s response didn’t include the CORS headers allowing your site’s ori…

411HTTP

HTTP 411 Length Required

The server refuses a request with a body but no Content-Length header.

sudo: unable to resolve hostLinux

sudo: unable to resolve host <hostname>: Name or service not known

The machine’s hostname isn’t in /etc/hosts (or DNS), so sudo prints this warning — usually after changing the hostname.

1016Cloudflare

Cloudflare Error 1016: Origin DNS error

Cloudflare can’t resolve the origin hostname your DNS record points to (usually a CNAME target).

1018Cloudflare

Cloudflare Error 1018: Could not find host

The hostname isn’t found on Cloudflare — the zone was recently added/removed, or the record doesn’t exist yet.

Could not resolve hostGit

fatal: unable to access 'https://github.com/…': Could not resolve host: github.com

DNS lookup for the Git host failed from this machine.

UnknownHostExceptionJava

java.net.UnknownHostException: api.example.com

DNS resolution failed for the hostname.

ENOTFOUNDnpm

npm ERR! code ENOTFOUND — request to https://registry.npmjs.org/x failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org

npm couldn’t resolve the registry hostname.