Proxy error: unable to get local issuer certificate

[joaomoreno]

From @dogfish182

unable to get local issuer certificate

[joaomoreno]

Related to nodejs/node#3742

[dogfish182]

I'm not sure how to address this for myself as I have a standard install of win10 without any node stuff that i knowingly installed... also the issue presents on a fresh windows 7 corporate image that we don't use for development, so a basic install of win 7 for us (and 10 and 8.1) will all exhibit the same issue.

[colhountech]

This worked for me:
start a command prompt and navigate to working folder.

set NODE_TLS_REJECT_UNAUTHORIZED=0
code .

from http://stackoverflow.com/questions/33820733/error-unable-to-verify-the-first-certificate-how-to-trust-all-certificates

[joaomoreno]

@colhountech Does it work if you set "http.proxyStrictSSL": false in your settings?

[wgknowles]

// Whether the proxy server certificate should be verified against the list of supplied CAs.
This leads me to think there should be a way to add a CA to the "list of supplied CAs". Ideally, there should be a setting like http.useMachineCAStore that taps into the trusted root CA list of the system (same one used by IE)

Doesn't setting "http.proxyStrictSSL": false result in all CA's and self-signed certs being trusted? Seems like we are asking for a MITM hack.

[psmoot]

I'm having the same issue on Ubuntu 16 behind a firewall. Setting NODE_TLS_REJECT_UNAUTHORIZED worked but setting http.proxyStrictSSL did not.

I'm happy to try new builds if that will help resolving the issue, just let me know.

[joaomoreno]

@psmoot #11702 Fix is out in 1.5.2.

@wgknowles Unfortunately we didn't dedicate time to look into the CA list yet.

Closing this as it seems a duplicate of #11702.