npm ERR! code: 'ECONNREFUSED',

[CXX22]

Resolved

[preveen-stack]

@VivaRunor Looks like on your system registry.npmjs.org resolves to 10.32.47.71 which is a private ip address. Can you check your DNS pls.

On my system registry.npmjs.org resolves to 104.16.17.35 a public ip address.

[CXX22]

I'm trying my best but not yielding any positive result but errors

…

On 4 May 2019 15:29, "Preveen P" ***@***.***> wrote: @VivaRunor <https://github.com/VivaRunor> Looks like on your system registry.npmjs.org resolves to 10.32.47.71 which is a private ip address. Can you check your DNS pls. On my system registry.npmjs.org resolves to 104.16.17.35 a public ip address. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1887 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALKBGF7A7EIBCZECIDTZEA3PTWMUJANCNFSM4HJ5EIYQ> .

Can you please post the results of the following command on your system

ping -c 4 registry.npmjs.org

On my system the results look like this

PING registry.npmjs.org (104.16.22.35): 56 data bytes
64 bytes from 104.16.22.35: icmp_seq=0 ttl=55 time=27.237 ms
64 bytes from 104.16.22.35: icmp_seq=1 ttl=55 time=23.215 ms
64 bytes from 104.16.22.35: icmp_seq=2 ttl=55 time=24.693 ms
64 bytes from 104.16.22.35: icmp_seq=3 ttl=55 time=23.407 ms

--- registry.npmjs.org ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 23.215/24.638/27.237/1.605 ms

[CXX22]

@wide4head thanks for the followup.

I tried what you suggested and I was told:
Access denied. Option -C requires administrative privileges.

I did this on vs code terminal and my command prompt terminal. I even run my cmd as an administrator but still denied access

@VivaRunor please use lower case letter -c option and not the upper case one

@VivaRunor Oh, I forgot that you are on windows.

You only need

ping registry.npmjs.org

[CXX22]

Resolved

[CXX22]

Although, my system is not having internet presently. There's a disruption some minutes ago in my server.

I tried ping registry.npmjs.org and was told ping request could not find host registry.npmjs.org

Does ping work without internet plz?

@VivaRunor But the whole point of conversing through github comments in the nodejs/help repository is that the conversation is potentially helpful to other people with similar problems.

Sorry. the ping command will not work without the internet ;-)

[CXX22]

I know.
I wanna share something with you via email so you use to assist me

@VivaRunor go ahead and share in the comments so that other people, with far more experience than I have, can potentially help out

[CXX22]

You arent serious. I should share my personal details with you publicly cos I need speedy assistance? You can go

…

On 7 May 2019 09:53, "Preveen Padmanabhan" ***@***.***> wrote: @VivaRunor <https://github.com/VivaRunor> go ahead and share in the comments so that other people, with far more experience than I have, can potentially help out — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1887 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALKBGF7T7A5U7W6PRIJ4C6DPUE7PXANCNFSM4HJ5EIYQ> .

I think this issue is caused by an unreachable proxy on the local network.

Anybody comes across similar issues, make sure that the proxy server software is up and running on the designated proxy server machine on the local network and is listening to the correct port # as configured in the npm configuration.

More about proxy configuration can be found in
https://docs.npmjs.com/misc/config

Also
https://jjasonclark.com/how-to-setup-node-behind-web-proxy/
http://luxiyalu.com/how-to-remove-all-npm-proxy-settings/

[CXX22]

I started attempting to fix this issue since last week. I tried updating the proxy, getting and setting it according to some steps I followed on stackoverflow, I have also cleared the cache but to no avail. Now, I need someone with teamviewer to help check. That's all

…

On 7 May 2019 10:11, "Preveen Padmanabhan" ***@***.***> wrote: I think this issue is caused by an unreachable proxy on the local network. Anybody comes across similar issues, make sure that the proxy server software is up and running on the designated proxy server machine on the local network and is listening to the correct port # as configured in the npm configuration. More about proxy configuration can be found in https://docs.npmjs.com/misc/config <http://url> Also https://jjasonclark.com/how-to-setup-node-behind-web-proxy/ <http://url> http://luxiyalu.com/how-to-remove-all-npm-proxy-settings/ <http://url> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1887 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALKBGF6L4AY2DFWC4PWJZNTPUFBTRANCNFSM4HJ5EIYQ> .

[CXX22]

Resolved