Error map
ETIMEDOUT API Request Timed Out (ETIMEDOUT / ReadTimeout / timeout of 30000ms exceeded)
API · layer 4, Application & API
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)
Cloudflare Error 522: Connection Timed Out
Cloudflare’s TCP connection to your origin timed out — the origin didn’t answer at all.
ERR_CONNECTION_TIMED_OUT: This site can’t be reached — example.com took too long to respond
The browser waited for the server but got no response — the server is down/unreachable, a firewall drops traffic, or DNS points t…
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.
cURL error 28: Operation timed out after 30001 milliseconds with 0 bytes received
A PHP cURL (or Guzzle) request timed out before the remote server answered.
Error Domain=NSURLErrorDomain Code=-1001 "The request timed out."
The server didn’t respond within URLSession’s timeout (60 s default) — slow server, unreachable host on this network, or a stalle…
ERROR: canceling statement due to statement timeout
A query ran longer than statement_timeout and PostgreSQL cancelled it.
java.net.ConnectException: Connection refused
Nothing is listening at the host:port the Java client connected to.
java.net.SocketException: Connection reset
The remote side closed the TCP connection abruptly while Java was reading or writing.
Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded)
Docker couldn’t reach the registry in time — a network, DNS, proxy or firewall problem between your machine and the registry.
ERR_CONNECTION_RESET: This site can’t be reached — The connection was reset
The connection to the website was cut off mid-way — by the server, a firewall/antivirus, a VPN/proxy, or network equipment.
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.
AWS Lambda: Task timed out after X seconds
The function ran longer than its configured timeout (default 3 seconds) and Lambda stopped it.
Two steps away (36)
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
Cloudflare Error 520: Web Server Returned an Unknown Error
Cloudflare connected to your origin, but the origin returned an empty, unknown or invalid response.
Cloudflare Error 521: Web Server Is Down
Cloudflare couldn’t connect to your origin — the connection was refused.
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 407 Proxy Authentication Required
A proxy between you and the server requires credentials before it will forward your request.
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…
Error: socket hang up / read ECONNRESET
The other side closed the TCP connection abruptly while your client was still using it.
npm ERR! code ELIFECYCLE / Command failed with exit code 1
An npm script (build, start, test, postinstall) exited with an error. ELIFECYCLE is only the wrapper — the real error is printed…
HTTP 499 Client Closed Request (Nginx)
Nginx-specific code logged when the client disconnected before the server finished responding.
PHP Fatal error: Maximum execution time of 30 seconds exceeded
The script ran longer than `max_execution_time` and PHP stopped it.
Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
MySQL ERROR 2006 (HY000): MySQL server has gone away
The connection to MySQL was closed — usually by a timeout or a packet larger than `max_allowed_packet`.
MySQL ERROR 2013 (HY000): Lost connection to MySQL server during query
The connection dropped mid-query — server crash/restart, timeouts, or a proxy cutting long queries.
FATAL: terminating connection due to idle-in-transaction timeout
A session opened a transaction and sat idle longer than idle_in_transaction_session_timeout.
HTTP 304 Not Modified
The cached copy is still valid, so the server sends no body and the client reuses its cache.
Lock wait timeout exceeded; try restarting transaction (MySQL 1205)
A query waited too long for a row lock held by another transaction and gave up.
ERROR: current transaction is aborted, commands ignored until end of transaction block
An earlier statement in the same transaction failed; PostgreSQL rejects everything until you ROLLBACK.
java.net.UnknownHostException: api.example.com
DNS resolution failed for the hostname.
ConnectionRefusedError: [Errno 111] Connection refused
Nothing is listening on the host/port Python tried to connect to.
SSL error: tlsv1 alert protocol version / unsupported protocol / no protocols available
The client and server couldn’t agree on a TLS version or cipher, so the HTTPS handshake failed before any HTTP was exchanged.
TypeError: Failed to execute 'json' on 'Response': body stream already read
A fetch Response body was consumed twice (e.g. calling .text() then .json()).
TypeError: fetch failed (cause: ConnectTimeoutError / ECONNREFUSED / UND_ERR)
Node’s built-in fetch (undici) couldn’t complete the request; the real reason is in error.cause.
cURL error 6: Could not resolve host: api.example.com
PHP cURL couldn’t resolve the hostname via DNS.
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.
fatal: early EOF — fatal: index-pack failed
A clone or fetch was cut off mid-transfer.
net::ERR_BLOCKED_BY_CLIENT
A browser extension (ad blocker, privacy tool) blocked the request.
fatal: unable to access 'https://github.com/…': Could not resolve host: github.com
DNS lookup for the Git host failed from this machine.
ssh: connect to host github.com port 22: Connection timed out
Outbound SSH on port 22 is blocked (firewall, corporate or public Wi-Fi).
kex_exchange_identification: Connection closed by remote host
The SSH connection was closed before the handshake — server overload, rate limiting, or a proxy/firewall interfering.
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
The docker CLI can’t talk to the Docker engine — it isn’t running, or your user can’t access the socket.
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.
WebSocket connection to 'wss://x' failed
The browser couldn’t open (or keep) a WebSocket connection.
AWS: ThrottlingException / Rate exceeded
You exceeded the request rate for an AWS API; retry with exponential backoff.
java.util.concurrent.TimeoutException
A Future.get(timeout) or async operation didn’t complete in the allowed time.
Lambda: Runtime exited with error: signal: killed (Runtime.ExitError)
The function process was killed — almost always because it ran out of its configured memory.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException