Help / Monitors
SSL certificate monitor
An SSL certificate monitor connects to a server, reads its certificate and warns you before it expires. It also tells you when the certificate stops being valid, for example when it is not trusted or does not match the name.
Do you need one?
If you already have a website monitor on an https:// address, it reads the certificate on every check. It sends a certificate warning when fewer days are left than its Warn before certificate expiry (days) setting, which is 14 by default. The same goes for keyword monitors.
A separate SSL certificate monitor is useful when:
- the certificate is on a port other than 443, such as a mail server on 993;
- you want the certificate watched on its own, apart from whether the site answers; or
- you want an outage-style alert, with an incident, when the certificate is close to expiry.
What you need first
- The host name the certificate is for, such as
www.example.com. Use the name, not the IP address: the check compares the certificate against the name you type. - The port, if it is not 443.
Set it up
- Open Monitors and press Add monitor.
- Choose SSL certificate.
- In Host, type the host name. If you paste a full address, the
https://and anything after the name are ignored. - In Port, type the port. Leave it empty for 443.
- Give it a Friendly name.
- Open More settings and set Warn before certificate expiry (days). The default is 14. You can choose from 1 to 365.
- Look over Where alerts go and press Start monitoring.
What it checks
Each check opens a secure (TLS) connection and reads the certificate the server presents. The check fails when:
- the certificate cannot be verified, for example because it has expired, it is self-signed, the chain is incomplete, or it does not cover the host name; or
- it expires in fewer days than your warning setting.
A failed check counts like any other. With the default settings, two cities must fail twice in a row. The monitor then goes down, an incident opens, and a down alert goes out with the reason, for example "Certificate expires in 12 days". So make sure your alert channels have Down ticked on the Alerts page. When you renew the certificate, the monitor comes back up and a recovery message goes to channels that have Back up ticked.
The monitor page shows the days left, the expiry date and who issued the certificate.
The check starts TLS as soon as it connects. Ports where the server first talks in plain text and switches to TLS later (STARTTLS, such as mail on port 587) cannot be checked this way. Use the TLS port instead, such as 465 or 993 for mail.
Certificate warnings from website monitors
Website and keyword monitors work differently. Their certificate warning is a separate alert, sent once, while the site keeps counting as up. It goes to channels that have Certificate expiring ticked on the Alerts page. When a renewed certificate has more days left than the setting, the warning is reset and can be sent again next time.
Send a test
Open Alerts and press Send test on each channel. Then open the monitor. After the first round, it should show the days left and the issuer.
When it does not work
- "Certificate not trusted". The certificate could not be verified. Common causes are an expired certificate, a self-signed certificate, a missing intermediate certificate on the server, or a certificate for a different name. Hold the pointer over the message to see the full reason. If the certificate has expired, renew it: the monitor recovers on the next checks after the new certificate is in place.
- "Timed out" or "Connection refused". Nothing answered on that port. Check the port number, and that a firewall is not blocking it. See Allowing our checks through a firewall.
- "Secure connection (TLS) cut off by the server". The server closed the connection during the handshake. This often means the port does not speak TLS straight away.
- You renewed, but it still warns. Some servers need a restart or reload before they serve the new certificate. Check that the expiry date on the monitor page has changed.
Still stuck? Email [email protected] and say which guide you were following.