Troubleshooting

Interpreting Error Codes

12 views Updated 2 days ago

HTTP status codes indicate what happened during a check.

Common Status Codes

2xx Success Codes

  • 200 OK: Page loaded successfully
  • 201 Created: Resource created (APIs)
  • 204 No Content: Success but no content

3xx Redirection Codes

  • 301 Moved Permanently: Permanent redirect
  • 302 Found: Temporary redirect
  • 304 Not Modified: Cached content valid

4xx Client Error Codes

  • 400 Bad Request: Invalid request
  • 401 Unauthorized: Authentication required
  • 403 Forbidden: Access denied
  • 404 Not Found: Page does not exist
  • 429 Too Many Requests: Rate limited

5xx Server Error Codes

  • 500 Internal Server Error: Server problem
  • 502 Bad Gateway: Proxy/gateway error
  • 503 Service Unavailable: Server overloaded
  • 504 Gateway Timeout: Server too slow to respond

What to Do

For 4xx Errors

  • Check if URL is correct
  • Verify authentication if required
  • Check if monitoring IP is allowed

For 5xx Errors

  • Check server logs
  • Verify server is running
  • Check database connections
  • Review recent deployments

For Timeout Errors

  • Check server performance
  • Review slow database queries
  • Optimize code if needed
  • Consider scaling resources