HTTP troubleshooting
404 Not Found
The requested path was not found, even though the domain itself may still be reachable. 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 404 means for a monitor
Statixoup records an incident when 404 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Check the exact path and spelling.
- 2.
Check 2
Confirm the route exists in the current deployment.
- 3.
Check 3
Review redirects and base-path changes.
- 4.
Check 4
Update the URL only if the service moved intentionally.
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.