Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It does not work reason: connect ECONNREFUSED 104.18.97.96:443 !!! #5

Open
denis99999 opened this issue Jun 27, 2018 · 3 comments
Open

Comments

@denis99999
Copy link

Hi,

My machine is behind a proxy, I set the npm proxy settings and 'npm install' works fine !
But when I try 'npm-consider install', it fails with this error:

GET https://registry.npmjs.org/http-proxy{ FetchError: request to https://registry.npmjs.org/@slack%2fclient failed, reason: connect ECONNREFUSED 104.18.95.96:443
    at ClientRequest.<anonymous> (/usr/lib/node_modules/npm-consider/node_modules/node-fetch/index.js:133:11)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at TLSSocket.socketErrorListener (_http_client.js:387:9)
    at emitOne (events.js:116:13)
    at TLSSocket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
  name: 'FetchError',
  message: 'request to https://registry.npmjs.org/@slack%2fclient failed, reason: connect ECONNREFUSED 104.18.95.96:443',
  type: 'system',
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED' }

It seems 104.18.95.96:443 is hard-coded as a proxy by the tool because it is not the proxy I configured !

Thanks.

@denis99999
Copy link
Author

But if the machine is not behind a proxy, it works well !

@delfrrr
Copy link
Owner

delfrrr commented Jun 28, 2018

true, proxy is not supported.

@delfrrr
Copy link
Owner

delfrrr commented Aug 6, 2018

Hi! I checked the address you mention 104.18.95.96

EDIT:

I compared traceroute registry.npmjs.org with traceroute 104.16.23.35 and its probably one of the addressed of registry.npmjs.org returned by their dynamic DNS

looks like the issue is with a network setup in your place;

probably it will work if proxy support added to the tool

if you can contribute and test proxy support, please do!

@delfrrr delfrrr added help wanted and removed bug labels Aug 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants