Error map
NAT gateway SNAT port exhaustion (ErrorPortAllocation) Networking: NAT gateway ErrorPortAllocation / SNAT port exhaustion — intermittent outbound connection timeouts
Networking · layer 2, Network
Centre: this error. First ring: errors it is linked with (9). 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 (9)
Docker: Bind for 0.0.0.0:80 failed: port is already allocated
Another container or host process already publishes that host port.
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.
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Nginx (or another server) can’t listen on the port because another process already holds it — often Apache, another Nginx, or a s…
Networking: Port forwarding configured but the port stays closed — carrier-grade NAT (CGNAT) or double NAT
Your router forwards the port correctly, but another NAT in front of it (your ISP or a second router) blocks inbound connections.
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.
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.
Networking: kernel: nf_conntrack: table full, dropping packet — new connections fail on a Linux firewall/NAT host
The connection-tracking table is full, so the kernel drops packets for any new connection.
Networking: Server reachable from the internet but not from inside the LAN via its public IP — NAT loopback / hairpin NAT not working
Devices on your own network can't use the router's public address to reach a server that is also on that network.
Networking: connect: Cannot assign requested address — ephemeral port range exhausted by TIME_WAIT connections
The machine ran out of local ports for new outgoing connections to the same destination.
Two steps away (27)
Error: listen EADDRINUSE: address already in use :::3000
Another process is already listening on that port.
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.
Conflict. The container name "/x" is already in use by container …
A container (running or stopped) already has that name; Docker won’t create a second one with the same name.
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…
Web server failed to start. Port 8080 was already in use.
Spring Boot couldn’t bind its embedded server port because another process uses it.
Error: listen EACCES: permission denied 0.0.0.0:80
Node isn’t allowed to bind that port — ports below 1024 need root on Linux/macOS, and some Windows ports are reserved.
HTTP 403 Forbidden
The server understood the request but refuses to authorize it — you (or the server process) are not allowed to access this resour…
Nginx 444 No Response (connection closed without response)
An Nginx-specific code: the server deliberately closed the connection without sending anything — a rule is dropping the request.
Nginx 400: The SSL certificate error (495 / 496 client certificate)
Nginx rejected the request because the client certificate was invalid (495) or missing (496) on a site that requires mutual TLS.
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.
Networking: Wi-Fi keeps disconnecting / signal -80 dBm / wlan0: deauthenticating by local choice (reason=3)
The wireless link is too weak or too noisy to hold, so the client drops and rejoins repeatedly.
Networking: Interface down — SFP transceiver Loss of Signal / no receive light
A fibre or SFP link is down because the transceiver receives no light.
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…
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.
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…
client_loop: send disconnect: Broken pipe (SSH session drops when idle)
The SSH connection was cut — usually an idle timeout on a NAT router, firewall or the server, sometimes a network change.
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.
Cloudflare Error 1006 / 1007 / 1008: Access denied — Your IP address has been banned
The site owner (or a Cloudflare security setting) blocked your IP address.
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.
Networking: `arp -n` shows (incomplete) / Destination Host Unreachable — no ARP reply from the next hop
The machine asked "who has this IP?" and nobody on the local network answered.
Networking: TCP: request_sock_TCP: Possible SYN flooding on port 80. Sending cookies. Check SNMP counters.
The server's pending-connection queue filled, so the kernel switched to SYN cookies to survive.
Networking: Windows: Default gateway is not available / Diagnose Connection Problems: DHCP not enabled
The PC can't reach its router, so it has no path out of the local network.
Networking: DNS changed but the domain still resolves to the old IP — TTL and resolver caching ("propagation")
You updated a DNS record, but resolvers and devices keep serving the old answer until its TTL expires.
Networking: VPN connected but internal names like db.corp.local don't resolve — split DNS / 127.0.0.53 stub resolver not using the VPN DNS
The VPN works by IP, but internal hostnames fail because queries still go to your normal DNS server.
Networking: Network cable unplugged / `ip link` shows NO-CARRIER state DOWN / Ethernet: Network cable unplugged
The network card sees no electrical link, so nothing above it (IP, DNS, browser) can work.
Networking: wlan0: WPA: 4-way handshake failed - pre-shared key may be incorrect / WRONG_KEY
The Wi-Fi association started but key negotiation failed, almost always a wrong password.
Networking: %CDP-4-NATIVE_VLAN_MISMATCH / device on the wrong VLAN can't reach the gateway
A port or trunk carries a different VLAN than expected, so hosts silently land on the wrong network.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError