The spottyness was caused moviing the site to a new faster. The move went well over the weekend but while securing the site for SSL, there were some verification issues.
In case you weren’t aware it, the heartbleed bug that caused such a stir, did not effect Windows Servers. SSL is the best way to secure a site with encrypted data.
The OpenSSL Heartbleed Bug: What It Means To You
The recent discovery of what’s known as the ‘Heartbleed’ Bug in OpenSSL has caused great concern in the industry and you’ve no doubt heard about it by now. But what does it mean for you? Below are the simple steps you can take to resolve this issue. We advise you to complete these steps as soon as possible. Also, if you would like more information about the Heartbleed Bug, you can find that below as well.
Heartbleed Resolution for Comodo
- Step 1: To determine if you are vulnerable due to the Heartbleed bug, enter your domain name on https://www.ssllabs.com/ssltest/index.html. If your site is in the clear, then no action is needed. However, if it is determined that your site is vulnerable, immediate action is advised and you should proceed to step 2.
- Step 2: Install the updated version of OpenSSL on your server. You can find this version right here: https://rhn.redhat.com/errata/RHSA-2014-0376.html. You can also read OpenSSL’s security advisory here: https://www.openssl.org/news/secadv_20140407.txt.
Read More about Certificates and the Heartbleed here.