Author: Mark
Deprecation of TLS 1.0 and 1.1
Deprecation of TLS 1.0 and 1.1 Since Chrome 79, a ‘not secure’ warning is shown for sites that use TLS 1.0 or 1.1 and do not support TLS 1.2 or greater. From Chrome 84 onwards (scheduled for release on the 4th of August) the site will become inaccessible if it doesn’t support TLS 1.2 at a minimum. Any sites which don’t support TLS 1.2 from the 4th of August onwards will display a full-page warning. What is TLS? TLS is
How to renew your Really Simple Security Pro license
How to renew your Really Simple SSL Pro license There are multiple ways to renew your Really Simple SSL Pro license. Really Simple SSL Pro is a subscription that will renew automatically. But sometimes the subscription will not automatically renew, this can be caused by a number of reasons. Renewal payment failed Usually when the renewal payment failed there’s an issue with your card. For example, a new card has been issued or your old card has expired. To fix
Common issues with HSTS
There are several causes for HTTP Strict Transport Security (HSTS) not working correctly. The most common HSTS issues are listed in this article. Response error: Multiple HSTS headers (number of HSTS headers: 2) When you see this error the HSTS header has been set twice. The HSTS header should be set only once. This is usually caused by a second HSTS header, added by either your hosting provider or a different plugin. This header is often located in the .htaccess file. Check your
Updating your payment method / renewal failing
You can update your payment method via your account page. The process of doing this slightly differs depending on if you are switching from PayPal or Credit Card. Please note: Your renewal price is linked to your auto-renewal subscription. If we would ever increase the price for your purchased license type, it will not affect your subscription as long as auto-renewal is kept enabled. Whenever you cancel your subscription, any renewals will revert to the current pricing scheme. You can find your
Google Chrome will start blocking mixed content soon
Google previously announced that it would block mixed content by default from Chrome 79 onwards (released December 2019), and that further changes to handling mixed content would be made in subsequent releases. With the release of Chrome 80 (released February 2020), mixed audio and video resources are now automatically being upgraded to https://. Mixed content images would still load, but would display a ‘not secure’ warning in the address bar. Finally, with the introduction of Chrome 81, mixed image resources