Error map

506 HTTP 506 Variant Also Negotiates

HTTP · layer 2, Network

Open the full error page →

Centre: this error. First ring: errors it is linked with (3). 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.

2 · Network 6 · Platform & cloud
506 — HTTP 506 Variant Also Negotiates (HTTP)506500 — HTTP 500 Internal Server Error (HTTP)500406 — HTTP 406 Not Acceptable (HTTP)406507 — HTTP 507 Insufficient Storage (HTTP)507404 — HTTP 404 Not Found (HTTP)404502 — HTTP 502 Bad Gateway (HTTP)502503 — HTTP 503 Service Unavailable (HTTP)503400 — HTTP 400 Bad Request (HTTP)400403 — HTTP 403 Forbidden (HTTP)403415 — HTTP 415 Unsupported Media Type (HTTP)415ENOSPC — no space left on device (Docker / Linux) (Docker)ENOSPC413 — HTTP 413 Content Too Large (Request Entity Too Large) (HTTP)413429 — HTTP 429 Too Many Requests (HTTP)429

Directly related (3)

500HTTP

HTTP 500 Internal Server Error

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

406HTTP

HTTP 406 Not Acceptable

The server can’t produce a response in any format listed in the request’s Accept headers.

507HTTP

HTTP 507 Insufficient Storage

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

Two steps away (9)

404HTTP

HTTP 404 Not Found

The server can’t find anything at the requested URL.

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.

503HTTP

HTTP 503 Service Unavailable

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

400HTTP

HTTP 400 Bad Request

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

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…

415HTTP

HTTP 415 Unsupported Media Type

The server refuses the request because the body’s Content-Type isn’t one it accepts.

ENOSPCDocker

no space left on device (Docker / Linux)

The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.

413HTTP

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.

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.

Map another error

Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException