URL monitoring - Common error codes

While performing URL monitoring in OpManager, there are a few common errors encountered when adding and monitoring URLs. The error codes and measures needed to resolve those issues are as follows:

Response status code Description Ways to resolve
301 Moved Permanently "Moved Permanently" means permanent URL redirection. To monitor such URLs in OpManager, we need to monitor the final redirected URL in OpManager.
302 Moved Temporarily A common way of performing URL redirection. The requested resource resides temporarily under a different URI. To monitor such URLs in OpManager, we need to monitor the final redirected URL in OpManager.
400 Bad Request The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing). This issue needs URL-side troubleshooting in order to be fixed.
403 Forbidden The server understood the request, but is refusing to fulfill it. This may be due to the user not having the necessary permissions for a resource or attempting a prohibited action. This issue needs URL-side troubleshooting in order to be fixed.
500 Internal Server Error An unexpected condition was encountered on the server side. This issue needs URL-side troubleshooting in order to be fixed.
503 Service Unavailable The server cannot handle the request (because it is overloaded or down for maintenance). This issue needs URL-side troubleshooting in order to be fixed.

Other possible errors:

Error Message Description Ways to resolve
Input/Output transfer has been terminated because the thread performing it was interrupted. This is an issue in the user's environment.  
Certificates does not conform to algorithm constraints. The latest Java version (Java 8) disabled a few weak signature algorithms to improve security. The mentioned URL is using one such weak algorithm. You can view the list of accepted cipher suites in Java 8 here.Note that only OpManager builds later than 12.4 support Java 8, so it might be necessary to upgrade your OpManager installation to the latest version. This issue needs URL-side troubleshooting in order to be fixed.
Certificate required to access the URL is not imported into OpManager. The necessary certificate of the site needs to be imported into OpManager. Go to Settings → Security Settings → Trusted Certificates. Here, you can import the certificate of the URL. Note that this option is available only in OpManager 12.4 and above.
Peer not authenticated. 'SSL Error due to Peer not authenticated' - this exception occurs when the connection made to the server URL is not from the authenticated client. This may be due to wrong SSL version, no certificate being provided, the particular cipher suite being used not supporting authentication or no peer authentication being established during SSL handshaking. This issue needs URL-side troubleshooting in order to be fixed.
Missing WWW-Authenticate header. 'WWW-Authenticate header' is missing from URL response. This issue needs URL-side troubleshooting in order to be fixed.
NTLM version of URL. The latest version of the OpManager supports NTLM version 1.0 and 1.1. Refer the Microsoft help page to know about NTLM versions.
URL might be using Kerberos Authentication. Currently, OpManager does not support Kerberos Authentication NA
Inappropriate Proxy Configuration. Any/all of your proxy configuration details such as server or credentials are wrong. Check your proxy configuration details and configure them properly.
Please increase time-out value to resolve this issue. URL timed out occurred. This issue happens in different situations like when target URL is absent, the IP/domain or port (i.e service) is down and so on. Increase time-out of the URL in OpManager to resolve this issue.
Socket connection reset error occurred. Commonly, this issue is caused by writing to a connection where the other end has already closed normally. In other words, it is an application protocol error. It can also be caused by closing a socket when there is unread data in the socket receive buffer. This issue needs URL-side troubleshooting in order to be fixed.
Video Zone
OpManager Customer Videos
Altaleb Alshenqiti - Ministry of National Guard - Health Affairs
  
  •  IT Admin from "Royal flying doctor service", Australia
     Jonathan ManageEngine Customer
  •  Michael - Network & Tech, ManageEngine Customer
     Altaleb Alshenqiti - Ministry of National Guard - Health Affairs
  •  David Tremont, Associate Directory of Infrastructure,USA
     Todd Haverstock Administrative Director
  •  Donald Stewart, IT Manager from Crest Industries
     John Rosser, MIS Manager - Yale Chase Equipment & Services
 Pricing  Get Quote