npm -g install.... ETIMEDOUT This is a problem related to network connectivity.


(Bkarv) #1

What I Wanted to Do

Running
npm install -g ionic --verbose

OR

npm install -g @angular/cli --verbose

I am getting a FetchError: request to https://registry.npmjs.org/

I am running MacOs and checked if I am behind proxy server which I am pretty sure I am not. I also tried this on another computer and getting similar results.

I tried restarting my internet + I did an internet speed check where I am getting 32 Mbps downloa. Also I am able to install smaller npm’s eg ngx-mat-select-search as well as run npm install on my ionic/angular project.

Has anyone else experienced this issue?

What Happened Instead

Details

Error Log for Ionic below (unable to attach due to status)

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'install',
1 verbose cli   '-g',
1 verbose cli   'ionic',
1 verbose cli   '--verbose' ]
2 info using npm@6.5.0
3 info using node@v10.13.0
4 verbose npm-session 8c6c5725fdfdec2d
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/ionic 183ms (from cache)
8 silly pacote tag manifest for ionic@latest fetched in 204ms
9 timing stage:loadCurrentTree Completed in 298ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 2ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule ionic@4.6.0 checking installable status
17 http fetch GET 200 https://registry.npmjs.org/elementtree 43ms
18 silly pacote range manifest for elementtree@^0.1.7 fetched in 47ms
19 silly resolveWithNewModule elementtree@0.1.7 checking installable status
20 http fetch GET 304 https://registry.npmjs.org/log-update 29ms (from cache)
21 silly pacote range manifest for log-update@^2.3.0 fetched in 30ms
22 silly resolveWithNewModule log-update@2.3.0 checking installable status
23 http fetch GET 304 https://registry.npmjs.org/leek 104ms (from cache)
24 silly pacote version manifest for leek@0.0.24 fetched in 105ms
25 silly resolveWithNewModule leek@0.0.24 checking installable status
26 http fetch GET 304 https://registry.npmjs.org/opn 31ms (from cache)
27 silly pacote range manifest for opn@^5.2.0 fetched in 32ms
28 silly resolveWithNewModule opn@5.4.0 checking installable status
29 http fetch GET 304 https://registry.npmjs.org/debug 129ms (from cache)
30 silly pacote range manifest for debug@^4.0.0 fetched in 131ms
31 silly resolveWithNewModule debug@4.1.1 checking installable status
32 http fetch GET 304 https://registry.npmjs.org/os-name 34ms (from cache)
33 silly pacote range manifest for os-name@^3.0.0 fetched in 35ms
34 silly resolveWithNewModule os-name@3.0.0 checking installable status
35 http fetch GET 304 https://registry.npmjs.org/semver 38ms (from cache)
36 silly pacote range manifest for semver@^5.5.0 fetched in 41ms
37 silly resolveWithNewModule semver@5.6.0 checking installable status
38 http fetch GET 304 https://registry.npmjs.org/split2 41ms (from cache)
39 silly pacote range manifest for split2@^3.0.0 fetched in 42ms
40 silly resolveWithNewModule split2@3.1.0 checking installable status
41 http fetch GET 304 https://registry.npmjs.org/ssh-config 37ms (from cache)
42 silly pacote range manifest for ssh-config@^1.1.1 fetched in 38ms
43 silly resolveWithNewModule ssh-config@1.1.5 checking installable status
44 http fetch GET 304 https://registry.npmjs.org/superagent 34ms (from cache)
45 silly pacote range manifest for superagent@^3.8.2 fetched in 36ms
46 silly resolveWithNewModule superagent@3.8.3 checking installable status
47 http fetch GET 304 https://registry.npmjs.org/@ionic%2futils-fs 201ms (from cache)
48 silly pacote version manifest for @ionic/utils-fs@0.0.6 fetched in 202ms
49 silly resolveWithNewModule @ionic/utils-fs@0.0.6 checking installable status
50 http fetch GET 304 https://registry.npmjs.org/superagent-proxy 34ms (from cache)
51 silly pacote range manifest for superagent-proxy@^2.0.0 fetched in 35ms
52 silly resolveWithNewModule superagent-proxy@2.0.0 checking installable status
53 http fetch GET 304 https://registry.npmjs.org/tar 34ms (from cache)
54 silly pacote range manifest for tar@^4.3.0 fetched in 35ms
55 silly resolveWithNewModule tar@4.4.8 checking installable status
56 http fetch GET 304 https://registry.npmjs.org/through2 32ms (from cache)
57 silly pacote range manifest for through2@^3.0.0 fetched in 34ms
58 silly resolveWithNewModule through2@3.0.0 checking installable status
59 http fetch GET 304 https://registry.npmjs.org/tslib 31ms (from cache)
60 silly pacote range manifest for tslib@^1.9.0 fetched in 32ms
61 silly resolveWithNewModule tslib@1.9.3 checking installable status
62 http fetch GET 304 https://registry.npmjs.org/update-notifier 32ms (from cache)
63 silly pacote range manifest for update-notifier@^2.3.0 fetched in 34ms
64 silly resolveWithNewModule update-notifier@2.5.0 checking installable status
65 http fetch GET 304 https://registry.npmjs.org/uuid 38ms (from cache)
66 silly pacote range manifest for uuid@^3.2.1 fetched in 41ms
67 silly resolveWithNewModule uuid@3.3.2 checking installable status
68 http fetch GET 304 https://registry.npmjs.org/@ionic%2fdiscover 961ms (from cache)
69 silly pacote version manifest for @ionic/discover@1.0.9 fetched in 963ms
70 silly resolveWithNewModule @ionic/discover@1.0.9 checking installable status
71 http fetch GET 304 https://registry.npmjs.org/chalk 86341ms attempt #2 (from cache)
72 silly pacote range manifest for chalk@^2.3.0 fetched in 86342ms
73 silly resolveWithNewModule chalk@2.4.1 checking installable status
74 http fetch GET 304 https://registry.npmjs.org/diff 86347ms attempt #2 (from cache)
75 silly pacote range manifest for diff@^3.4.0 fetched in 86350ms
76 silly resolveWithNewModule diff@3.5.0 checking installable status
77 http fetch GET 304 https://registry.npmjs.org/@ionic%2futils-network 87206ms attempt #2 (from cache)
78 silly pacote version manifest for @ionic/utils-network@0.0.5 fetched in 87207ms
79 silly resolveWithNewModule @ionic/utils-network@0.0.5 checking installable status
80 http fetch GET 304 https://registry.npmjs.org/@ionic%2fcli-framework 223033ms attempt #3 (from cache)
81 silly pacote version manifest for @ionic/cli-framework@1.5.1 fetched in 223035ms
82 silly resolveWithNewModule @ionic/cli-framework@1.5.1 checking installable status
83 warn registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning ETIMEDOUT: request to https://registry.npmjs.org/lodash failed, reason: connect ETIMEDOUT 104.16.18.35:443
84 warn registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
85 http fetch GET 200 https://registry.npmjs.org/lodash 297351ms attempt #2 (from cache)
86 silly pacote range manifest for lodash@^4.17.5 fetched in 297352ms
87 silly resolveWithNewModule lodash@4.17.11 checking installable status
88 http fetch GET 200 https://registry.npmjs.org/rimraf 97ms
89 http fetch GET 200 https://registry.npmjs.org/stream-combiner2 104ms
90 http fetch GET 200 https://registry.npmjs.org/wrap-ansi 105ms
91 http fetch GET 200 https://registry.npmjs.org/minimist 111ms
92 silly pacote range manifest for stream-combiner2@^1.1.1 fetched in 112ms
93 silly resolveWithNewModule stream-combiner2@1.1.1 checking installable status
94 silly pacote range manifest for wrap-ansi@^4.0.0 fetched in 113ms
95 silly resolveWithNewModule wrap-ansi@4.0.0 checking installable status
96 http fetch GET 200 https://registry.npmjs.org/tree-kill 116ms
97 silly pacote version manifest for tree-kill@1.2.1 fetched in 118ms
98 silly resolveWithNewModule tree-kill@1.2.1 checking installable status
99 http fetch GET 200 https://registry.npmjs.org/rimraf/-/rimraf-2.6.2.tgz 31ms
100 silly pacote range manifest for rimraf@^2.6.2 fetched in 133ms
101 silly resolveWithNewModule rimraf@2.6.2 checking installable status
102 http fetch GET 200 https://registry.npmjs.org/write-file-atomic 34ms
103 http fetch GET 200 https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz 39ms
104 silly pacote range manifest for minimist@^1.2.0 fetched in 153ms
105 silly resolveWithNewModule minimist@1.2.0 checking installable status
106 silly pacote range manifest for write-file-atomic@^2.3.0 fetched in 38ms
107 silly resolveWithNewModule write-file-atomic@2.3.0 checking installable status
108 http fetch GET 200 https://registry.npmjs.org/string-width 85308ms attempt #2
109 silly pacote range manifest for string-width@^3.0.0 fetched in 85310ms
110 silly resolveWithNewModule string-width@3.0.0 checking installable status
111 http fetch GET 200 https://registry.npmjs.org/inquirer 85329ms attempt #2
112 silly pacote range manifest for inquirer@^6.0.0 fetched in 85333ms
113 silly resolveWithNewModule inquirer@6.2.1 checking installable status
114 http fetch GET 200 https://registry.npmjs.org/slice-ansi 220478ms attempt #3
115 silly pacote range manifest for slice-ansi@^2.0.0 fetched in 220480ms
116 silly resolveWithNewModule slice-ansi@2.0.0 checking installable status
117 http fetch GET 200 https://registry.npmjs.org/untildify 220489ms attempt #3
118 silly pacote range manifest for untildify@^3.0.2 fetched in 220491ms
119 silly resolveWithNewModule untildify@3.0.3 checking installable status
120 silly fetchPackageMetaData error for strip-ansi@^5.0.0 request to https://registry.npmjs.org/strip-ansi failed, reason: connect ETIMEDOUT 104.16.17.35:443
121 timing stage:rollbackFailedOptional Completed in 0ms
122 timing stage:runTopLevelLifecycles Completed in 593356ms
123 verbose type system
124 verbose stack FetchError: request to https://registry.npmjs.org/strip-ansi failed, reason: connect ETIMEDOUT 104.16.17.35:443
124 verbose stack     at ClientRequest.req.on.err (/usr/local/lib/node_modules/npm/node_modules/node-fetch-npm/src/index.js:68:14)
124 verbose stack     at ClientRequest.emit (events.js:182:13)
124 verbose stack     at TLSSocket.socketErrorListener (_http_client.js:391:9)
124 verbose stack     at TLSSocket.emit (events.js:182:13)
124 verbose stack     at emitErrorNT (internal/streams/destroy.js:82:8)
124 verbose stack     at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
124 verbose stack     at process._tickCallback (internal/process/next_tick.js:63:19)
125 verbose cwd /Users/karvanj/www/ourmgmt-client
126 verbose Darwin 18.0.0
127 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "ionic" "--verbose"
128 verbose node v10.13.0
129 verbose npm  v6.5.0
130 error code ETIMEDOUT
131 error errno ETIMEDOUT
132 error network request to https://registry.npmjs.org/strip-ansi failed, reason: connect ETIMEDOUT 104.16.17.35:443
133 error network This is a problem related to network connectivity.
133 error network In most cases you are behind a proxy or have bad network settings.
133 error network
133 error network If you are behind a proxy, please make sure that the
133 error network 'proxy' config is set properly.  See: 'npm help config'
134 verbose exit [ 1, true ]

Error Log for Angular/cli

    0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'install',
1 verbose cli   '-g',
1 verbose cli   '@angular/cli',
1 verbose cli   '--verbose' ]
2 info using npm@6.5.0
3 info using node@v10.13.0
4 verbose npm-session 40f86da8a0e39060
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/@angular%2fcli 134ms (from cache)
8 silly pacote tag manifest for @angular/cli@latest fetched in 150ms
9 timing stage:loadCurrentTree Completed in 248ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 2ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule @angular/cli@7.1.4 checking installable status
17 http fetch GET 200 https://registry.npmjs.org/semver 21ms (from cache)
18 silly pacote version manifest for semver@5.5.1 fetched in 24ms
19 silly resolveWithNewModule semver@5.5.1 checking installable status
20 http fetch GET 304 https://registry.npmjs.org/inquirer 84ms (from cache)
21 silly pacote version manifest for inquirer@6.2.0 fetched in 86ms
22 silly resolveWithNewModule inquirer@6.2.0 checking installable status
23 http fetch GET 304 https://registry.npmjs.org/@angular-devkit%2fschematics 335ms (from cache)
24 silly pacote version manifest for @angular-devkit/schematics@7.1.4 fetched in 340ms
25 silly resolveWithNewModule @angular-devkit/schematics@7.1.4 checking installable status
26 http fetch GET 304 https://registry.npmjs.org/@schematics%2fangular 352ms (from cache)
27 silly pacote version manifest for @schematics/angular@7.1.4 fetched in 354ms
28 silly resolveWithNewModule @schematics/angular@7.1.4 checking installable status
29 http fetch GET 304 https://registry.npmjs.org/@angular-devkit%2farchitect 422ms (from cache)
30 silly pacote version manifest for @angular-devkit/architect@0.11.4 fetched in 423ms
31 silly resolveWithNewModule @angular-devkit/architect@0.11.4 checking installable status
32 http fetch GET 304 https://registry.npmjs.org/symbol-observable 85557ms attempt #2 (from cache)
33 silly pacote version manifest for symbol-observable@1.2.0 fetched in 85558ms
34 silly resolveWithNewModule symbol-observable@1.2.0 checking installable status
35 http fetch GET 304 https://registry.npmjs.org/@schematics%2fupdate 85660ms attempt #2 (from cache)
36 silly pacote version manifest for @schematics/update@0.11.4 fetched in 85663ms
37 silly resolveWithNewModule @schematics/update@0.11.4 checking installable status
38 http fetch GET 304 https://registry.npmjs.org/@angular-devkit%2fcore 220984ms attempt #3 (from cache)
39 silly pacote version manifest for @angular-devkit/core@7.1.4 fetched in 220989ms
40 silly resolveWithNewModule @angular-devkit/core@7.1.4 checking installable status
41 warn registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning ETIMEDOUT: request to https://registry.npmjs.org/opn failed, reason: connect ETIMEDOUT 104.16.24.35:443
42 warn registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
43 http fetch GET 200 https://registry.npmjs.org/opn 296232ms (from cache)
44 silly pacote version manifest for opn@5.3.0 fetched in 296233ms
45 silly resolveWithNewModule opn@5.3.0 checking installable status
46 http fetch GET 200 https://registry.npmjs.org/rxjs 23376ms attempt #2
47 silly pacote version manifest for rxjs@6.3.3 fetched in 23384ms
48 silly resolveWithNewModule rxjs@6.3.3 checking installable status
49 http fetch GET 200 https://registry.npmjs.org/ajv 66ms
50 silly pacote version manifest for ajv@6.5.3 fetched in 71ms
51 silly resolveWithNewModule ajv@6.5.3 checking installable status
52 http fetch GET 200 https://registry.npmjs.org/source-map 94ms
53 silly pacote version manifest for source-map@0.7.3 fetched in 97ms
54 silly resolveWithNewModule source-map@0.7.3 checking installable status
55 http fetch GET 200 https://registry.npmjs.org/chokidar 23374ms attempt #2
56 silly pacote version manifest for chokidar@2.0.4 fetched in 23377ms
57 silly resolveWithNewModule chokidar@2.0.4 checking installable status
58 http fetch GET 200 https://registry.npmjs.org/fast-json-stable-stringify 96635ms attempt #3
59 silly pacote version manifest for fast-json-stable-stringify@2.0.0 fetched in 96637ms
60 silly resolveWithNewModule fast-json-stable-stringify@2.0.0 checking installable status
61 http fetch GET 200 https://registry.npmjs.org/fast-deep-equal 31ms
62 silly pacote range manifest for fast-deep-equal@^2.0.1 fetched in 35ms
63 silly resolveWithNewModule fast-deep-equal@2.0.1 checking installable status
64 http fetch GET 200 https://registry.npmjs.org/uri-js 71ms
65 silly pacote range manifest for uri-js@^4.2.2 fetched in 75ms
66 silly resolveWithNewModule uri-js@4.2.2 checking installable status
67 http fetch GET 200 https://registry.npmjs.org/json-schema-traverse 23332ms attempt #2
68 silly pacote range manifest for json-schema-traverse@^0.4.1 fetched in 23336ms
69 silly resolveWithNewModule json-schema-traverse@0.4.1 checking installable status
70 http fetch GET 200 https://registry.npmjs.org/punycode 32ms
71 silly pacote range manifest for punycode@^2.1.0 fetched in 36ms
72 silly resolveWithNewModule punycode@2.1.1 checking installable status
73 http fetch GET 200 https://registry.npmjs.org/inherits 9ms (from cache)
74 silly pacote range manifest for inherits@^2.0.1 fetched in 9ms
75 silly resolveWithNewModule inherits@2.0.3 checking installable status
76 http fetch GET 200 https://registry.npmjs.org/anymatch 31ms
77 silly pacote range manifest for anymatch@^2.0.0 fetched in 33ms
78 silly resolveWithNewModule anymatch@2.0.0 checking installable status
79 http fetch GET 200 https://registry.npmjs.org/glob-parent 72ms
80 http fetch GET 200 https://registry.npmjs.org/upath 40ms
81 silly pacote range manifest for glob-parent@^3.1.0 fetched in 77ms
82 silly resolveWithNewModule glob-parent@3.1.0 checking installable status
83 silly pacote range manifest for upath@^1.0.5 fetched in 46ms
84 silly resolveWithNewModule upath@1.1.0 checking installable status
85 http fetch GET 200 https://registry.npmjs.org/normalize-path 80ms
86 http fetch GET 200 https://registry.npmjs.org/is-glob 82ms
87 silly pacote range manifest for normalize-path@^2.1.1 fetched in 83ms
88 silly resolveWithNewModule normalize-path@2.1.1 checking installable status
89 silly pacote range manifest for is-glob@^4.0.0 fetched in 84ms
90 silly resolveWithNewModule is-glob@4.0.0 checking installable status
91 http fetch GET 200 https://registry.npmjs.org/path-is-absolute 95ms
92 http fetch GET 200 https://registry.npmjs.org/fsevents 35ms
93 silly pacote range manifest for fsevents@^1.2.2 fetched in 49ms
94 silly resolveWithNewModule fsevents@1.2.4 checking installable status
95 silly tarball trying https://registry.npmjs.org/fsevents/-/fsevents-1.2.4.tgz by hash: sha512-z8H8/diyk76B7q5wg+Ud0+CqzcAF3mBBI/bA5ne5zrRUUIvNkJY//D3BqyH571KuAC4Nr7Rw7CjWX4r0y9DvNg==
96 silly tarball no local data for https://registry.npmjs.org/fsevents/-/fsevents-1.2.4.tgz. Extracting by manifest.
97 http fetch GET 200 https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.1.tgz 41ms
98 silly pacote range manifest for path-is-absolute@^1.0.0 fetched in 141ms
99 silly resolveWithNewModule path-is-absolute@1.0.1 checking installable status
100 http fetch GET 200 https://registry.npmjs.org/fsevents/-/fsevents-1.2.4.tgz 204ms
101 silly extract https://registry.npmjs.org/fsevents/-/fsevents-1.2.4.tgz extracted to /tmp/npm-971-b8bb6b05/unpack-ed3e8fc9 (225ms)
102 silly addBundled read tarball
103 silly cleanup remove extracted module
104 http fetch GET 200 https://registry.npmjs.org/is-binary-path 23416ms attempt #2
105 silly pacote range manifest for is-binary-path@^1.0.0 fetched in 23419ms
106 silly resolveWithNewModule is-binary-path@1.0.1 checking installable status
107 http fetch GET 200 https://registry.npmjs.org/async-each 23426ms attempt #2
108 http fetch GET 200 https://registry.npmjs.org/braces 23428ms attempt #2
109 silly pacote range manifest for async-each@^1.0.0 fetched in 23430ms
110 silly resolveWithNewModule async-each@1.0.1 checking installable status
111 silly pacote range manifest for braces@^2.3.0 fetched in 23431ms
112 silly resolveWithNewModule braces@2.3.2 checking installable status
113 http fetch GET 200 https://registry.npmjs.org/readdirp 96685ms attempt #3
114 silly pacote range manifest for readdirp@^2.0.0 fetched in 96688ms
115 silly resolveWithNewModule readdirp@2.2.1 checking installable status
116 silly fetchPackageMetaData error for lodash.debounce@^4.0.8 request to https://registry.npmjs.org/lodash.debounce failed, reason: connect ETIMEDOUT 104.16.23.35:443
117 timing stage:rollbackFailedOptional Completed in 1ms
118 timing stage:runTopLevelLifecycles Completed in 549750ms
119 verbose type system
120 verbose stack FetchError: request to https://registry.npmjs.org/lodash.debounce failed, reason: connect ETIMEDOUT 104.16.23.35:443
120 verbose stack     at ClientRequest.req.on.err (/usr/local/lib/node_modules/npm/node_modules/node-fetch-npm/src/index.js:68:14)
120 verbose stack     at ClientRequest.emit (events.js:182:13)
120 verbose stack     at TLSSocket.socketErrorListener (_http_client.js:391:9)
120 verbose stack     at TLSSocket.emit (events.js:182:13)
120 verbose stack     at emitErrorNT (internal/streams/destroy.js:82:8)
120 verbose stack     at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
120 verbose stack     at process._tickCallback (internal/process/next_tick.js:63:19)
121 verbose cwd /
122 verbose Darwin 18.0.0
123 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "@angular/cli" "--verbose"
124 verbose node v10.13.0
125 verbose npm  v6.5.0
126 error code ETIMEDOUT
127 error errno ETIMEDOUT
128 error network request to https://registry.npmjs.org/lodash.debounce failed, reason: connect ETIMEDOUT 104.16.23.35:443
129 error network This is a problem related to network connectivity.
129 error network In most cases you are behind a proxy or have bad network settings.
129 error network
129 error network If you are behind a proxy, please make sure that the
129 error network 'proxy' config is set properly.  See: 'npm help config'
130 verbose exit [ 1, true ]

Platform Info

$ npm --versions
{ app: '0.0.1',
  npm: '6.5.0',
  ares: '1.14.0',
  cldr: '33.1',
  http_parser: '2.8.0',
  icu: '62.1',
  modules: '64',
  napi: '3',
  nghttp2: '1.34.0',
  node: '10.13.0',
  openssl: '1.1.0i',
  tz: '2018e',
  unicode: '11.0',
  uv: '1.23.2',
  v8: '6.8.275.32-node.36',
  zlib: '1.2.11' }

$ node -p process.platform
darwin

(Guilherme Campos) #2

I am having the same issue here. :( since yesterday


(Guilherme Campos) #3

I was able to get to work if I force the registry.npmjs.org name to resolve to one of their dns ips. (please don’t do this as a final fix). (Manually changing the /etc/hosts file)
It feels like one of their CDN servers are having trouble.

Actually was one off, is not working :frowning:

Where are you located? I am located in melbourne.

Yes. It’s possible that is Telstra. My friend tried with his phone and it works and its not telstra. My phone on Telstra doesn’t work. At the office is Telstra.


(Guilherme Campos) #4

@zkat do you have any clues? ^^


(Bkarv) #5

You have no idea how glad to hear that this is not only me! I’ve been working on it since yesterday thinking was an issue on my end…I’ve tried:

  • Reinstalling node
  • downgrading Node/NPM
  • cleaning the cache
  • checking firewalls
  • using multiple computers
  • different internet connections

I manage to successfully download one package on my laptop but it was really slow. You might be right about the CDN, I know little about networking but could there be an issue with too much traffic?

If there was an issue though shouldn’t be showing on npm status?

I will try your suggestion btw.


(Bkarv) #6

I’m located in Melbourne tool! Are you with Telstra?

@guilherme

Yes. It’s possible that is Telstra. My friend tried with his phone and it works and its not telstra. My phone on Telstra doesn’t work. At the office is Telstra

Makes sense I tried on mobile phone which is also Telstra. I did ring up telstra technical support but as you may guess they have no idea. I am that desperate I will go get a prepaid internet from another isp. What mobile company is your friend with?


(Bkarv) #7

Also I manually changed my etc/hosts to the following but still getting issues. Does my host file look right to you? Apart from restarting the computer is there anything else I need to do?

53%20am


(Kat Marchán) #8

Looking at the behavior definitely makes this look like intentional throttling. If you’re located with a telecom that’s likely to throttle heavy connection to a host, that’s what I’d say is going on. If you suspect npm itself is throttling you, I’d shoot an email to support@npmjs.com so we can check if you specifically hit a spam filter or something.


(Guilherme Campos) #9

it worked before, but was one off. I don’t think this will do. Yeah, that would be the idea.

For now, what we’re doing is using a phone connection with Optus.


(Bkarv) #10

Would using a VPN resolve the issue?


(Bkarv) #11

I found a workaround with Telstra. I configured my system to use proxies for HTTPS and HTTP from https://free-proxy-list.net/. Once configured I was able to use npm install without any hangups.

For macos the instructions are here:
https://kb.k12usa.com/knowledgebase/proxy-settings-on-a-mac-os-x

I also tried an Optus Internet connection and it worked. So it is definitely a Telstra issue. Perhaps they are throttling during the holidays.


(Guilherme Campos) #12

I was able to confirm with npm js support. I contacted them as @zkat suggested. there were issues with telstra on that day.


(Bkarv) #13

Thanks for the reply everything seems back working as normal now without proxies requirements.