Node V5 has issues with installing behind proxies

[Wyatt Biker]

I am behind corporate proxy. I ve tried everything under the sun with flags and configs. (yes i set up the --proxy and --https-proxy).  I reverted back to 0.12 and everything works fine. 

Any ideas?

Here is the message:

Enter node package to install: ws

Enter -g for global install:

> bufferutil@1.1.0 install /mnt/mydir/mytest/node_modules/bufferutil
> node-gyp rebuild


gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: unable to verify the first certificate
gyp ERR! stack     at Error (native)
gyp ERR! stack     at TLSSocket.<anonymous> (_tls_wrap.js:1057:38)
gyp ERR! stack     at emitNone (events.js:67:13)
gyp ERR! stack     at TLSSocket.emit (events.js:166:7)
gyp ERR! stack     at TLSSocket._finishInit (_tls_wrap.js:596:8)
gyp ERR! System Linux 2.6.32-573.1.1.el6.x86_64
gyp ERR! command "/mnt/node/bin/node" "/mnt/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /mnt/mydir/mytest/node_modules/bufferutil
gyp ERR! node -v v5.1.0
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
npm WARN install:bufferutil@1.1.0 bufferutil@1.1.0 install: `node-gyp rebuild`
npm WARN install:bufferutil@1.1.0 Exit status 1

[Ben Noordhuis]

On Mon, Nov 30, 2015 at 6:42 PM, Wyatt Biker <wyatt...@gmail.com> wrote:
> I am behind corporate proxy. I ve tried everything under the sun with flags
> and configs. (yes i set up the --proxy and --https-proxy). I reverted back
> to 0.12 and everything works fine.
>
> Any ideas?
>
> Here is the message:
> Enter node package to install: ws
> Enter -g for global install:
>

>> buffe...@1.1.0 install /mnt/mydir/mytest/node_modules/bufferutil

>> node-gyp rebuild
>
>
> gyp WARN install got an error, rolling back install
> gyp ERR! configure error
> gyp ERR! stack Error: unable to verify the first certificate
> gyp ERR! stack at Error (native)
> gyp ERR! stack at TLSSocket.<anonymous> (_tls_wrap.js:1057:38)
> gyp ERR! stack at emitNone (events.js:67:13)
> gyp ERR! stack at TLSSocket.emit (events.js:166:7)
> gyp ERR! stack at TLSSocket._finishInit (_tls_wrap.js:596:8)
> gyp ERR! System Linux 2.6.32-573.1.1.el6.x86_64
> gyp ERR! command "/mnt/node/bin/node"
> "/mnt/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js"
> "rebuild"
> gyp ERR! cwd /mnt/mydir/mytest/node_modules/bufferutil
> gyp ERR! node -v v5.1.0
> gyp ERR! node-gyp -v v3.0.3
> gyp ERR! not ok

> npm WARN install:buffe...@1.1.0 buffe...@1.1.0 install: `node-gyp
> rebuild`
> npm WARN install:buffe...@1.1.0 Exit status 1

node-gyp is telling you that the TLS certificate doesn't check out.
If your proxy uses a self-signed certificate, try setting
NODE_TLS_REJECT_UNAUTHORIZED=0 in the environment.

Alternatively, and more securely, you can download the source tarball
manually from https://nodejs.org/dist/v5.1.0/node-v5.1.0-headers.tar.gz
and extract it to $HOME/.node-gyp/5.1.0. Pass --strip-components=1 to
tar to remove the node-v5.1.0/ directory prefix from the files in the
tarball.

You can find GPG-signed SHA256 checksums in
https://nodejs.org/dist/v5.1.0/SHASUMS256.txt.asc to verify the
tarball after downloading.

[Peter Rust]

Any idea why 0.12 would behave differently?

[Ben Noordhuis]

On Tue, Dec 1, 2015 at 5:28 PM, Peter Rust <pe...@cornerstonenw.com> wrote:
> Any idea why 0.12 would behave differently?

It's possible the proxy uses a certificate that's signed by a CA
that's accepted by v0.12 but not by v4.x or v5.x.

[Wyatt Biker]

I also had tried NODE_TLS_REJECT_UNAUTHORIZED=0 but to no avail. Would you be able to give me the exact steps for the source?

 After I remove node-v5.1.0/ , what do I do?