HTTP troubleshooting
403 Forbidden
The server understood the request but refused it because of access policy or missing permission.
What 403 means for a monitor
Statixoup records an incident when 403 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Check IP allowlists, firewall, CDN, and bot protection.
- 2.
Check 2
Confirm the credentials have permission.
- 3.
Check 3
Review required headers and HTTP method.
- 4.
Check 4
Inspect server or edge logs.
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.