Last week, we improved the email notifications sent by Oh Dear whenever something is down or broken. They now contain links that allow you to snooze further emails, essentially "silencing" the alert for a defined period of time.
As part of our SSL certificate monitoring, we check a lot of things. The usuals, like if it covers the right domain name or if it hasn't expired are, of course, already included. But SSL certificates can get quite complex. Sometimes, SSL certificates get revoked by the issuer. When that happens, browsers worldwide stop trusting them and will throw an invalid certificate warning.
We're excited to announce all Oh Dear users now have access to detailed performance metrics for all of their websites! Let us take you through a quick tour of the new performance monitoring.
Some of our users have received reports about their AddTrust External CA Root or USERTrust RSA Certification Authority certificate. The problem occurs because the remote server sends a root certificate in the chain that will expire in less than 14 days. Here are the steps to verify this and a few tips on how to resolve it.
As part of our service, we perform SSL certificate monitoring. We do this slightly different than other providers, which is why were able to detect a problem with the SSL certificates of a large, commercial, CDN provider. In this post, we'll do a technical deep-dive into how we found this problem!
We've introduced two very cool new features to Oh Dear: the ability to temporarily silence alerts and advanced Slack notifications.
We've added the ability to see detailed webhook logs to Oh Dear, showing both the sent request and the received response for all notifications we have sent.
We've added the ability to disable the team-level notification settings on a per-site basis. This allows for even more flexibility in the way you set up and configure your alerts!
When we first launched Oh Dear, we had a fixed certificate expiration timer: 14 days. As soon as the expiration date came within 14 days, we'd start sending a daily reminder to hurry up and renew those certificates. Our first exception was made when Let's Encrypt gained more in popularity. We started notifying Let's Encrypt certificates 7 days before expiration date.
We added a series of improvements to our notifications settings, making it easier for you to control where your alerts are sent.
