Google warns me that the Certificate is not appropiate for my subdomain


#1

Google just sent me this warning today:

SSL/TLS certificate doesn’t match your subdomain comunidad.tecnogaming.com/

To: Webmaster of comunidad.tecnogaming.com/

Google has detected that the SSL/TLS certificate used on https://comunidad.tecnogaming.com/ has been issued for https://tecnogaming.com/ only and doesn’t match your subdomain’s URL. This means that your website is not currently perceived as secure by some browsers. As a result, many web browsers will block users by displaying a security warning message when your site is accessed. This is done to protect users’ browsing behavior from being intercepted by a third party, which can happen on sites that are not secure.

Recommended Action:

Get a new certificate
To correct this problem, you need to get a new dedicated SSL/TLS certificate that matches your subdomain, from a trusted Certificate Authority (CA), or a wildcard certificate that can be used for multiple subdomains on a domain.

I am SURE i marked the subdomain appropiately and the sites works with the green lock and no errors whatsoever, none of my readers are reporting any error, so this is google just complaining ? or is there something wrong?

The certs are loaded on my own server working with nginx and I just can’t find anything wrong with the configuration or the operation, its google just complaining? what should I do?


#2

Your current cert is definitely OK for comunidad.technogaming.com.

Do you know how Google found out about the site and chose to contact you? Do you know when they accessed it? Is it possible that they accessed it too early, before the certificate was installed?


#3

Thanks for your answer shoen.

No, sadly it’s not possible since I was very careful in the implementation. I switched the forum software to the new https, then implemented the certificate, then made sure the forum software was working fine on it’s new location and then tried several browsers all working perfectly.

After that I double-checked XML rules and then I proceeded to upload the site as google sugested, adding a new property. There is no way they could of get the version with no certificate.