HTTPS Monitoring Failed

Last Modified

Fri Nov 23 22:44 GMT 2018

Description

  • HTTPS Service on the indicated device is showing as failed based on 'HTTPS Availability' but all other fields show as correct.
  • How is it possible that the service picked up the SSL cert / expiration and is reporting on this, but somehow the HTTPS service is unavailable?

Environment

  • N-able N-central 9.5+

Solution

  1. Check the configuration of the service. Both HTTP and HTTPS services require some configuration on each device even when applied via a Service Template, specifically the URL and any required login information are specific not only to the server but to each web instance tied to that server (eg. mail.example.com would need to be in the URL field to monitor the availability of the HTTPS services on an exchange server).
  2. The availability of a Web server is based on the response code returned by the HTTPS response header. This will appear as Failed if the CA certificate of the Web server has not been uploaded or if it is not in the default CA certificate file.
  3. Other errors can be found by trying to load the web page on the monitoring device, via we page on the Probe for example.
  • Here is a link to further explain HTTPS monitoring by N-able N-central : HTTPS Service