Error map
504 504 Gateway Timeout from load balancer idle timeout (long request)
HTTP · 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)
Networking: nc -vz hangs then times out — firewall silently DROPs packets (REJECT would answer "Connection refused")
A connection attempt gets no answer at all, which points to a firewall dropping the packets rather than a closed port.
Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
Laravel: Illuminate\Http\Client\ConnectionException: cURL error 28: Operation timed out after 30001 milliseconds with 0 bytes received
The Laravel `Http::` client waited for a response longer than its timeout and gave up.
Networking: Every connection pauses about 5 seconds — resolv.conf nameserver timeout, then fallback to the next DNS server
The first DNS server in the list isn't answering, so each lookup waits out a timeout before trying the next one.
Laravel: Symfony\Component\ErrorHandler\Error\FatalError: Maximum execution time of 30 seconds exceeded
A web request ran longer than PHP's `max_execution_time` and was killed.
Networking: ping — Request timed out / 100% packet loss (host drops or filters ICMP)
No echo reply arrived in time: the host is down, unreachable, or simply ignores ping.
Laravel: Symfony\Component\Process\Exception\ProcessTimedOutException: The process "npm run build" exceeded the timeout of 60 seconds
A subprocess launched via the `Process` class or `Process::run()` exceeded its allowed time.
HTTP 598 Network Read Timeout Error
A non-standard code some proxies use when the upstream didn't send data before the read timeout.
AWS ALB 460 Client Closed Connection
The client closed the connection before the Application Load Balancer sent its response.
WebSocket closed with code 1006 (abnormal closure)
The WebSocket connection dropped without a proper close handshake.
HTTP 599 Network Connect Timeout Error
A non-standard code some proxies and libraries use when they couldn't connect to the upstream in time.
Two steps away (36)
Cloudflare Error 1020: Access Denied
A Cloudflare firewall/WAF custom rule blocked the request — the visitor’s IP, country, user agent or request pattern matched a bl…
ssh: connect to host x port 22: Connection timed out
SSH packets get no reply — a firewall/security group drops them, the server is off, or the IP is wrong.
connect: No route to host (EHOSTUNREACH)
The destination host isn’t reachable — it’s down, on another subnet without routing, or a firewall rejects with “host unreachable…
PHP Fatal error: Maximum execution time of 30 seconds exceeded
The script ran longer than `max_execution_time` and PHP stopped it.
Cloudflare Error 522: Connection Timed Out
Cloudflare’s TCP connection to your origin timed out — the origin didn’t answer at all.
java.util.concurrent.TimeoutException
A Future.get(timeout) or async operation didn’t complete in the allowed time.
HTTP 408 Request Timeout
The server closed the connection because the client took too long to send the complete request.
HTTP 500 Internal Server Error
The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.
HTTP 502 Bad Gateway
A proxy or gateway (Nginx, load balancer, CDN) got an invalid response — or no response — from the upstream server behind it.
Go: Get "https://api.example.com": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
An operation did not finish before its context deadline or HTTP client timeout.
Laravel/PHP 8: ErrorException: Attempt to read property "name" on null
You accessed a property on a value that is `null`, typically an empty relationship or a query that found nothing.
Laravel/PHP: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in vendor/laravel/framework
A request (or artisan job) used more memory than PHP's `memory_limit` allows.
DNS not working inside a Kubernetes pod (could not resolve host / nslookup: can't resolve)
Pods can’t resolve service names or external hosts — CoreDNS is down, blocked by NetworkPolicy, or the upstream resolver fails.
ping: google.com: Temporary failure in name resolution
The Linux host can’t resolve domain names — no working DNS server is configured or reachable.
Networking: Sites load slowly or hang for seconds — broken IPv6 (AAAA resolves, IPv6 route missing) falling back to IPv4
The client prefers IPv6, but the IPv6 path is broken, so every connection waits for a timeout before using IPv4.
Laravel Queue: Illuminate\Queue\MaxAttemptsExceededException: App\Jobs\SendReport has been attempted too many times or run too long
A queued job failed repeatedly or ran past its timeout, so it was marked failed.
Laravel: Symfony\Component\Console\Exception\CommandNotFoundException: Command "make:livewire" is not defined. Did you mean one of these?
`php artisan` doesn't know the command you typed — typo, missing package or an unregistered service provider.
Laravel scheduler: INFO No scheduled commands are ready to run. (tasks never execute)
`schedule:run` is executing but finds nothing due — or the cron entry that triggers it isn't set up.
driver failed programming external connectivity on endpoint: iptables: No chain/target/match by that name
Docker’s iptables rules were wiped (firewalld/ufw reload, iptables flush) while Docker was running, so it can’t publish ports.
Azure SQL: Cannot open server 'x' requested by the login. Client with IP address 'y' is not allowed to access the server (Error 40615)
The Azure SQL server firewall doesn’t allow your client’s IP address.
Cloudflare Error 1005: Access denied — The owner of this website has banned the autonomous system number (ASN) your IP address is in
The site owner blocked your network provider (ASN) — common for VPNs, cloud/data-center IPs and some mobile carriers.
Redis: Closing idle client / Connection closed by server after timeout 300
Redis' `timeout` directive closes connections idle longer than N seconds.
Redis client: Error: Command timed out / redis.exceptions.TimeoutError: Timeout reading from socket
The client waited longer than its timeout for a Redis reply.
SMTP connection closed unexpectedly: greeting delay, tarpit or anti-bot rejection before EHLO
The server delays or drops connections before the greeting, or closes after EHLO, so clients time out ("Connection closed", "gree…
HTTP 407 Proxy Authentication Required
A proxy between you and the server requires credentials before it will forward your request.
HTTP 511 Network Authentication Required
A captive portal (hotel, airport, office Wi-Fi) is intercepting your traffic until you log in or accept its terms.
Chrome: No internet — There is something wrong with the proxy server. ERR_TUNNEL_CONNECTION_FAILED
Chrome asked a proxy to open a tunnel (HTTPS CONNECT) to the website and the proxy refused or could not reach it.
HTTP 499 Client Closed Request (Nginx)
Nginx-specific code logged when the client disconnected before the server finished responding.
{"message":"Missing Authentication Token"} / No authorization token was found
The request reached a protected endpoint without credentials — or, on AWS API Gateway, it hit a path/method that doesn’t exist.
AWS Cognito: NotAuthorizedException: Incorrect username or password
Cognito rejected the sign-in — wrong credentials, a disabled user, an auth flow not enabled on the app client, or an expired refr…
WebSocket connection to 'wss://x' failed
The browser couldn’t open (or keep) a WebSocket connection.
Browser: WebSocket connection to 'wss://example.com/socket' failed: Error during WebSocket handshake: Unexpected response code: 400 (nginx proxy)
Nginx isn't forwarding the `Upgrade`/`Connection` headers needed for WebSockets.
Networking: Connection works, then fails after being idle — firewall/NAT idle timeout dropped the TCP session (use keepalive)
A connection that sat idle was forgotten by a firewall or NAT device, so the next packet gets reset or vanishes.
HTTP 218 This is fine (Apache)
A non-standard Apache status that some hosts use to let an error body pass through a proxy.
HTTP 420 Enhance Your Calm
A non-standard rate-limit response (originally Twitter's) telling you to slow down.
HTTP 440 Login Time-out (IIS)
Microsoft IIS reports that the client's session has expired and a new login is needed.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError