This happens when you update from Chrome 55 to Chrome 56 (56.0.2924.87).This is an increase in security enforcement.It doesn't go away by restarting the browser, and it's not a bug.Mountain View says it's hoping you don't ever encounter the message,because Certificate Authorities are required to stop issuing SHA-1certificates in 2016. Just in case, Google plans to continue issuingwarnings until Chrome completely stops supporting SHA-1 on January1st, 2017. I had a similar issue recently. I was trying to access an https REST endpoint which had a self signed certificate. I was getting net::ERRINSECURERESPONSE in the Google Chrome console.
Did a bit of searching on the web to find this solution that worked for me:. Open a new tab in the same window that you are trying to make the API call. Navigate to the https URL that you are trying to access programmatically.
You should see a screen similar this:. Click on Advanced proceed to and you should see the response (if there is one).
Now try making the API call through your script. @StefanSteiger It's complicated to setup, has impact on the source code, works differently between dev/staging/prod envs. Basically, another layer of complexity. Also, let's encrypt doesn't provide certificate for IP addresses, so using a DNS routing is necessary to get a domain name. Would be even worse if it wasn't free, wouldn't like to pay for certificate in staging environment for instance.
Failed To Verify Server Certificate Macbook
I'm not complaining about let'sEncrypt, but rather about the whole complexity around certificates in general. Especially for a beginner and non sys-admin.–Dec 8 '17 at 10:58.