URL Monitoring
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 Authentication Failed error
Authentication Failure Authentication failure occurs when the request to a resource is missing or has invalid credentials. Check if URL requires authentication Access the URL in an incognito/private window and check if any pop up asking for ...
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 ...
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 ...
Monitoring NTLM based URLs is not working
Reason: cryptix-jce-provider.jar might not have been uploaded. Solution: To monitor NTLM authenticated URLs, copy the cryptix-jce-provider.jar from http://www.cryptix.org/cryptix-jce-20050328-snap.zip to '<AppMgr Home>\lib\ext' and restart ...
When I change the IP address of a website, the URL monitor still pings the old IP.
Reason: Upon successful DNS lookup, AppManager, by default, caches the resolved IP forever. Solution: We should specify the amount of time a successful lookup should be cached. To do so, please do the following : 1. Navigate to ...