HTTP Status Code
The page opens to a 404 error. Did I write the wrong link, or was the deployment incomplete?
The page opens to a 404 error. Did I write the wrong link, or was the deployment incomplete?
/old-page404The server has no such resource/save500The server failed while handling it/dashboard401The identity was not accepted/home200This request succeededCheck server logs for this request; the page message cannot replace the status code
Use the buttons above to switch status-code scenarios. The first digit groups the outcome (2xx success, 3xx redirect, 4xx client error, 5xx server error); the exact number narrows the cause.
Read the category first: The first digit groups response classes: 2xx success, 3xx redirection, 4xx client error, and 5xx server error. This guides the next check; use the request and logs to locate a cause.
The exact number narrows the cause: A 404 response says the target resource was not found, 401 means valid authentication credentials are missing, and 400 signals a problem with the request. Check the URL, request, and response for the cause.
Where to find it: The browser Network panel records the status code of every request; debugging tools and errors reported by AI agents also print the number directly.
The page returns 404 and the form returns 500. Check each URL, status, and response in Network; review the route or deployment for the 404, and correlate the 500 request ID with server logs. After fixing it, resend and verify the page and saved data.