SSL Cert error

[ThomasErb]

Just  just implemented SSL with a wild card cert and I got an email from google that my non-www cert is not valid.

Any ideas ?

SSL/TLS certificate does not include domain name https://electrictime.com/

To: Webmaster of https://electrictime.com/,

Google has detected that the current SSL/TLS certificate used on <a>https://electrictime.com/</a>  does not include <a>https://electrictime.com/</a>  domain name. This means that your website is not perceived as secure by some browsers. As a result, many web browsers will block users accessing your site by displaying a security warning message. This is done to protect users’ browsing behavior from being intercepted by a third party, which can happen on sites that are not secure.

[crumbpeter]

I suggest to just do redirection from non www to www or http to https version. This link may be helpful for you.

[TucsonAZWebDesign]

How did you impliment it? Do you have access to Apache? if you do This is how I have about 20 of my websites SSL CRT/KEY files setup if you want something to check it with. IF you did it with php.ini probably will need to check the walkthrough with your webhost.

<virtualhost *:443=""></virtualhost>

Serveradmin some@email.com

ServerName website.com

ServerAlias www.website.com

DocumentRoot /var/www/html/website/

SSLEngine on

SSLCertificateFile "/var/key/website.com.crt"

SSLCertificateKeyFile "/var/key/website.com.key"

allow from all

Options Indexes FollowSymLinks MultiViews

Require all granted

AllowOverride All

Order allow,deny

[Nigel_Carr]

Hi Thomas

If you registered the SSL for www then it won't necessarily cover the non www. You should make sure that the version you sign up for SSL with matches the configuration you are using. If you bought an SSL for www then use www.

I have this issue with one of our sites but it is only saying this in the Opera browser.

https://stackoverflow.com/questions/40309552/do-i-need-an-ssl-certificate-for-www-and-non-www

Regards

Nigel

[Vijay-Gaur]

Hi There,

Your website is accurately redirected to the https://www version, I won't worry about the error as non-www version is not relevant in your case. You may also read the following articles why this problem might have come:

https://www.digitalocean.com/community/questions/do-i-need-to-buy-separate-ssl-certs-for-www-and-non-www

https://www.clickssl.net/blog/do-i-need-different-ssl-certificates-for-www-non-www-domain

https://www.quora.com/How-can-an-HTTPS-certificate-work-for-both-the-www-and-non-www-domains

I hope this helps, let me know if you have further queries.

Best Regards,

Vijay