You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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!
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:
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.
The text was updated successfully, but these errors were encountered: