npm install error: socket hang up

[nasser-torabzade]

Salam (means Hello) :)

When I'm trying to install a package (in this case: urlparse) using npm install, installation process fails and this error log is generated:

can you identify the source of this error?

npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'install',
1 verbose cli   'urlparse' ]
2 info using npm@1.3.14
3 info using node@v0.10.22
4 verbose node symlink C:\Program Files\nodejs\\node.exe
5 warn package.json jsdom@0.5.5 'repositories' (plural) Not supported.
5 warn package.json Please pick one as the 'repository' field
6 warn package.json querystring@0.2.0 querystring is also the name of a node core module.
7 verbose cache add [ 'urlparse', null ]
8 verbose cache add name=undefined spec="urlparse" args=["urlparse",null]
9 verbose parsed url { protocol: null,
9 verbose parsed url   slashes: null,
9 verbose parsed url   auth: null,
9 verbose parsed url   host: null,
9 verbose parsed url   port: null,
9 verbose parsed url   hostname: null,
9 verbose parsed url   hash: null,
9 verbose parsed url   search: null,
9 verbose parsed url   query: null,
9 verbose parsed url   pathname: 'urlparse',
9 verbose parsed url   path: 'urlparse',
9 verbose parsed url   href: 'urlparse' }
10 silly lockFile e07a1222-urlparse urlparse
11 verbose lock urlparse C:\Users\Nasser\AppData\Roaming\npm-cache\e07a1222-urlparse.lock
12 silly lockFile e07a1222-urlparse urlparse
13 silly lockFile e07a1222-urlparse urlparse
14 verbose addNamed [ 'urlparse', '' ]
15 verbose addNamed [ null, '*' ]
16 silly lockFile 251047af-urlparse urlparse@
17 verbose lock urlparse@ C:\Users\Nasser\AppData\Roaming\npm-cache\251047af-urlparse.lock
18 silly addNameRange { name: 'urlparse', range: '*', hasData: false }
19 verbose url raw urlparse
20 verbose url resolving [ 'https://registry.npmjs.org/', './urlparse' ]
21 verbose url resolved https://registry.npmjs.org/urlparse
22 info trying registry request attempt 1 at 15:59:54
23 http GET https://registry.npmjs.org/urlparse
24 info retry will retry, error on last attempt: Error: socket hang up
25 info trying registry request attempt 2 at 16:00:08
26 http GET https://registry.npmjs.org/urlparse
27 info retry will retry, error on last attempt: Error: socket hang up
28 info trying registry request attempt 3 at 16:01:10
29 http GET https://registry.npmjs.org/urlparse
30 silly lockFile 251047af-urlparse urlparse@
31 silly lockFile 251047af-urlparse urlparse@
32 error network socket hang up
32 error network This is most likely not a problem with npm itself
32 error network and is related to network connectivity.
32 error network In most cases you are behind a proxy or have bad network settings.
32 error network
32 error network If you are behind a proxy, please make sure that the
32 error network 'proxy' config is set properly.  See: 'npm help config'
33 error System Windows_NT 6.1.7601
34 error command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "urlparse"
35 error cwd D:\Projects\server v3
36 error node -v v0.10.22
37 error npm -v 1.3.14
38 error code ECONNRESET
39 verbose exit [ 1, true ]

[robertkowalski]

Hi,

are you behind a corporate proxy or something like that? the error is network related:

32 error network socket hang up
32 error network This is most likely not a problem with npm itself
32 error network and is related to network connectivity.
32 error network In most cases you are behind a proxy or have bad network settings.

[bbohling]

npm installs started failing for me as well...and yes I am behind a corporate firewall. in the past, i never had any issues but after i updated npm i can no longer use it behind a proxy server. I have tried all the techniques mentioned here as well: http://wil.boayue.com/blog/2013/06/14/using-npm-behind-a-proxy/

[nasser-torabzade]

@robertkowalski Hi,

No, I'm not behind any proxies, and my network settings are intact since the last time when npm install was working properly. any other idea?

[robertkowalski]

@nasser-torabzade do you still have the issue? did you check your windows networks settings? does it work on another internet connection / pc for you?

[robertkowalski]

@bbohling do you still have the issue?

[othiym23]

Closing as abandoned. Please install the latest stable version of npm and this problem should go away, if you're still encountering it.