Closed shanehaw closed 8 years ago
I would also assume that it has something to do with Zscaler and not an issue with the project. If you believe that it's an issue with the project still though, the bug should be reported to the main meanjs/mean repo. This is simply the generator. Good Luck and let us know if it is a bug!
Apologies if this is in the wrong place; the reason I put it here is that I get the error when running the generator.
I had a similar issue when running visual studio code - when I tried to install any extensions it also gave me the error unable to get local issuer certificate
. When I researched it further I found they provided a setting:
// Whether the proxy server certificate should be verified against the list of supplied CAs.
"http.proxyStrictSSL": true,
which, when set to false managed to reach whichever server it was trying to reach through SSL. So I suppose I was hoping that there would be an equivalent setting or parameter I could pass into the yeoman generator to also get through Zscaler.
Regardless, I understand what you are saying; I will just have to make another plan.
Thank you for your reply.
The company I work for uses a Zscaler proxy and I am trying to get the meanjs yeoman generator to work on my Windows 10 machine. So far I have managed to get npm to work by setting the proxy, https-proxy and the registry as follows:
however when I run:
yo meanjs
I get the following:
Which seems to indicate that it can't connect via https to
https://node-inspector.s3.amazonaws.com/debug/v0.7.7/node-v46-win32-ia32.tar.gz
I have tried setting up http_proxy and https_proxy environment variables, but this doesn't seem to have made a difference. I am also able to browse to that URL in a browser without an issue.
I assume the error has to do with the way Zscaler is handling https. Any help would be greatly appreciated.