Error - HTTPS not secure
HTTPS not secure
When a browser makes a secure HTTPS connection to a site, the server sends a certificate of authenticity to the browser, which is necessary to validate the browser's identity. This certificate certifies that it is not a hacker attack aimed at redirecting traffic to another server. When the browser receives this certificate, it verifies the identity of the site with certification authorities. This verification is directly integrated into the browsers by a list of valid authorizations such as Symantec, VeriSign or Digicert.
When a certificate is not found or is not valid, the browser denies the access to the site in order to guarantee the security of the user. In most cases, this security is managed by the hosting provider which ensures secure access to the sites they host. Also, the loading of third party resources needed for your page can also be affected by these errors, so it is necessary to be careful with the resources used from other sites.
The most common errors are identified through codes by Google Chrome, the most common are :
- ERR_CERT_AUTHORITY_INVALID: certificate signed by an untrusted authority
- ERR_CERT_AUTHORITY_INVALID : the certificate is not valid
- ERR_CERT_CONTAINS_ERRORS: the certificate contains errors
- ERR_CERT_COMMON_NAME_INVALID: the certificate does not correspond to the site
When our robots receive instructions to not ignore this type of error, it is necessary to :
- check the access to the site from a browser
- check the validity of the certificate with your service provider