Even after installing an SSL certificate in ADManager Plus, your browser might still display a “Not secure” message or a certificate warning when you access the console via HTTPS. This article walks you through why this happens and how to resolve it.
An untrusted certificate authority (CA): The browser doesn’t recognize or trust the CA that issued the SSL certificate.
An incomplete certificate chain: Intermediate or root certificates are missing from the installation.
Access via HTTP: You may still be using an unsecured HTTP URL instead of HTTPS.
A valid SSL certificate (issued by a trusted CA or internal CA)
Admin access to the ADManager Plus server
Access to the keystore used for certificate importing
Ensure the certificate is installed in the correct location:
Open the server.xml file located under ADManager Plus\conf\.
Verify that the correct keystore file and password are referenced.
Use tools like SSL Labs, SSL Checker, or OpenSSL to validate the certificate chain.
Always access ADManager Plus using the exact hostname or fully qualified domain name (FQDN) listed in the certificate’s CN or SAN.
Avoid using localhost or the server’s IP address in the browser.
Download the complete certificate chain from your CA.
Import the root and intermediate certificates into the Java KeyStore or your browser’s trust store.
After making SSL-related changes, restart ADManager Plus using the Start console to apply the updates.
For external access, use certificates issued by a public CA for broad trust compatibility.
If using an internal CA, ensure the root certificate is trusted on all client machines.
Always access the product via https://your-fqdn:port to avoid warnings.
Keep SSL certificates renewed and updated before expiration.
If the issue persists, contact our support team here.