Page 1 of 1

Problem with SSL/TLS certificate

Posted: Tue Jul 30, 2019 9:32 am
by HIINNS
I recently installed a SSL/TLS certificate on Nagios XI ver. 5.4.13 that works when I use and Internet Explorer browser. When I use Google Chrome however, I get a message stating that "Your Connection is not Private". Is there a reason for this????

Re: Problem with SSL/TLS certificate

Posted: Tue Jul 30, 2019 9:54 am
by HIINNS
The error message I get is: NET::ERR_CERT_COMMON_NAME_INVALID

Re: Problem with SSL/TLS certificate

Posted: Tue Jul 30, 2019 2:29 pm
by cdienger
The common name invalid message usually means that the hostname seen in the url does not match the common name set on the certificate. What are you putting in the address bar and what is set on the certificate if you view its properties? Also check under Admin > System Config > System Settings, for the Program URL that is set to the common name on the certificate.

Re: Problem with SSL/TLS certificate

Posted: Thu Aug 01, 2019 5:46 am
by HIINNS
The certificate works when I use the Internet Explorer browser. When I use Google Chrome I get the error I posted. I made sure that hostname in the url mateches the common name in the certificate.

Re: Problem with SSL/TLS certificate

Posted: Thu Aug 01, 2019 2:38 pm
by cdienger
Open Chrome's dev tools and look under the Security section for details on the certificate and why Chrome is not accepting it. Use the View Certificate button as well to view details of the cert. What is the common name set to in the cert? Is it using a wildcard? Are there subject alternative names?

You may be running into:

https://support.google.com/chrome/a/ans ... 1219?hl=en

Re: Problem with SSL/TLS certificate

Posted: Mon Aug 05, 2019 7:42 am
by HIINNS
I'm not sure what happened over the weekend, but for some unknown reason the certificate is now recognized by Chrome. Thank you for your assistance, and please close out the case.

Re: Problem with SSL/TLS certificate

Posted: Mon Aug 05, 2019 8:32 am
by scottwilkerson
HIINNS wrote:I'm not sure what happened over the weekend, but for some unknown reason the certificate is now recognized by Chrome. Thank you for your assistance, and please close out the case.
Great! Glad it is resolved

Locking