HTTP troubleshooting
301 Moved Permanently
The requested resource has permanently moved to a new URL. Update monitors to the new URL or follow redirects if intended. 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 301 means for a monitor
Statixoup records an incident when 301 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Check the Location header for the new URL.
- 2.
Check 2
Update the monitor URL to the new permanent location.
- 3.
Check 3
Avoid following redirects when you need explicit original-host checks.
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.