-
Notifications
You must be signed in to change notification settings - Fork 125
npm installer fails on proxy and certificates #228
Comments
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it! Here is what to expect next, and if anyone wants to comment, keep these things in mind. |
This worked for me |
JordyMoos suggestion of using NODE_TLS_REJECT_UNAUTHORISED="0" works fine but a) it seems like more of a work-around than a fix and b) I couldn't find it on the npmjs.com page for Elm. I'm concerned it will put off people less obsessive than me! ;-) |
We need a way to work around a corporate firewall as well. If there were a way to provide a custom binary host URL, that would be great for us. Otherwise, we'll have to hack a bunch of other packages that require a elm as an NPM dependency. |
The system has all the necessary certs installed to allow things to work with our Corporate MITM proxy here, but for some reason, this operation does not use those certificates, and so I also had to disable the TLS verification :( The right solution is to fix the install.js so it honors system certificates. |
When I attempt to use the npm installer for Elm (on CentOS7):
npm install -g elm
(as per https://www.npmjs.com/package/elm)
I get the following error:
I have attached the npm-debug-log file:
npm-debug.log
One of my colleagues suggested this workaround:
and that was successful. He had a look at the issue and suggest that cause might be this:
My colleague believes the workaround is successful because wget will honor the https_proxy / HTTPS_PROXY environment variable
The text was updated successfully, but these errors were encountered: