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 resolve 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 using cURL/Wget commands.
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 new tab in a browser from Applications Manager installed server.
- Press F12 or open the Network tab in developer tools.
- Access the problematic URL and check the response code in the Network tab under status column 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 in the URL add/edit monitor page.
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.
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.
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.
Forbidden URL
Response Code: 403
Forbidden URL error indicates that the request from Applications Manager does not have the privilege to access the resource. In such cases, verify the below cases.
- Check if the resource credentials configured(If any) in URL Monitor has the privilege to access the resource.
- Check the User-Agent value associated with the URL monitor. You can get your User-Agent's value from here. After entering the User Agent value in User Agent field under HTTP Configurations in the edit monitor page, 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 and 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 in 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 indicates 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.
Still facing issues?
If the problem persists, contact our support team along with the following details:
- A screenshot of the "Add Monitor" page.
- The URL debug tool response for the URL monitor.
- Reproduce the issue and share the latest Support Information File (SIF) from Applications Manager, with the "Print all logs" option enabled. To do this, go to Settings > Logging, and choose "Print all logs".
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the below steps for troubleshooting. Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer this help ...How to generate a URL Debug Tool Response for troubleshooting?
The URL Debug Tool in Applications Manager helps you analyze and troubleshoot the performance of URLs and their components on webpages. It executes the URL, collects performance data, and provides detailed reports for further analysis. Follow the ...DNS Monitor - Troubleshooting
Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...Mail Server Monitor - Troubleshooting
Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...REST API Monitor - FAQS
1. What to do when Basic Authentication fails in REST API monitor? When Basic Authentication fails in the REST API monitor, follow the below steps to troubleshoot the error. Ensure the credentials provided in Applications Manager (Username and ...