URL Monitoring
Troubleshooting Server error responses
When encountering the following server error responses—Bad Gateway (502), Service Unavailable (503), and Gateway Timeout (504)—it typically indicates issues with the server hosting the URL. Troubleshooting Review your server's access logs for the 30 ...
Troubleshooting Bad Request and Internal Server error
When a server responds with a Bad Request (400) or Internal Server Error (500), It typically indicates issues with how the request is being made or processed. The reasons for these errors can vary, but the most common causes are Incorrectly formatted ...
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
When configuring a URL monitor in Applications Manager, you might encounter several errors related to accessibility, configuration, or server-side issues. Below are common errors along with step-by-step troubleshooting instructions to help you ...
Troubleshooting SSL Handshake Error
An SSL Handshake error typically occurs when a secure connection cannot be established due to issues like incompatible SSL protocol versions, ciphers or missing client certificates. Verify URL Accessibility Ensure that the URL you’re monitoring is ...
Prerequisites - URL Monitoring
Prerequisites: Ensure that the URL you want to monitor is accessible from the machine where Applications Manager is installed. Check if the proxy is configured in Machine/Browser for accessing the URL. If so, the same proxy settings must be ...
When I change the IP address of a website, the URL monitor still pings the old IP.
Reason: Upon successful DNS lookup, Applications Manager by default, caches the resolved IP forever. This IP might be used even if there is a change in IP address. Solution: We should specify the amount of time a successful lookup should be cached. ...