Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

npm install mongoose returns 404. Fetch failed #2697

Closed
ravishroshan opened this Issue · 3 comments

3 participants

@ravishroshan

Hi,
i have trying to install mongoose for quite sometime now. However, I always get 404 error.

The error trace was as follows.

c:\InnoJam\PingCounter>npm install mongoose
npm WARN package.json applauseometer@0.0.1 No README.md file found!
npm http GET http://registry.npmjs.org/mongoose
npm http 200 http://registry.npmjs.org/mongoose
npm http GET http://registry.npmjs.org/-/mongoose-3.0.1.tgz
npm http 404 http://registry.npmjs.org/-/mongoose-3.0.1.tgz
npm ERR! fetch failed http://registry.npmjs.org/-/mongoose-3.0.1.tgz
npm ERR! Error: 404 Not Found
npm ERR! at null. (C:\Program Files\nodejs\node_modules\npm\lib\utils\fetch.js:47:16)
npm ERR! at EventEmitter.emit (events.js:115:20)
npm ERR! at WriteStream.flush (fs.js:1511:12)
npm ERR! at fs.close (C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:94:5)
npm ERR! at Object.oncomplete (fs.js:297: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" "mongoose"
npm ERR! cwd c:\InnoJam\PingCounter
npm ERR! node -v v0.8.4
npm ERR! npm -v 1.1.45
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! c:\InnoJam\PingCounter\npm-debug.log
npm ERR! not ok code 0

@shimaore

Seeing the same issue with some of my own packages as well. Re-publish (npm --force publish, no errors), clear ~/.npm/<package>, npm install <package> fails due to missing .tgz.

When trying to access the URL with a browser or curl, they both complain about Untrusted Connection (the CA is npm CA).

This is with Node.js 0.8.6, npm 1.1.48.

@ravishroshan

Closing the issue. It's working now. Probably the server issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.