npm "error network getaddrinfo ENOTFOUND"
Solution 1
I did not find any solution for this but at the end I had to re-install my Windows. It is working now...
Solution 2
Remove any proxy that is set in your npm config file.
At the command prompt, type npm config edit
This will open your .npmrc config file in your text editor.
Inside this file, go down to the proxy settings and if there are any entered settings there that you didn't configure yourself (such as http://proxyurl/:port
), remove these settings, save the file, and go from there. This fixes this issue most of the time.
Alok Pant
Alok Pant is web designer. I love creating designs that are simple and clean yet elegant and bold.
Updated on July 09, 2022Comments
-
Alok Pant almost 2 years
I am trying to install different modules through npm.
c:\>npm install -g express
But I am getting following error message:
0 info it worked if it ends with ok 1 verbose cli [ 'D:\\FH Kiel\\WS 13\\Advanced Javascript\\nodejs\\\\node.exe', 1 verbose cli 'D:\\FH Kiel\\WS 13\\Advanced Javascript\\nodejs\\node_modules\\npm\\bin\\npm-cli.js', 1 verbose cli 'install', 1 verbose cli 'express' ] 2 info using [email protected] 3 info using [email protected] 4 verbose node symlink D:\FH Kiel\WS 13\Advanced Javascript\nodejs\\node.exe 5 verbose cache add [ 'express', null ] 6 verbose cache add name=undefined spec="express" args=["express",null] 7 verbose parsed url { protocol: null, 7 verbose parsed url slashes: null, 7 verbose parsed url auth: null, 7 verbose parsed url host: null, 7 verbose parsed url port: null, 7 verbose parsed url hostname: null, 7 verbose parsed url hash: null, 7 verbose parsed url search: null, 7 verbose parsed url query: null, 7 verbose parsed url pathname: 'express', 7 verbose parsed url path: 'express', 7 verbose parsed url href: 'express' } 8 silly lockFile f3c62de4-express express 9 verbose lock express C:\Users\MW\AppData\Roaming\npm-cache\f3c62de4-express.lock 10 silly lockFile f3c62de4-express express 11 silly lockFile f3c62de4-express express 12 verbose addNamed [ 'express', '' ] 13 verbose addNamed [ null, '*' ] 14 silly lockFile 64a534c1-express express@ 15 verbose lock express@ C:\Users\MW\AppData\Roaming\npm-cache\64a534c1-express.lock 16 silly addNameRange { name: 'express', range: '*', hasData: false } 17 verbose url raw express 18 verbose url resolving [ 'http://registry.npmjs.org/', './express' ] 19 verbose url resolved http://registry.npmjs.org/express 20 info trying registry request attempt 1 at 15:47:46 21 http GET http://registry.npmjs.org/express 22 info retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND 23 info trying registry request attempt 2 at 15:47:59 24 http GET http://registry.npmjs.org/express 25 info retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND 26 info trying registry request attempt 3 at 15:49:01 27 http GET http://registry.npmjs.org/express 28 silly lockFile 64a534c1-express express@ 29 silly lockFile 64a534c1-express express@ 30 error network getaddrinfo ENOTFOUND 30 error network This is most likely not a problem with npm itself 30 error network and is related to network connectivity. 30 error network In most cases you are behind a proxy or have bad network settings. 30 error network 30 error network If you are behind a proxy, please make sure that the 30 error network 'proxy' config is set properly. See: 'npm help config' 31 error System Windows_NT 6.1.7601 32 error command "D:\\FH Kiel\\WS 13\\Advanced Javascript\\nodejs\\\\node.exe" "D:\\FH Kiel\\WS 13\\Advanced Javascript\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "express" 33 error cwd D:\nodejs 34 error node -v v0.10.22 35 error npm -v 1.3.14 36 error syscall getaddrinfo 37 error code ENOTFOUND 38 error errno ENOTFOUND 39 verbose exit [ 1, true ]
I have tried the following solutions:
npm config set proxy http://usr:pwd@proxyname:port npm config set https-proxy http://usr:pwd@proxyname:port npm config set registry http://registry.npmjs.org/
I have disabled the firewall and tried... nothing is working... There is no proxy setting so this should work (and is working in other computers)... I have installed node.js without any problem.
Thanx.
Update: Here is the windows host file :
# # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost 127.0.0.1 localhost 127.0.0.1 localhost 127.0.0.1 localhost
I have also tried this solution found in other post:
npm install <packagename> --registry http://registry.npmjs.org/
Didn't work either :(
-
MNG MAN almost 4 years
npm config delete proxy
somehow did it for me -
Abrar Hossain about 3 yearsWelcome to SO. Firstly, similar suggestions are already provided by older answers. Secondly, the OP mentioned that they tried to set the registry explicitly while install the package and that did not work. Next time, carefully review existing answers and add your answer when there is relevant information missing in existing answers or you have another approach that is not mentioned by any other answers.