root@hack3rs:/srv/www$ curl -i /401/
HTTP/1.1 401 Unauthorized
Authentication is required or the credentials were rejected.
status-summary.log
HTTP 401 Unauthorized
The request reached the server but lacks valid authentication. The session may have expired, the token may be invalid, or credentials were not sent at all.
Check token expiry, clock skew, and IdP health before assuming an application bug. Most 401s are credential or session problems, not code problems.
likely-causes.lst
- $Expired or missing session cookie or Authorization header.
- $Revoked API key, invalid token signature, or failed MFA challenge.
- $System clock skew causing JWT expiry or nbf validation to fail.
- $SSO or identity provider outage upstream.
recovery-steps.md
- Re-authenticate and get a fresh token or session.
- Verify token claims: audience, issuer, expiry, and not-before.
- Check IdP and auth gateway health dashboards and logs.
- Confirm the account has access to the target environment — not just valid credentials.
quick-actions.sh
ops-note.txt
Use these pages for debugging and user guidance. In production, configure your host or reverse proxy to return the matching HTTP status code for the route (especially for 401 and 404/500 responses) rather than serving a 200 with error-themed content.