Created 12-06-2016 04:03 AM
Hi!
I created cluster and tried to access to Ambari Web. However, I got an error "NET::ERR_CERT_INVALID" in IE, Firefox and chrome.
This issue has occurred with only Windows OS. Using Mac, I could access to Ambari Web successfully with the error "NET::ERR_CERT_AUTHORITY_INVALID" in chrome.
I cannot find the documents for the issue.
I need to access to Ambari Web using Windows PC.
Could you please tell me what is the cause and how to resolve that?
Created 01-05-2017 03:52 PM
FYI I solved my NET::ERR_CERT_INVALID problem by using Firefox 46 on windows 7.
I think the issue is that the cluster uses sha1 certificates, and windows recently removed support for them. Browsers that use the windows OS for certificate handling think these certificates are corrupted now. I'm guessing that Firefox does its own certificate handling
Created 12-06-2016 04:09 AM
Looks like you have setup HTTPs for ambari. in standard JKS format.
The ssl_keystore and ssl_truststore are standard JKS format key and trust store files. You can replace the content of these files with what you want. Just generate a cert and private key and put that in the keystore and put the signer in the truststore.
Please see: https://www.youtube.com/watch?v=O5l0FuAfCK4 to (How to fix NET::ERR_CERT_AUTHORITY_INVALID error) understand more about NET::ERR_CERT_INVALID
Created 12-06-2016 04:21 AM
Thank you!
I cannot find the documents about that. I have no idea about the procedure. Do you know whether there is the document?
I don't know why I can access to Ambari using Mac...
Created 12-30-2016 07:03 PM
I have exactly the same NET::ERR_CERT_INVALID problem (cannot access Ambari on Windows 7) .
Are the AWS marketplace stacks meant to work 'out of the box'?
Created 12-31-2016 03:27 AM
Try this
Created 01-05-2017 03:52 PM
FYI I solved my NET::ERR_CERT_INVALID problem by using Firefox 46 on windows 7.
I think the issue is that the cluster uses sha1 certificates, and windows recently removed support for them. Browsers that use the windows OS for certificate handling think these certificates are corrupted now. I'm guessing that Firefox does its own certificate handling
Created 01-11-2017 12:32 AM
Thank you! This issue was gone using the newest Firefox on Windows 10. Using IE or Chrome, the issue is still exist.