ssl error behind proxy

[seanmccully]

$ npm install -g bower
npm ERR! Darwin 14.3.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "-g" "bower"
npm ERR! node v0.12.2
npm ERR! npm  v2.7.4
npm ERR! code ECONNRESET

npm ERR! network tunneling socket could not be established, cause=write EPROTO 140735156925184:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:782:
npm ERR! network
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/user/npm-debug.log

$ npm config list

; cli configs
user-agent = "npm/2.7.4 node/v0.12.2 darwin x64"

; userconfig /Users/user/.npmrc
http-proxy = "http://proxy:8888"
https-proxy = "https://proxy:8888/"
proxy = "http://proxy:8888/"

; node bin location = /usr/local/bin/node
; cwd = /Users/user
; HOME = /Users/user
; 'npm config ls -l' to show all defaults.

[thephilip]

Please try setting the registry server:
npm config set registry http://registry.npmjs.org/
npm cache clean

Does that help at all? If not, try changing it to the HTTPS registry (https://registry.npmjs.org/).

[tmen]

Try to set
npm config set https_proxy

[npm-robot]

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining package.community and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

[abhi19gupta]

Somehow, it worked for me when I set the the value for https_proxy to be the same as that of http_proxy i.e. the one with "http://...". Strange but worked.

Command: npm config set https-proxy http://<proxy_server>:<port>

[robertojsh]

@abhi19gupta setting http proxy on https proxy setting worked for me too. Thanks!