[BUG] npm I fails due to IP address being used to connect

[Lagicrus]

Is there an existing issue for this?

• [X] I have searched the existing issues

This issue exists in the latest npm version

• [X] I am using the latest npm

Current Behavior

When I run npm i after getting the packages it then spits out

npm ERR! code ETIMEDOUT
npm ERR! syscall connect
npm ERR! errno ETIMEDOUT
npm ERR! network request to http://192.168.3.117/value-equal/-/value-equal-1.0.1.tgz failed, reason: connect ETIMEDOUT 192.168.3.117:80
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 am not using the 192.168.3.X subnet
• No Proxy was set
• No Proxy is in use I have thus far 0 ideas how to fix or find where it is pulling that IP address from

Expected Behavior

It to connect to the normal npm.com domain and download the package

Steps To Reproduce

1. Run npm i

Environment

• npm: 8.5.5
• Node.js: v17.9.0
• OS Name: Windows
• System Model Name: 11
• npm config:

; "user" config from C:\Users\Lagicrus\.npmrc

registry = "https://registry.npmjs.org/"

; node bin location = C:\Program Files\nodejs\node.exe
; cwd = E:\GitHub\project
; HOME = C:\Users\Lagicrus
; Run `npm config ls -l` to show all defaults.

[lukekarrys]

Can you share the package.json and/or debug log from your install?

[Lagicrus]

https://starb.in/A67y9U.json - package.json https://starb.in/UljlON.log - debug log @lukekarrys

[lukekarrys]

Thanks @lagicrus. One more thing, is the output from npm config ls in your first comment run from your project directory? It says cwd = E:\GitHub\project which makes me think it is not. Can you navigate to the directory containing the package.json and run npm config ls again and paste that output?

[lukekarrys]

I'm not able to reproduce this so far with the information I have.

npm config ls

; "user" config from /Users/lukekarrys/.npmrc

//registry.npmjs.org/:_authToken = (protected) 
registry = "https://registry.npmjs.org/" 
sign-git-tag = true 

; "project" config from /Users/lukekarrys/Documents/npm-sandbox/4720/.npmrc

cache = "/Users/lukekarrys/Documents/npm-sandbox/4720/.cache" 
loglevel = "silly" 
logs-dir = "/Users/lukekarrys/Documents/npm-sandbox/4720" 
logs-max = 9999999 

; node bin location = /Users/lukekarrys/.volta/tools/image/node/16.14.2/bin/node
; cwd = /Users/lukekarrys/Documents/npm-sandbox/4720
; HOME = /Users/lukekarrys
; Run `npm config ls -l` to show all defaults.

I'm setting some config items to make getting logs easier and ensuring an empty cache to force the tarball no local data for code path.

And here are the resulting logs: 2022-04-10T17_38_40_769Z-debug-0.log

I suspect there is something else in your local config or environment that is setting that url. Running npm config ls in your project dir will help narrow that down.

[Lagicrus]

; "user" config from C:\Users\Lagicrus\.npmrc

registry = "https://registry.npmjs.org/"

; node bin location = C:\Program Files\nodejs\node.exe
; cwd = E:\GitHub\vaccinator-fe
; HOME = C:\Users\Lagicrus
; Run `npm config ls -l` to show all defaults.

[lukekarrys]

Thanks for the follow-up. I see that you were originally in the correct directory, so nothing has changed. I'm attempting to reproduce on macOS so it's possible something platform specific is happening which I should be able to test on later. But for now I don't know why this would be happening. 🤔

[Rajdave69]

Deleting package-lock.json fixed this issue for me.

[owlstronaut]

Deleting package-lock.json fixed this issue for me.

Are you saying the issue has been resolved then?

[Rajdave69]

I guess so. I haven't tried this with OP's exact configuration though

[owlstronaut]

I think your profile pictures were similar enough on a small screen that I thought you were op 😆