Skip to main content

Insecure Warning in Browser After Installing an SSL Certificate

This guide provides standardized solutions verified by Certificate Authorities (CAs) for the most common types of security alerts that occur after certificate deployment.

The browser shows an insecure warning when accessing the site after SSL certificate installation.​

There are three common causes:

Missing intermediate certificate​

Cause: The certificate chain was not imported when installing the certificate. Solution:

  1. For IIS, enter mmc to go to the console and import the pfx certificate.
  2. For other devices, use the public key and private key in the nginx folder (the intermediate certificate has already been merged).

Insecure protocols are configured in the certificate encryption protocol settings​

Solution:

IIS services​

  1. Download the server security management tool IIS Crypto to the IIS server using the button below:
  2. After decompression, double-click IISCrypto.exe directly to start the installation. Select the options as described below, then click Apply to save the settings, and then click Reboot to restart the server.

SSLDeployIssue

Nginx or Apache​

Modify the configuration file and refer to the following parameters:

  1. You need to configure cipher suites that comply with the PFS specification. Recommended configuration:
ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH:!NULL:!
 aNULL:!MD5:!ADH:!RC4:!DH:!DHE；
  1. You need to enable TLS1.2 in the TLS protocol on the server side. Recommended configuration: TLSv1 TLSv1.1 TLSv1.2；

The page references resources under http​

Open the website with chrome, and press F12. If you see a similar error prompt, it means http resources are referenced.

SSLDeployIssue

Solution: Modify the page to replace all http resources with https resources.

If none of the above solutions resolve the issue, please contact technical support for assistance.

Last updated on