Error map

420 HTTP 420 Enhance Your Calm

HTTP · layer 2, Network

Open the full error page →

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.

420 — HTTP 420 Enhance Your Calm (HTTP)4201015 — Cloudflare Error 1015: You are being rate limited (Cloudflare)1015503 — HTTP 503 Service Unavailable (HTTP)503429 — HTTP 429 Too Many Requests (HTTP)429429 Too Many Requests (Laravel throttle) — Laravel: Illuminate\Http\Exceptions\ThrottleRequestsException: Too Many Attempts. / 429 Too Many Requests (Laravel)429 Too Many Reques…limiting requests, excess: (503 from limit_req) — Nginx: [error] limiting requests, excess: 5.370 by zone "perip", client: 203.0.113.5 (Nginx / Apache)limiting requests, …too many certificates already issued — Let's Encrypt: urn:ietf:params:acme:error:rateLimited :: too many certificates (5) already issued for this exact set of identifiers in the last 168 hours (SSL / TLS)too many certificat…218 — HTTP 218 This is fine (Apache) (HTTP)218450 — HTTP 450 Blocked by Windows Parental Controls (HTTP)450598 — HTTP 598 Network Read Timeout Error (HTTP)598429 — 429 quota exceeded (daily/monthly API limit) (HTTP)429449 — HTTP 449 Retry With (HTTP)449429 — 429 Too Many Requests: honouring Retry-After (HTTP)429ThrottlingException — AWS: ThrottlingException / Rate exceeded (AWS)ThrottlingException1020 — Cloudflare Error 1020: Access Denied (Cloudflare)1020concurrent_requests_limit — API Error: Too many concurrent requests (concurrency limit reached) (API)concurrent_requests…CrashLoopBackOff — Kubernetes: CrashLoopBackOff (Kubernetes)CrashLoopBackOff500 — HTTP 500 Internal Server Error (HTTP)500502 — HTTP 502 Bad Gateway (HTTP)502ImagePullBackOff — Kubernetes: ImagePullBackOff / ErrImagePull (Kubernetes)ImagePullBackOff403 — HTTP 403 Forbidden (HTTP)403507 — HTTP 507 Insufficient Storage (HTTP)507419 Page Expired — Laravel: 419 Page Expired (CSRF token mismatch) (PHP)419 Page Expired421 4.7.0 Try again later (rate limited) — SMTP: 421 4.7.0 Our system has detected an unusual rate of unsolicited mail originating from your IP address. Mail sent from your IP address has been temporarily rate limited (Email / SMTP)421 4.7.0 Try again…SES: Maximum sending rate exceeded — Amazon SES: Throttling — Maximum sending rate exceeded (454 Throttling failure) (Email / SMTP)SES: Maximum sendin…cf-mitigated: challenge — API/app requests get 403 with cf-mitigated: challenge (Bot Fight Mode / challenge on non-browser clients) (Cloudflare)cf-mitigated: chall…nginx: client intended to send too large body — Nginx: [error] client intended to send too large body: 5242880 bytes (413 Request Entity Too Large) (Nginx / Apache)nginx: client inten…worker_connections are not enough — Nginx: [alert] 1234#1234: *987 1024 worker_connections are not enough while connecting to upstream (Nginx / Apache)worker_connections …Challenge failed for domain — Let’s Encrypt / Certbot: Challenge failed for domain example.com — Invalid response from http://example.com/.well-known/acme-challenge/x: 404 (SSL / TLS)Challenge failed fo…SSLCertificateFile: file does not exist — Apache: AH02240: Server should be SSL-aware but has no certificate configured / SSLCertificateFile: file '/etc/ssl/x.crt' does not exist or is empty (SSL / TLS)SSLCertificateFile:…DNS problem: NXDOMAIN looking up A — Certbot: Detail: DNS problem: NXDOMAIN looking up A for www.example.com - check that a DNS record exists for this domain (SSL / TLS)DNS problem: NXDOMA…200 — HTTP 200 OK (but something is still wrong) (HTTP)200506 — HTTP 506 Variant Also Negotiates (HTTP)506AH00558 — Apache: AH00558: apache2: Could not reliably determine the server's fully qualified domain name (Nginx / Apache)AH00558451 — HTTP 451 Unavailable For Legal Reasons (HTTP)451ERR_NETWORK_ACCESS_DENIED — Chrome: This site can’t be reached — ERR_NETWORK_ACCESS_DENIED (blocked by firewall or antivirus) (Browser)ERR_NETWORK_ACCESS_…Could not establish trust relationship for the SSL/TLS secure channel — .NET: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel (SSL / TLS)Could not establish…407 — HTTP 407 Proxy Authentication Required (HTTP)407504 — HTTP 504 Gateway Timeout (HTTP)504511 — HTTP 511 Network Authentication Required (HTTP)511CORS blocked (Laravel API) — Browser: Access to XMLHttpRequest at 'https://api.example.com' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header — Laravel (Laravel)CORS blocked (Larav…422 Unprocessable Entity: The given data was invalid — Laravel: {"message":"The given data was invalid.","errors":{"email":["The email field is required."]}} (422) (Laravel)422 Unprocessable E…102 — HTTP 102 Processing (HTTP)102400 — HTTP 400 Bad Request (HTTP)400428 — HTTP 428 Precondition Required (HTTP)428440 — HTTP 440 Login Time-out (IIS) (HTTP)440201 — HTTP 201 Created (HTTP)201202 — HTTP 202 Accepted (HTTP)202503 — 503 Service Unavailable with Retry-After (maintenance) (HTTP)503

Directly related (12)

1015Cloudflare

Cloudflare Error 1015: You are being rate limited

The site’s Cloudflare rate-limiting rule blocked you for sending too many requests in a short time.

503HTTP

HTTP 503 Service Unavailable

The server is temporarily unable to handle the request — overloaded, in maintenance, or has no healthy backends.

429HTTP

HTTP 429 Too Many Requests

You’ve hit a rate limit — too many requests in a given time window. Slow down and retry later.

429 Too Many Requests (Laravel throttle)Laravel

Laravel: Illuminate\Http\Exceptions\ThrottleRequestsException: Too Many Attempts. / 429 Too Many Requests

Laravel's rate limiter blocked the client for exceeding the allowed requests per minute.

limiting requests, excess: (503 from limit_req)Nginx / Apache

Nginx: [error] limiting requests, excess: 5.370 by zone "perip", client: 203.0.113.5

`limit_req` rejected requests because the client exceeded the configured rate (burst) — response 503 (or 429).

too many certificates already issuedSSL / TLS

Let's Encrypt: urn:ietf:params:acme:error:rateLimited :: too many certificates (5) already issued for this exact set of identifiers in the last 168 hours

You hit a Let's Encrypt rate limit — too many certificates, failed validations or new orders in a period.

218HTTP

HTTP 218 This is fine (Apache)

A non-standard Apache status that some hosts use to let an error body pass through a proxy.

450HTTP

HTTP 450 Blocked by Windows Parental Controls

A Microsoft status shown when Windows Parental Controls blocks the requested site.

598HTTP

HTTP 598 Network Read Timeout Error

A non-standard code some proxies use when the upstream didn't send data before the read timeout.

429HTTP

429 quota exceeded (daily/monthly API limit)

Unlike short-term rate limiting, you used up your daily or monthly allowance for the API key.

449HTTP

HTTP 449 Retry With

A Microsoft extension asking the client to retry after supplying the required information.

429HTTP

429 Too Many Requests: honouring Retry-After

The server told you to slow down and said how long to wait with a Retry-After header.

Two steps away (36)

ThrottlingExceptionAWS

AWS: ThrottlingException / Rate exceeded

You exceeded the request rate for an AWS API; retry with exponential backoff.

1020Cloudflare

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…

concurrent_requests_limitAPI

API Error: Too many concurrent requests (concurrency limit reached)

You have more requests in flight at once than the API allows for your key — even if your requests-per-minute rate is fine.

CrashLoopBackOffKubernetes

Kubernetes: CrashLoopBackOff

The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.

500HTTP

HTTP 500 Internal Server Error

The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.

502HTTP

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.

ImagePullBackOffKubernetes

Kubernetes: ImagePullBackOff / ErrImagePull

The node can’t pull the container image — wrong name/tag, missing registry credentials, or registry unreachable.

403HTTP

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…

507HTTP

HTTP 507 Insufficient Storage

The server can’t store what’s needed to complete the request — the disk, quota or mailbox is full.

419 Page ExpiredPHP

Laravel: 419 Page Expired (CSRF token mismatch)

Laravel rejected a POST because the CSRF token was missing, expired or didn’t match the session.

421 4.7.0 Try again later (rate limited)Email / SMTP

SMTP: 421 4.7.0 Our system has detected an unusual rate of unsolicited mail originating from your IP address. Mail sent from your IP address has been temporarily rate limited

The receiving server (often Gmail or Outlook) is temporarily throttling your mail because the volume or reputation of your sendin…

SES: Maximum sending rate exceededEmail / SMTP

Amazon SES: Throttling — Maximum sending rate exceeded (454 Throttling failure)

You are sending faster than your Amazon SES account's per-second limit, so SES throttles the requests.

cf-mitigated: challengeCloudflare

API/app requests get 403 with cf-mitigated: challenge (Bot Fight Mode / challenge on non-browser clients)

Cloudflare is answering API calls, webhooks or mobile-app requests with a challenge page (HTML 403) because bot protection treats…

nginx: client intended to send too large bodyNginx / Apache

Nginx: [error] client intended to send too large body: 5242880 bytes (413 Request Entity Too Large)

A request body exceeded `client_max_body_size` (default 1 MB), so Nginx returned 413 before reaching your app.

worker_connections are not enoughNginx / Apache

Nginx: [alert] 1234#1234: *987 1024 worker_connections are not enough while connecting to upstream

Nginx ran out of simultaneous connection slots in a worker.

Challenge failed for domainSSL / TLS

Let’s Encrypt / Certbot: Challenge failed for domain example.com — Invalid response from http://example.com/.well-known/acme-challenge/x: 404

Let’s Encrypt couldn’t verify you control the domain — the HTTP-01 challenge file wasn’t served, or DNS points elsewhere.

SSLCertificateFile: file does not existSSL / TLS

Apache: AH02240: Server should be SSL-aware but has no certificate configured / SSLCertificateFile: file '/etc/ssl/x.crt' does not exist or is empty

Apache cannot find the certificate or key file named in its configuration, or `SSLEngine on` is set without any certificate.

DNS problem: NXDOMAIN looking up ASSL / TLS

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.

200HTTP

HTTP 200 OK (but something is still wrong)

The request succeeded at the HTTP level — yet the page is blank, the data is wrong, or an error is hidden inside the response bod…

506HTTP

HTTP 506 Variant Also Negotiates

The server's content-negotiation setup is circular, so it can't pick a representation.

AH00558Nginx / Apache

Apache: AH00558: apache2: Could not reliably determine the server's fully qualified domain name

A harmless startup warning: Apache has no global ServerName, so it guessed one from the host’s IP.

451HTTP

HTTP 451 Unavailable For Legal Reasons

The content is blocked for legal reasons — a court order, government censorship, sanctions, or GDPR geo-blocking.

ERR_NETWORK_ACCESS_DENIEDBrowser

Chrome: This site can’t be reached — ERR_NETWORK_ACCESS_DENIED (blocked by firewall or antivirus)

Something on your computer — usually the Windows firewall or antivirus — denied Chrome network access.

Could not establish trust relationship for the SSL/TLS secure channelSSL / TLS

.NET: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel

A .NET client could not validate the server certificate or negotiate TLS, so the HTTPS call failed.

407HTTP

HTTP 407 Proxy Authentication Required

A proxy between you and the server requires credentials before it will forward your request.

504HTTP

HTTP 504 Gateway Timeout

A proxy or gateway waited too long for the upstream server to respond and gave up.

511HTTP

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.

CORS blocked (Laravel API)Laravel

Browser: Access to XMLHttpRequest at 'https://api.example.com' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header — Laravel

The browser blocked a cross-origin call to your Laravel API because the response lacks the right CORS headers.

422 Unprocessable Entity: The given data was invalidLaravel

Laravel: {"message":"The given data was invalid.","errors":{"email":["The email field is required."]}} (422)

Request validation failed, so Laravel returned HTTP 422 with the field errors.

102HTTP

HTTP 102 Processing

An interim WebDAV response saying the server accepted a long-running request and is still working on it.

400HTTP

HTTP 400 Bad Request

The server could not understand the request because its syntax, headers or body are malformed or invalid.

428HTTP

HTTP 428 Precondition Required

The server requires a conditional request (If-Match / If-Unmodified-Since) to prevent lost updates, and you didn’t send one.

440HTTP

HTTP 440 Login Time-out (IIS)

Microsoft IIS reports that the client's session has expired and a new login is needed.

201HTTP

HTTP 201 Created

The request succeeded and a new resource was created, normally returned after POST or PUT.

202HTTP

HTTP 202 Accepted

The server accepted the request for processing, but the work is not finished yet.

503HTTP

503 Service Unavailable with Retry-After (maintenance)

The service is temporarily down, usually for planned maintenance or deploys, and says when to retry.