Today we're announcing the availability of Cachet v2.3.0! v2.3.0 fixes a major pain point for a lot of installations, the Subscriber's system. Joe has rewritten the majority, ridding the system of the notorious issues that many of you have faced.
SSLping was born as a side project. It’s useful to people, which is cool, but today it was also helpful to me! I use it to monitor my HTTPS websites. This morning, my own SSLping project sent me an email about how my website https://hire.chris-hartwig.com is about to expire (in 10 days): it’s using Letsencrypt, and it’s been 80 days since I installed the cert.
TL;DR you’re never done with Let’s encrypt: once your servers are secure, you must ensure they stay that way. Let’s encrypt is a no brainer: this initiative benefits us all, with free domain-validated certificates. It’s easy to setup and free. There’s probably automatic installation for your web server of choice, the community behind it can help, and tutorials are everywhere. Then you head to https://
The best way for organizations to handle these kinds of situations is with complete transparency. This can easily be achieved by setting up a status page that reflects your service's operational status. You can set up this status page to display uptime metric graphs, any recent incidents, what is being done to resolve them, and an incident history.