Error while trying to install with npm

Igor Moura · 13 Mar 2016, 20:31

Hey folks,
After updating my onion and installing node/npm, I can't install anything using npm, all it does is throw me the following error:

npm ERR! Linux 3.18.27
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "npm@latest"
npm ERR! node v4.3.1
npm ERR! npm  v2.14.12
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! syscall getaddrinfo

npm ERR! network getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is 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'

npm ERR! Please include the following file with any support request:
npm ERR!     /root/npm-debug.log

It's worth saying that I don't have a proxy and I'm able to ping/curl without problems.
Any ideas?

Matt Ogborne · 14 Mar 2016, 18:35

@Igor-Moura I've got the same issue as well. I'd love to know a resolution too.

And I'm betting you have no proxy like me either!

Matt

Matt Ogborne · 14 Mar 2016, 18:47

As a reference I've tried:

npm config set strict-ssl false
npm config set registry http://registry.npmjs.org/

And also using this fails too:

npm install <packagename> --registry http://registry.npmjs.org/

And of course I've also checked the Omega can actually reach "registry.npmjs.org", it responds to a ping command.

Matt

Benjamin Rau · 14 Mar 2016, 20:24

Same problem here!
No proxy, accessing registry with wget works fine, also on https....

Some fix would be really great!!

Igor Moura · 15 Mar 2016, 23:31

@Matt-Ogborne looks like we are in the same situation.

The only thing I could do for now was to load the modules manually (git clone or use npm in another device, then copy the downloaded folder to the omega).

Zheng Han · 16 Mar 2016, 04:28

Thanks for raising this issue. It seems to be related to IPv6 resolution. We are working on a fix.

Jean-Philippe Rey · 17 Mar 2016, 19:21

Same issue for me. Did anyone fix it in the meantime?

Ates Goral · 26 Mar 2016, 23:21

@Zheng-Han Are there at least any workarounds for the time being?

Christopher Hiller · 29 Mar 2016, 16:19

I spent a few hours w/ this last night but was unable to find a workaround that didn't involve manual modification of the Node.js sources to force dns resolution via IPv4. I'd also be very surprised if Node.js was the only affected program!

Lazar Demin · 1 Apr 2016, 17:57

We're very close to a fix, sit tight!

Matt Ogborne · 1 Apr 2016, 19:38

@Lazar-Demin said:

We're very close to a fix, sit tight!

Happy days

Matt

Zheng Han · 3 Apr 2016, 05:09

Fix is now available with the new 0.0.8 firmware release

Ates Goral · 5 Apr 2016, 15:48

@Zheng-Han Awesome! Will give it a shot now.