HTTP troubleshooting
401 Unauthorized
The endpoint requires valid authentication, but the monitor did not provide credentials the server accepts. In simple terms, this guide helps you understand why the response may make a monitor appear unhealthy and what to check before changing your monitor settings.
What 401 means for a monitor
Statixoup records an incident when 401 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Confirm this is the intended protected URL.
- 2.
Check 2
Re-enter the basic-auth username and password.
- 3.
Check 3
Check whether the server expects a token or custom header.
- 4.
Check 4
Test without browser cookies.
After the service is fixed
- Confirm the URL returns the expected status without a browser session.
- Review response-time and incident history for the recovery.
- Change Expected status code only when the different response is intentional.
Avoid hiding a real outage
Changing the expected code can make an unhealthy response appear operational. Fix the service first whenever the response is unexpected.