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 Manager is installed. You can check that by accessing the URL in a browser or in cURL/Wget.
If the URL is accessible from the server but Applications Manager cannot connect to it, then check the proxy configuration of your system and Applications Manager, ensure they are the same.
For GET URLs, check if the response code being returned by the URL in a browser is the same as the one shown in Applications Manager. To do this,
-
Open a browser in Applications Manager server.
-
Press F12 or open the Network tab in developer tools.
-
Access the problematic URL and check the response code in the Network tab for the URL.
-
If the same response code is shown in Applications Manager then the URL's default response code is not 200.
-
In such cases, modify the "Error if Response Code is" condition to "!=" the URL's default response code.
SSL Handshake Error
Response Code: 615
URL monitors added with
https://
at times can have an issue in establishing a secure connection to the URL's server. In such a case this error message is shown.
Here is how to troubleshoot it
.
Authentication Failed
Response Code: 401
Authentication failure happens when authentication information sent to the URL is incorrect or missing.
Here is how to troubleshoot it
.
Bad Request
Response Code: 400
Bad request error indicates that the request could not be understood by the URL's server.
Here is how to troubleshoot it
.
Forbidden URL
Response Code: 403
Forbidden URL error indicates that the agent making the request does not have the privilege to access the resource. In such cases, check the User-Agent value associated with the url monitor. You can get your User-Agent's value from
https://www.whatismybrowser.com/detect/what-is-my-user-agent
. After entering the value in the edit monitor screen, update the URL monitor and poll the monitor a couple of times and check.
Page Not Found
Response Code: 404
This error indicates that the server can not find the requested resource i.e., the URL is not recognized. Check the URL added for monitoring confirm if it can be accessed successfully from the server where Applications Manager is installed.
Invalid HTTP request method
Response Code: 405
As indicated by the same, the HTTP method used to make the request is invalid. If the URL is using GET then change the request type to POST and vice versa. After this poll the monitor and check. Check the URL's documentation for which HTTP methods does it support.
Internal Server Error
Response Code: 500
This indicates an error while processing the request received by the server.
Here is how to troubleshoot it
.
Bad Gateway
Response Code: 502
Bad Gateway server error response indicates that the server, while acting as a gateway or proxy, received an invalid response from the upstream server.
Here is how to troubleshoot it
.
Service Unavailable
Response Code: 503
The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded.
Here is how to troubleshoot it
.
Gateway Timeout
Response Code: 504
This error response is given when the server is acting as a gateway and cannot get a response in time.
Here is how to troubleshoot it
.
New to ADSelfService Plus?
Related Articles
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 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 ...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 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. ...Troubleshooting - URL Monitoring
Prerequisites: The URL which the customer want to monitor should be accessible from the Machine where the APM is installed. Check if the customer have configured any proxy for accessing the particular URL If yes, then the same proxy must be ...