Category: SSL & HTTPS
Chrome and Firefox ending support for legacy Symantec certificates
Chrome and Firefox ending support for legacy Symantec certificates From Google Chrome version 66 and Firefox 60 onwards, support for legacy Symantec certificates (certificates issued before 1 June 2016) will be suspended due to a number of issues. If your site uses one of these certificates this will result in the site not having the green lock and a warning being shown to your visitors. This affects certificates from the following providers as well, as they are (former) sub-companies/partners of Symantec:
htaccess redirect to https may cause redirect to 401.shtml when using password protection
When using the .htaccess for password protection in combination with the .htaccess 301 redirect to https in Really Simple SSL, a redirect to https://domain.com/401.shtml might occur. A simple solution that has been reported to work is to add ErrorDocument 401 default To the top of your .htaccess, so the end result looks like this (the error document should come before the password lines): # Error Document ErrorDocument 401 default #password protection AuthType Basic AuthName “YOUR AUTH NAME” AuthUserFile “/path/to/file” require
ERR_SSL_PROTOCOL_ERROR
err_ssl_protocol_error The err_ssl_protocol_error is usually caused by a failure to securely communicate with the server and often has to do with the server configuration. For any SSL related error, there are a number of steps to finding the cause of the issue. The first step is clearing your browser’s cache. If that doesn’t help, the next step is to try reproducing it in another browser or on another device. Does the error occur only in one specific browser? Then it’s
SSL_ERROR_BAD_CERT_DOMAIN
ssl_error_bad_cert_domain The ssl_error_bad_cert_domain error is shown when the domain name on the certificate doesn’t match the domain of your site. A lot of hosting providers will have a default SSL certificate installed using their own domain. This error occurs when visiting a site that doesn’t have its own certificate installed. To test this, you can do a test over at the Qualys SSL Labs to check your certificate. If the domain name does not match, the SSL Labs test will
ERR_SSL_UNRECOGNIZED_NAME_ALERT
err_ssl_unrecognized_name_alert This error means that the name on the certificate is not recognized and is usually caused by a SSL configuration error. The first thing to do is to check for any errors in your certificate using the Qualys SSL Labs scan. If there are any issues with your certificate, the scan will let you know. Do you see any error messages? Then it’s likely that the error is related to your certificate configuration, contact your hosting or certificate provider