npm ERR! code ERR_SOCKET_TIMEOUT npm ERR! network Socket timeout

Question

This the error:

npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! network Socket timeout
npm ERR! network This is a problem 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'

I ran npm cache clean --force

Deleted node_modules and package-lock.json and run npm install but still got me that error

are you running ubuntu ? 20.04 ? did you get any solutions ? — mod7ex, Jun 28 '22 at 21:27
In my case, I was using laragon on windows for development, I just needed to use npm from Cmdler terminal — OLIVIERS, Sep 18 '22 at 21:30
me i was using vpn while installing npm @agular/cli when i turned it off.. it worked — Nsamba Isaac, Jul 19 '23 at 09:06

mod7ex · Accepted Answer · 2022-09-23T21:53:31.327

26

Try this answer

or run npm i -g npm@8.5.1

i think it's an issue with npm version , 8.5.1 solves the problem in most cases

basically try earlier versions and i think the problem will be solved

edited Sep 23 '22 at 21:53

answered Jun 28 '22 at 21:53

mod7ex

874
9
27

1

I've been trying to solve this since 4 hours, this finally solved my problem, thank you – saurabh gajjar Mar 28 '23 at 18:16

Suptohita · Answer 2 · 2023-07-03T08:14:48.500

I faced this error some days ago. I changed the timeout and it works for me. (Note: my npm version was 8.19.1)

You can try this solution with other npm versions as well.

First of all, check the current settings. For checking the current settings run npm config ls -l

Then, check these 4 values (fetch-retries, fetch-retry-factor, fetch-retry-maxtimeout, fetch-retry-mintimeout, fetch-timeout)

$ npm config ls -l

fetch-retries = 2
fetch-retry-factor = 10
fetch-retry-maxtimeout = 60000
fetch-retry-mintimeout = 10000
fetch-timeout = 300000

For changing the time out, Run these two commands-

npm config set fetch-retry-mintimeout 20000

npm config set fetch-retry-maxtimeout 120000

score 5 · Answer 3 · answered Sep 13 '22 at 21:32

5

I am not sure if this will help anyone else, but what appears to have worked for me was dropping my company's VPN connection and reestablishing it!

answered Sep 13 '22 at 21:32

cptully

615
1
9
24

I had the same issue with Proton VPN – Adam Apr 21 '23 at 19:36

score 4 · Answer 4 · answered Jul 02 '22 at 12:19

I solved this by setting a timeout of 60000 for npm in the .npmrc file. To do that from your terminal, simply do the following:

$ nano .npmrc from your work directory if you want a configuration locally.

Add timeout=60000, save and you're good to go.

Originally posted here: https://github.com/facebook/create-react-app/issues/10251

score 3 · Answer 5 · answered Aug 06 '22 at 13:31

3

I faced this problem recently. I tried many solutions like npm cache verify, npm cache clean --force, npm config set fetch-retry-mintimeout, npm config set fetch-retry-maxtimeout, deleting package-lock.json, using different version of npm and/or node.

But the solution that worked for me was to switch to yarn.

answered Aug 06 '22 at 13:31

Rivosoa

61
2
4

1

deleting yarn.lock would have fixed o your issue. Seems like it looks in yarn.lock instead of package.json first. – Indunil Withana Sep 23 '22 at 10:49

score 3 · Answer 6 · answered Aug 15 '22 at 18:37

3

You can resolve this using YARN package manager. yarn create react-app my-app hope it help.

answered Aug 15 '22 at 18:37

Dhanushka sasanka

518
3
18

100% worked for me – Pamela Sillah Dec 01 '22 at 15:48

score 2 · Answer 7 · answered Feb 18 '23 at 06:23

2

Try removing proxy settings by running the commands below:

$ npm config rm proxy
$ npm config rm https-proxy

answered Feb 18 '23 at 06:23

David Njuguna

803
7
8

thanks that worked for me on a fresh installation of 19.9.0. i didn't have to change any timeouts – Luke Schoen Jun 19 '23 at 23:56

score 1 · Answer 8 · answered Sep 23 '22 at 11:27

1

In my scenario, it was the yarn.lock file availability. So the installer tried to fetch dependencies and threw an error since the response time was delayed. So deleted both yarn.lock and package.lock file and reinstalled after setting npm to npm@8.5.1

answered Sep 23 '22 at 11:27

Indunil Withana

176
1
8

score 1 · Answer 9 · answered May 01 '23 at 12:08

1

I was able to install packages using yarn install instead.

answered May 01 '23 at 12:08

Luc Thi

21
1
1

score 0 · Answer 10 · answered Nov 10 '22 at 12:40

0

I found solution for it, which works great for me

1.npm config set registry http://registry.npmjs.org/

2.npm i or npm i --save --legacy-peer-deps

answered Nov 10 '22 at 12:40

Yasir

489
5
11

score 0 · Answer 11 · answered Apr 27 '23 at 10:29

0

My problem was that my system was using the homebrew version of npm, not the one I installed with tj/n. Once I ran brew uninstall node everything was fine again.

answered Apr 27 '23 at 10:29

Jan Wirth

411
2
13

score 0 · Answer 12 · answered May 14 '23 at 06:50

0

In my case, deleting the yarn.lock file solved the problem.

answered May 14 '23 at 06:50

Nishant Kumar

691
1
11
31

score 0 · Answer 13 · answered May 26 '23 at 12:13

I had this problem. It turned out that I have two VPNs turned on. Once I turned off the VPN that was not meant for this project, it worked. It might worth checking if you need a VPN to run your project or if you need to turn the VPN off before running the project.

score 0 · Answer 14 · answered May 30 '23 at 23:00

0

Downgrading node from 20 to 19 helped me (macOS, homebrew):

$ brew unlink node
$ brew install node@19

answered May 30 '23 at 23:00

yegor256

102,010
123
446
597

Karma Dechen Dema · Answer 15 · 2022-06-04T18:38:26.250

-2

mine worked using these steps, hope it works for you too.

npm cache clean --force
npm uninstall -g create-react-app
npm uninstall create-react-app and then
npx create-react-app project-app

if it does not then probably your internet connection is poor or there is a proxy set up error. let me know if it does not work.

edited Jun 04 '22 at 18:38

answered Jun 04 '22 at 18:36

Karma Dechen Dema

1
1

npm ERR! code ERR_SOCKET_TIMEOUT npm ERR! network Socket timeout

15 Answers15