Troubleshooting Server error responses
Server error responses
Internal Server Error, Bad Gateway, Service Unavailable and Gateway Timeout are the most common server error messages. Seeing any one among these errors generally indicates an issue with the URL's server.
Troubleshooting for Internal Server Error is mentioned here
Bad Gateway error, Service Unavailable and Gateway Timeout
Check if at the time when this error was occurring, other requests to your server will successful or not. You can check this by accessing the URL server's access logs and check the response code to the requests 30 minutes before and after Applications Manager reported the error. If other requests were failing as well, then check the URL's server for possible overloading or if it was under maintenance at the time.
Access the URL using the browser or cURL/Wget at the time the error is reported and check if a response code among 502, 503 or 504 is returned. If it is, then check the URL's server for overload.
In URL monitor, check "If monitor detects error, re-try immediately to verify error." option. This will allow Applications Manager to verify the server error before reporting the error thus avoiding false positives.
Troubleshooting Bad Request and Internal Server error
Bad Request & Internal Server error When the server of URL cannot understand the request it has received it responds with a Bad request or a malformed syntax error message. If there is an error in processing the request received by the server, it ...
Troubleshooting URL Monitor
Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...
IIS Server monitor - Troubleshooting steps
Troubleshooting guide for adding an IIS Server monitor Troubleshooting 'No data available' error for IIS Server performance metrics (IIS Websites and Application Pools statistics)
AWS EKS Troubleshooting FAQs
AWS EKS monitor can be configured only if you have already added an Amazon monitor in Applications Manager. Ensure that you have met the pre-requisites for the Amazon monitor before monitoring Elastic Kubernetes Service in Applications Manager. How ...
Troubleshooting SSL Handshake Error
SSL Handshake Error SSL Handshake error occurs when a secure connection cannot be established to the URL added for monitoring. Common reasons for it are wrong SSL protocol version, incompatible ciphers, and invalid/missing client-side certificate. ...