Npm install error, failed, reason: socket hang up

i am getting below errors:

"silly fetchpackagemetadata error for request to http://registry.npmjs.org/concurrently failed, reason: socket hang up"

i am behind corporate proxy. firewall is off

here is my settings:

command npm config get proxy

result: https://myproxy:8080

command: npm config get registry

result: http://registry.npmjs.org

command: npm config get key

result: true

i am getting bellow error:

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' ]

2 info using [email protected]

3 info using [email protected]

4 verbose npm-session de63d2bc21c34436

5 silly install runPreinstallTopLevelLifecycles

6 silly preinstall [email protected]

7 info lifecycle [email protected]~preinstall: [email protected]

8 silly install loadCurrentTree

9 silly install readLocalPackageData

10 silly install loadIdealTree

11 silly install cloneCurrentTreeToIdealTree

12 silly install loadShrinkwrap

13 silly install loadAllDepsIntoIdealTree

14 silly fetchPackageMetaData error for concurrently@^3.2.0 request to http://registry.npmjs.org/concurrently failed, reason: socket hang up

15 silly fetchPackageMetaData error for lite-server@^2.2.2 request to http://registry.npmjs.org/lite-server failed, reason: socket hang up

16 silly fetchPackageMetaData error for [email protected] request to http://registry.npmjs.org/canonical-path failed, reason: socket hang up

17 silly fetchPackageMetaData error for typescript@~2.1.0 request to http://registry.npmjs.org/typescript failed, reason: socket hang up

18 silly fetchPackageMetaData error for tslint@^3.15.1 request to http://registry.npmjs.org/tslint failed, reason: socket hang up

19 silly fetchPackageMetaData error for karma@^1.3.0 request to http://registry.npmjs.org/karma failed, reason: socket hang up

20 silly fetchPackageMetaData error for karma-chrome-launcher@^2.0.0 request to http://registry.npmjs.org/karma-chrome-launcher failed, reason: socket hang up

21 silly fetchPackageMetaData error for lodash@^4.16.4 request to http://registry.npmjs.org/lodash failed, reason: socket hang up

22 silly fetchPackageMetaData error for karma-cli@^1.0.1 request to http://registry.npmjs.org/karma-cli failed, reason: socket hang up

23 silly fetchPackageMetaData error for jasmine-core@~2.4.1 request to http://registry.npmjs.org/jasmine-core failed, reason: socket hang up

24 silly fetchPackageMetaData error for karma-jasmine-html-reporter@^0.2.2 request to http://registry.npmjs.org/karma-jasmine-html-reporter failed, reason: socket hang up

25 silly fetchPackageMetaData error for @types/[email protected] request to http://registry.npmjs.org/@types%2fjasmine failed, reason: socket hang up

26 silly fetchPackageMetaData error for @types/node@^6.0.46 request to http://registry.npmjs.org/@types%2fnode failed, reason: socket hang up

27 silly fetchPackageMetaData error for @angular/common@~4.3.4 request to http://registry.npmjs.org/@angular%2fcommon failed, reason: socket hang up

28 silly fetchPackageMetaData error for @angular/forms@~4.3.4 request to http://registry.npmjs.org/@angular%2fforms failed, reason: socket hang up

29 silly fetchPackageMetaData error for karma-jasmine@^1.0.2 request to http://registry.npmjs.org/karma-jasmine failed, reason: socket hang up

30 silly fetchPackageMetaData error for @angular/core@~4.3.4 request to http://registry.npmjs.org/@angular%2fcore failed, reason: socket hang up

31 silly fetchPackageMetaData error for rimraf@^2.5.4 request to http://registry.npmjs.org/rimraf failed, reason: socket hang up

32 silly fetchPackageMetaData error for @angular/compiler@~4.3.4 request to http://registry.npmjs.org/@angular%2fcompiler failed, reason: socket hang up

33 silly fetchPackageMetaData error for protractor@~4.0.14 request to http://registry.npmjs.org/protractor failed, reason: socket hang up

34 silly fetchPackageMetaData error for @angular/http@~4.3.4 request to http://registry.npmjs.org/@angular%2fhttp failed, reason: socket hang up

35 silly fetchPackageMetaData error for @angular/platform-browser@~4.3.4 request to http://registry.npmjs.org/@angular%2fplatform-browser failed, reason: socket hang up

36 silly fetchPackageMetaData error for @angular/platform-browser-dynamic@~4.3.4 request to http://registry.npmjs.org/@angular%2fplatform-browser-dynamic failed, reason: socket hang up

37 silly fetchPackageMetaData error for @angular/router@~4.3.4 request to http://registry.npmjs.org/@angular%2frouter failed, reason: socket hang up

38 silly fetchPackageMetaData error for angular-in-memory-web-api@~0.3.0 request to http://registry.npmjs.org/angular-in-memory-web-api failed, reason: socket hang up

39 silly fetchPackageMetaData error for [email protected] request to http://registry.npmjs.org/systemjs failed, reason: socket hang up

40 silly fetchPackageMetaData error for [email protected] request to http://registry.npmjs.org/rxjs failed, reason: socket hang up

41 silly fetchPackageMetaData error for core-js@^2.4.1 request to http://registry.npmjs.org/core-js failed, reason: socket hang up

42 silly fetchPackageMetaData error for zone.js@^0.8.4 request to http://registry.npmjs.org/zone.js failed, reason: socket hang up

43 silly fetchPackageMetaData error for @angular/common@~4.3.4 request to http://registry.npmjs.org/@angular%2fcommon failed, reason: socket hang up

44 silly fetchPackageMetaData error for @angular/compiler@~4.3.4 request to http://registry.npmjs.org/@angular%2fcompiler failed, reason: socket hang up

45 silly fetchPackageMetaData error for @angular/http@~4.3.4 request to http://registry.npmjs.org/@angular%2fhttp failed, reason: socket hang up

46 silly fetchPackageMetaData error for @angular/router@~4.3.4 request to http://registry.npmjs.org/@angular%2frouter failed, reason: socket hang up

47 silly fetchPackageMetaData error for @angular/forms@~4.3.4 request to http://registry.npmjs.org/@angular%2fforms failed, reason: socket hang up

48 silly fetchPackageMetaData error for @angular/platform-browser-dynamic@~4.3.4 request to http://registry.npmjs.org/@angular%2fplatform-browser-dynamic failed, reason: socket hang up

49 silly fetchPackageMetaData error for @angular/platform-browser@~4.3.4 request to http://registry.npmjs.org/@angular%2fplatform-browser failed, reason: socket hang up

50 silly fetchPackageMetaData error for @angular/core@~4.3.4 request to http://registry.npmjs.org/@angular%2fcore failed, reason: socket hang up

51 silly fetchPackageMetaData error for angular-in-memory-web-api@~0.3.0 request to http://registry.npmjs.org/angular-in-memory-web-api failed, reason: socket hang up

52 silly fetchPackageMetaData error for [email protected] request to http://registry.npmjs.org/systemjs failed, reason: socket hang up

53 silly fetchPackageMetaData error for [email protected] request to http://registry.npmjs.org/rxjs failed, reason: socket hang up

54 silly fetchPackageMetaData error for zone.js@^0.8.4 request to http://registry.npmjs.org/zone.js failed, reason: socket hang up

55 silly fetchPackageMetaData error for core-js@^2.4.1 request to http://registry.npmjs.org/core-js failed, reason: socket hang up

56 silly saveTree [email protected]

57 verbose type system

58 verbose stack FetchError: request to http://registry.npmjs.org/@angular%2fcommon failed, reason: socket hang up

58 verbose stack at ClientRequest.req.on.err (C:\Program Files\nodejs\node_modules\npm\node_modules\pacote\node_modules\make-fetch-happen\node_modules\node-fetch-npm\src\index.js:68:14)

58 verbose stack at emitOne (events.js:116:13)

58 verbose stack at ClientRequest.emit (events.js:211:7)

58 verbose stack at TLSSocket.socketErrorListener (_http_client.js:387:9)

58 verbose stack at emitOne (events.js:116:13)

58 verbose stack at TLSSocket.emit (events.js:211:7)

58 verbose stack at emitErrorNT (internal/streams/destroy.js:64:8)

58 verbose stack at _combinedTickCallback (internal/process/next_tick.js:138:11)

58 verbose stack at process._tickCallback (internal/process/next_tick.js:180:9)

59 verbose cwd D:\RNDCode\Ang2\Ang_2_2

60 verbose Windows_NT 10.0.14393

61 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"

62 verbose node v8.11.0

63 verbose npm v5.6.0

64 error code ECONNRESET

65 error errno ECONNRESET

66 error network request to http://registry.npmjs.org/@angular%2fcommon failed, reason: socket hang up

67 error network This is a problem related to network connectivity.

67 error network In most cases you are behind a proxy or have bad network settings.

67 error network

67 error network If you are behind a proxy, please make sure that the

67 error network 'proxy' config is set properly. See: 'npm help config'

68 verbose exit [ 1, true ]

if i set proxy http://myproxy:8080 "http" without "s" it show below error

npm ERR! code E407 npm ERR! 407 Proxy Authentication Required: @angular/common@~4.3.4

i am stuck in this error, not able to find solution, i did googling 2-3 days tried many setting.

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Hrides Thakur8y ago
hi @raghavendra

I have alredy tried command mentioned by you,

run npm cache clean
npm config set proxy http://[YourHost]:[YourPort]
npm config set https-proxy http://[YourHost]:[YourPort]

but no did not get resolved that issue.
thanks
0
Navneet Arora8y ago
I think there is a problem in your proxy settings...

Have you tried to fix your proxies via I.E.
-1
Raghavendar Swaminathan8y ago
Hi Thakur,

Just try below options.

update the NPM : https://github.com/npm/npm/wiki/Troubleshooting#try-the-latest-stable-version-of-npm

run npm cache clean

npm config set proxy http://[YourHost]:[YourPort]
npm config set https-proxy http://[YourHost]:[YourPort]

Thanks
Raghav
0