npm 404 error #4455

Closed
paralin opened this Issue Jan 9, 2014 · 18 comments

Projects

None yet
paralin commented Jan 9, 2014

I'm getting a 404 on the package faye-websocket when I can copy and paste the link it tries to download into my browser and it works just fine.

Here is the error:

npm http GET https://registry.npmjs.org/sockjs/0.3.8
npm http 304 https://registry.npmjs.org/sockjs/0.3.8
npm http GET https://registry.npmjs.org/node-uuid/1.3.3
npm http GET https://registry.npmjs.org/faye-websocket/0.7.0
npm http 304 https://registry.npmjs.org/node-uuid/1.3.3
npm http 304 https://registry.npmjs.org/faye-websocket/0.7.0
npm http GET https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.7.0.tgz
npm http 404 https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.7.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.7.0.tgz
npm ERR! Error: 404 Not Found
npm ERR!     at WriteStream.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/fetch.js:57:12)
npm ERR!     at WriteStream.EventEmitter.emit (events.js:117:20)
npm ERR!     at fs.js:1596:14
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:103:5
npm ERR!     at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/isaacs/npm/issues>

npm ERR! System Linux 3.11.0-15-generic
npm ERR! command "node" "/usr/local/bin/npm" "install" "."
npm ERR! cwd ---snip---
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.23
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!    ----snip---- 
npm ERR! not ok code 0

And from the detailed debug

130 http GET https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.7.0.tgz
131 http 404 https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.7.0.tgz

If I simply put https://registry.npmjs.org/faye-websocket/-/faye-websocket-0.7.0.tgz into my web browser it works just fine.

ryross commented Jan 9, 2014

I'm seeing this, but on many other packages (domhandler, readable-stream, and more).

Can confirm problem with various packages as well.

ryross commented Jan 9, 2014

The errors are intermittent for me. I was able to get past this error by waiting and trying a few more times.

+1 I'm getting errors on various packages

I'm also getting random 404s with npm 1.3.14, right now it's domelementtype, domutils, cheerio, and others intermittently.

neumino commented Jan 9, 2014

I get this error on bytebuffer too.
Using wget to get the package doesn't work if I don't provide a user agent.

whampop commented Jan 9, 2014

+1
npm install gulp-header
404

juehuizh commented Jan 9, 2014

+1
A lot of npm install 404 error

I see the following on OSX

$ sudo npm install -g express
npm http GET https://registry.npmjs.org/express
npm http 304 https://registry.npmjs.org/express
npm http GET https://registry.npmjs.org/express/-/express-3.4.7.tgz
npm http 200 https://registry.npmjs.org/express/-/express-3.4.7.tgz
npm http GET https://registry.npmjs.org/connect/2.12.0
npm http GET https://registry.npmjs.org/commander/1.3.2
npm http GET https://registry.npmjs.org/mkdirp/0.3.5
npm http GET https://registry.npmjs.org/range-parser/0.0.4
npm http GET https://registry.npmjs.org/cookie/0.1.0
npm http GET https://registry.npmjs.org/buffer-crc32/0.2.1
npm http GET https://registry.npmjs.org/fresh/0.2.0
npm http GET https://registry.npmjs.org/methods/0.1.0
npm http GET https://registry.npmjs.org/send/0.1.4
npm http GET https://registry.npmjs.org/cookie-signature/1.0.1
npm http GET https://registry.npmjs.org/merge-descriptors/0.0.1
npm http GET https://registry.npmjs.org/debug
npm http 200 https://registry.npmjs.org/mkdirp/0.3.5
npm http 200 https://registry.npmjs.org/connect/2.12.0
npm http 200 https://registry.npmjs.org/commander/1.3.2
npm http 200 https://registry.npmjs.org/range-parser/0.0.4
npm http 200 https://registry.npmjs.org/cookie/0.1.0
npm http 200 https://registry.npmjs.org/fresh/0.2.0
npm http 200 https://registry.npmjs.org/methods/0.1.0
npm http 200 https://registry.npmjs.org/send/0.1.4
npm http GET https://registry.npmjs.org/range-parser/-/range-parser-0.0.4.tgz
npm http GET https://registry.npmjs.org/commander/-/commander-1.3.2.tgz
npm http GET https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz
npm http GET https://registry.npmjs.org/cookie/-/cookie-0.1.0.tgz
npm http GET https://registry.npmjs.org/connect/-/connect-2.12.0.tgz
npm http GET https://registry.npmjs.org/fresh/-/fresh-0.2.0.tgz
npm http GET https://registry.npmjs.org/send/-/send-0.1.4.tgz
npm http GET https://registry.npmjs.org/methods/-/methods-0.1.0.tgz
npm http 200 https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz
npm http 200 https://registry.npmjs.org/range-parser/-/range-parser-0.0.4.tgz
npm http 200 https://registry.npmjs.org/send/-/send-0.1.4.tgz
npm http 200 https://registry.npmjs.org/methods/-/methods-0.1.0.tgz
npm http 200 https://registry.npmjs.org/buffer-crc32/0.2.1
npm http 200 https://registry.npmjs.org/cookie-signature/1.0.1
npm http 200 https://registry.npmjs.org/debug
npm http 200 https://registry.npmjs.org/merge-descriptors/0.0.1
npm http GET https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.1.tgz
npm http GET https://registry.npmjs.org/debug/-/debug-0.7.4.tgz
npm http GET https://registry.npmjs.org/cookie-signature/-/cookie-signature-1.0.1.tgz
npm http GET https://registry.npmjs.org/merge-descriptors/-/merge-descriptors-0.0.1.tgz
npm http 404 https://registry.npmjs.org/fresh/-/fresh-0.2.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/fresh/-/fresh-0.2.0.tgz
npm http 200 https://registry.npmjs.org/commander/-/commander-1.3.2.tgz
npm http 200 https://registry.npmjs.org/cookie/-/cookie-0.1.0.tgz
npm http 200 https://registry.npmjs.org/connect/-/connect-2.12.0.tgz
npm http 200 https://registry.npmjs.org/merge-descriptors/-/merge-descriptors-0.0.1.tgz
npm ERR! Error: 404 Not Found
npm ERR! at WriteStream. (/usr/local/lib/node_modules/npm/lib/utils/fetch.js:57:12)
npm ERR! at WriteStream.EventEmitter.emit (events.js:117:20)
npm ERR! at fs.js:1596:14
npm ERR! at /usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:103:5
npm ERR! at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! npm-@googlegroups.com

npm ERR! System Darwin 10.8.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "express"
npm ERR! cwd /private/etc/puppet/hiera/develop
npm ERR! node -v v0.10.21
npm ERR! npm -v 1.3.11
npm http 200 https://registry.npmjs.org/debug/-/debug-0.7.4.tgz
npm http 200 https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.1.tgz
npm http 200 https://registry.npmjs.org/cookie-signature/-/cookie-signature-1.0.1.tgz
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /private/etc/puppet/hiera/develop/npm-debug.log
npm ERR! not ok code 0

I ran into this as well.

ryross commented Jan 9, 2014

As @3rd-Eden linked to above, NPM "switched to a new manta account, some tarballs got lost in transit, hence the 404s. backed replication up a bit, seems to be filling in."

This is a temporary issue. Let's stop +1ing this :) For those of you who don't know, you can unsubscribe from this thread on the bottom of this issue page.

For a quick workaround you can
download the file via browser,
unzip,
and add it to the npm-cache folder on your filesystem.

yeah, all fixed. thanks!

Member

@kidovate are you still experiencing this issue? Looks like it was a temporary glitch. Can you try again and report back?

#4430

@domenic domenic closed this Jan 11, 2014
AidasK commented Jan 14, 2014

npm install swagger-ui
npm http GET https://registry.npmjs.org/swagger-ui
npm http 304 https://registry.npmjs.org/swagger-ui
npm http GET https://registry.npmjs.org/swagger-ui/-/swagger-ui-2.0.3.tgz
npm http 404 https://registry.npmjs.org/swagger-ui/-/swagger-ui-2.0.3.tgz
npm ERR! fetch failed https://registry.npmjs.org/swagger-ui/-/swagger-ui-2.0.3.tgz
npm ERR! Error: 404 Not Found
npm ERR! at WriteStream. (C:\Program Files\nodejs\node_modules\npm\lib\utils\fetch.js:57:12)
npm ERR! at WriteStream.EventEmitter.emit (events.js:117:20)
npm ERR! at fs.js:1596:14
npm ERR! at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:103:5
npm ERR! at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! npm-@googlegroups.com

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "swagger-ui"
npm ERR! cwd C:\wamp\www
npm ERR! node -v v0.10.18
npm ERR! npm -v 1.3.8
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\wamp\www\npm-debug.log
npm ERR! not ok code 0

paralin commented Jan 15, 2014

Seems to be fixed for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment