
Even with auto-renewal in place, certificates expire unexpectedly. A DNS change can block the ACME validation challenge. A Certbot installation can become stale after an OS upgrade. A server migration can leave auto-renewal configured on the old server but not the new one. When the certificate expires, every visitor sees a browser security warning and the site effectively goes offline for anyone who doesn't click through warnings. Checking expiry proactively — and setting up monitoring — lets you catch these edge cases before they become outages.
In Chrome: click the padlock (or the tune icon) in the address bar → “Connection is secure” → “Certificate is valid”. The certificate detail panel shows the “Valid from” and “Valid to” dates. In Firefox: click the padlock → “Connection secure” → “More information” → “Security” tab → “View Certificate”. This method is convenient for a quick check but doesn't scale if you manage many domains.
The openssl command is the most reliable way to check a live certificate's expiry from the server or from your workstation:
If you manage multiple domains via Certbot on the same server, the certbot certificates command lists every managed certificate with its expiry date and renewal status:
Manual checks don't scale. A simple bash script run via cron can email you when any certificate on the server is within 21 days of expiry:
When SSL is managed through CloudStick, certificate expiry is monitored and renewal is triggered automatically — no cron jobs or scripts required. CloudStick attempts renewal when a certificate is within 30 days of expiry, retries on failure, and sends a dashboard notification if a renewal fails so you can investigate. The SSL status for each domain is visible in the SSL section of the website panel, showing the current expiry date and last renewal timestamp at a glance.


We use cookies to improve your experience
CloudStick uses cookies to personalise content, analyse traffic and keep you signed in. Cookie Policy · Terms of Service