Troubleshooting Server error responses

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 from the applications manager installed machine at the time the error is reported and check what response code is returned by using developer tools.
  1. If the response code returned in browser is 502, 503, 504, then check the URL's server for overload. 
  2. If the response returned in browser is 200, Then check if the proxy is configured in applications manager. If the proxy is configured in applications manager and the proxy is not required for the URL, kindly add an entry for the URL's hostname in the "Do not use proxy for addresses beginning with" field. Similarly, If the proxy is not configured in applications manager and the URL requires proxy, Then configure proxy in applications manager.

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.

                    New to ADSelfService Plus?

                      • Related Articles

                      • 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 ...
                      • Azure Kubernetes Service(AKS) Troubleshooting FAQs

                        Azure Kubernetes Service(AKS) monitor can be configured only if you have already added a Microsoft Azure monitor in Applications Manager. Ensure that you have met all the prerequisites for the Microsoft Azure monitor before monitoring Azure ...
                      • Real User Monitor (RUM) - Troubleshooting

                        If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...
                      • 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.  ...