Error map
Domain still resolves to the old IP (DNS propagation/cache) Networking: DNS changed but the domain still resolves to the old IP — TTL and resolver caching ("propagation")
Networking · layer 2, Network
Centre: this error. First ring: errors it is linked with (12). 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.
Directly related (12)
dial tcp: lookup registry-1.docker.io: no such host / Temporary failure in name resolution during docker build
DNS isn’t working for the Docker daemon or inside build containers, so pulls and package downloads fail.
Chrome: This site can’t be reached — server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN
The DNS server answered that the domain name does not exist (NXDOMAIN) — a typo, an expired or unregistered domain, a missing DNS…
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.
ping: google.com: Temporary failure in name resolution
The Linux host can’t resolve domain names — no working DNS server is configured or reachable.
Error 0x80072EE7 (Windows Update / Microsoft Store: server name could not be resolved)
Windows can’t resolve Microsoft’s server names — DNS, hosts file, proxy or firewall problems.
Cloudflare Error 1000: DNS points to prohibited IP
A proxied DNS record points at a Cloudflare IP address, creating a loop.
Cloudflare Error 1003: Direct IP access not allowed
The request went to a Cloudflare IP address directly (or with a Host header for a domain not on Cloudflare).
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.
Cloudflare Error 523: Origin is unreachable
Cloudflare can’t find a network route to your origin server — the DNS record points to a wrong/unroutable IP or the origin networ…
Cloudflare Error 1001: DNS resolution error
Cloudflare received the request but the hostname isn’t set up on Cloudflare (or the domain was just added and not active yet).
Chrome: No internet — DNS_PROBE_FINISHED_NO_INTERNET (DNS probe finished, no internet)
Chrome’s built-in DNS probe could not reach any DNS server, so the device effectively has no working internet or DNS.
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.
Two steps away (36)
Error: connect ECONNREFUSED 127.0.0.1:5432
Nothing is listening at that host:port — the target service is down or you’re connecting to the wrong address.
HTTP 408 Request Timeout
The server closed the connection because the client took too long to send the complete request.
TypeError: Failed to fetch / NetworkError when attempting to fetch resource
The browser couldn’t complete the request at the network level — CORS, DNS, offline, blocked mixed content, or the server refused…
API Request Timed Out (ETIMEDOUT / ReadTimeout / timeout of 30000ms exceeded)
The client gave up waiting — either for the connection to open or for the response to arrive.
Error: socket hang up / read ECONNRESET
The other side closed the TCP connection abruptly while your client was still using it.
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.
Cloudflare Error 1002: DNS points to Prohibited IP / Restricted
A record points to a private, reserved or Cloudflare IP that Cloudflare won’t proxy to.
Cloudflare Error 1004: Host Not Configured to Serve Web Traffic
The DNS record was just created or changed and Cloudflare hasn’t propagated it yet — or Spectrum/non-HTTP ports are involved.
Cloudflare Error 1016: Origin DNS error
Cloudflare can’t resolve the origin hostname your DNS record points to (usually a CNAME target).
fatal: unable to access 'https://github.com/…': Could not resolve host: github.com
DNS lookup for the Git host failed from this machine.
java.net.UnknownHostException: api.example.com
DNS resolution failed for the hostname.
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.
HTTP 407 Proxy Authentication Required
A proxy between you and the server requires credentials before it will forward your request.
error: RPC failed; HTTP 400 curl 22 / curl 92 HTTP/2 stream was not closed cleanly — the remote end hung up unexpectedly
A large HTTPS push/clone broke mid-transfer — size limits, proxies or flaky HTTP/2.
ssh: connect to host github.com port 22: Connection timed out
Outbound SSH on port 22 is blocked (firewall, corporate or public Wi-Fi).
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.
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.
hint: You have divergent branches and need to specify how to reconcile them.
Git 2.27+ asks you to choose merge, rebase or fast-forward-only when local and remote both have new commits.
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.
Cloudflare Error 1023: Could not find host
Cloudflare can’t find the host — typically a zone that’s inactive or a custom hostname/SSL for SaaS not set up.
Cloudflare Error 1034: Edge IP Restricted
The DNS record points to a Cloudflare IP not assigned to your zone — typically an A record pointing to an old Cloudflare IP or an…
user is not in the sudoers file. This incident will be reported.
Your account isn’t allowed to use sudo.
API Error: Invalid or unsupported API version
The API version you requested — in the URL, a header or the SDK config — doesn’t exist or has been retired.
API Error: Feature not enabled for this account (feature_not_enabled / not available on your plan)
The endpoint or option exists, but your account, plan, region or project hasn’t been granted access to it.
Cloudflare Error 521: Web Server Is Down
Cloudflare couldn’t connect to your origin — the connection was refused.
Cloudflare Error 522: Connection Timed Out
Cloudflare’s TCP connection to your origin timed out — the origin didn’t answer at all.
Cloudflare Error 1033: Argo Tunnel error (Cloudflare Tunnel not connected)
The hostname routes to a Cloudflare Tunnel, but no healthy cloudflared connector is running for it.
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 6: Could not resolve host: api.example.com
PHP cURL couldn’t resolve the hostname via DNS.
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.
net::ERR_BLOCKED_BY_CLIENT
A browser extension (ad blocker, privacy tool) blocked the request.
net::ERR_CONNECTION_REFUSED (This site can't be reached — refused to connect)
The browser reached the host but nothing was listening on that port.
net::ERR_ABORTED 404 (Not Found)
The browser cancelled the request — often because it returned an error (404) or the page navigated away.
cloudflared: Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared (502)
The tunnel is connected, but cloudflared can’t reach your local service at the address in the ingress rule.
Firefox: Hmm. We’re having trouble finding that site. / Server not found (DNS_PROBE or NS_ERROR_UNKNOWN_HOST)
Firefox could not resolve the website’s hostname to an IP address — a typo, a DNS problem or no internet.
Certbot: Detail: DNS problem: NXDOMAIN looking up A for www.example.com - check that a DNS record exists for this domain
Let's Encrypt could not resolve the domain you asked a certificate for; no A/AAAA record exists.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError