Error map
404 404 only with or without a trailing slash
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)
HTTP 404 Not Found
The server can’t find anything at the requested URL.
HTTP 301 Moved Permanently
The resource has a new permanent URL; clients and search engines should use the address in the Location header from now on.
TypeError: Missing parameter name at 1 (path-to-regexp)
An Express 5 (path-to-regexp v8) route uses old wildcard syntax like '*' or '/:id?'.
Networking: TTL expired in transit — routing loop between routers
A packet ran out of hops before arriving, which usually means two routers keep sending it back and forth.
API Error: Cannot GET /api/... / No route matches / The route could not be found
The server has no route for this URL and HTTP method combination — the endpoint path, API version prefix or method is wrong.
Cloudflare Error 1019: Compute server error (Workers)
A Cloudflare Worker routed the request to a loop or hit an internal compute error.
Next.js: Error: You cannot use different slug names for the same dynamic path ('id' !== 'slug')
Sibling dynamic folders at the same level use different parameter names.
Networking: VPN is connected but I can't reach the internal network — missing routes, split tunnel or overlapping subnets
The tunnel is up, but traffic for the office/VPC subnets isn't sent through it or comes back the wrong way.
Laravel: The GET method is not supported for route x. Supported methods: POST (MethodNotAllowedHttpException)
The URL exists, but not for the HTTP method used — e.g. opening a POST-only route in the browser, or a form sending GET.
Laravel: Symfony\Component\Routing\Exception\RouteNotFoundException: Route [login] not defined
Code called route('name') for a route name that doesn’t exist — very often route('login') from the auth middleware in API-only ap…
Nginx: reverse proxy returns 404 — location /api/ { proxy_pass http://app:3000/; } strips the prefix (or keeps it)
Whether `proxy_pass` has a URI part decides if the matched prefix is stripped, so the backend receives an unexpected path.
HTTP 405 Method Not Allowed
The URL exists, but it doesn’t accept the HTTP method you used (e.g. POST to a GET-only route).
Two steps away (36)
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…
HTTP 410 Gone
The resource used to exist but was intentionally and permanently removed, with no forwarding address.
SyntaxError: Unexpected token < in JSON at position 0
`JSON.parse()` / `response.json()` received something that isn’t JSON — very often an HTML error page.
Cloudflare Error 520: Web Server Returned an Unknown Error
Cloudflare connected to your origin, but the origin returned an empty, unknown or invalid response.
HTTP 302 Found (Temporary Redirect)
The resource is temporarily at another URL; clients should keep using the original URL for future requests.
HTTP 304 Not Modified
The cached copy is still valid, so the server sends no body and the client reuses its cache.
Whitelabel Error Page — This application has no explicit mapping for /error
Spring Boot’s default error page — the request hit no controller mapping (404) or a controller threw (500).
Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
An Express/Node handler tried to send a second response (or set headers) after one was already sent.
Express: req.body is undefined / {} (body parser missing)
Express didn’t parse the request body because no body-parsing middleware matched the request’s Content-Type.
connect: Network is unreachable (ENETUNREACH)
The host has no route to the destination network — no default gateway, interface down, or trying IPv6 without IPv6 connectivity.
SMTP: 554 5.4.14 Hop count exceeded - possible mail loop
The message passed through too many mail servers (usually over 25), which almost always means two systems forward mail to each ot…
Networking: ping — Destination Host Unreachable / Destination net unreachable (ICMP type 3)
A router (or your own PC) tells you it has no way to deliver the packet to that address.
URIError: URI malformed
decodeURIComponent/decodeURI received an invalid percent-encoded sequence.
No routes matched location "/x"
React Router found no route definition for the current URL.
Error: NextRouter was not mounted.
next/router’s useRouter was used inside the App Router (app/ directory), which uses next/navigation instead.
Cloudflare Error 1025: Please check back later (Workers request limit)
The site’s Cloudflare Workers plan exceeded its daily request limit (free plan: 100,000 requests/day).
Cloudflare Error 1101: Worker threw exception
The Cloudflare Worker serving this route threw an uncaught JavaScript exception.
Cloudflare Error 1102: Worker exceeded resource limits (CPU time / memory)
The Worker used more CPU time or memory than its plan allows for a single request.
Next.js: You're importing a component that needs createContext. It only works in a Client Component but none of its parents are marked with "use client"
A context provider (or a lib that uses `createContext`) is used in a Server Component.
Next.js 15: Error: Route "/blog/[slug]" used `params.slug`. `params` should be awaited before using its properties
In Next.js 15 `params` and `searchParams` are Promises; reading properties synchronously triggers this error/warning.
Next.js: Page "/blog/[slug]" is missing "generateStaticParams()" so it cannot be used with "output: export" config
A dynamic route can't be statically exported without telling Next.js which paths to generate.
Networking: Two hosts on one LAN can't talk — subnet mask or network address mismatch
The hosts disagree about which addresses are local, so one tries to route traffic that should go straight across the LAN.
Networking: SSH/HTTPS connects but hangs on large data — path MTU discovery black hole
Small packets pass but full-size ones vanish, so logins work and then transfers or page loads stall.
Networking: %OSPF-5-ADJCHG: Nbr 10.0.0.2 from EXSTART to DOWN — OSPF neighbor stuck in EXSTART/EXCHANGE (MTU mismatch)
Two OSPF routers see each other but never finish exchanging databases, cycling between EXSTART and DOWN.
AmbiguousMatchException: The request matched multiple endpoints. Matches: X, Y
Two controller actions or minimal API endpoints have the same route and HTTP method.
WordPress REST API: {"code":"rest_no_route","message":"No route was found matching the URL and request method."}
The REST endpoint doesn’t exist for that URL and HTTP method — wrong namespace/route, plugin not active, or route registered too…
Angular: NG8002: Can't bind to 'ngModel' since it isn't a known property of 'input'
The template uses a property binding that no imported directive provides — for ngModel, FormsModule isn’t imported.
Git: Permission denied (publickey). fatal: Could not read from remote repository.
SSH authentication to GitHub/GitLab/Bitbucket failed — no key, wrong key, or the key isn’t added to your account.
Azure AD (Entra ID): AADSTS700016 Application not found in the directory
The client ID in your sign-in request doesn’t exist in the tenant you’re authenticating against.
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
Ingress returns "404 Not Found" / "default backend - 404" (ingress-nginx)
The ingress controller received the request but no Ingress rule matched the host/path, so it answered with its default backend.
Nginx: [error] upstream sent too big header while reading response header from upstream (502 Bad Gateway)
The backend's response headers (cookies, Set-Cookie, long headers) exceeded Nginx's proxy/fastcgi buffer size.
Nginx: [error] connect() failed (111: Connection refused) while connecting to upstream, upstream: "http://127.0.0.1:3000/"
Nginx tried to proxy a request but nothing listens on the upstream address, so the client gets 502.
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
CORS Error: No 'Access-Control-Allow-Origin' header is present
The browser blocked a cross-origin request because the server’s response didn’t include the CORS headers allowing your site’s ori…
HTTP 501 Not Implemented
The server doesn’t support the functionality (usually the HTTP method) needed to fulfil the request.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError