Skip to content

Instantly share code, notes, and snippets.

@triptych
Created April 14, 2011 21:23
Show Gist options
  • Select an option

  • Save triptych/920592 to your computer and use it in GitHub Desktop.

Select an option

Save triptych/920592 to your computer and use it in GitHub Desktop.
feedchief-lm:~ awooldri$ npm install couchdb
npm info it worked if it ends with ok
npm info using npm@0.2.11-5
npm info using node@v0.4.4
npm info range traits@>=0.3.0
npm ERR! registry error parsing json
npm ERR! Failed to fetch http://packages.dojofoundation.org/promised-io
npm ERR! SyntaxError: Unexpected token ILLEGAL
npm ERR! <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
npm ERR! <html><head>
npm ERR! <title>502 Proxy Error</title>
npm ERR! </head><body>
npm ERR! <h1>Proxy Error</h1>
npm ERR! <p>The proxy server received an invalid
npm ERR! response from an upstream server.<br />
npm ERR! The proxy server could not handle the request <em><a href="/promised-io">GET&nbsp;/promised-io</a></em>.<p>
npm ERR! Reason: <strong>Error reading from remote server</strong></p></p>
npm ERR! <p>Additionally, a 502 Bad Gateway
npm ERR! error was encountered while trying to use an ErrorDocument to handle the request.</p>
npm ERR! <hr>
npm ERR! <address>Apache/2.2.15 (Linux/SUSE) Server at packages.dojofoundation.org Port 80</address>
npm ERR! </body></html>
npm ERR!
npm ERR! at Object.parse (native)
npm ERR! at IncomingMessage.<anonymous> (/usr/local/Cellar/npm/0.2.11-5/libexec/lib/utils/registry/request.js:121:25)
npm ERR! at IncomingMessage.emit (events.js:81:20)
npm ERR! at HTTPParser.onMessageComplete (http.js:132:23)
npm ERR! at Client.onData [as ondata] (http.js:1464:27)
npm ERR! at Client._onReadable (net.js:677:27)
npm ERR! at IOWatcher.onReadable [as callback] (net.js:177:10)
npm ERR! Report this *entire* log at <http://github.com/isaacs/npm/issues>
npm ERR! or email it to <npm-@googlegroups.com>
npm ERR! Just tweeting a tiny part of the error will not be helpful.
npm not ok
feedchief-lm:~ awooldri$
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment