Last active
August 29, 2015 13:56
-
-
Save stelcheck/9319397 to your computer and use it in GitHub Desktop.
npm publish fail
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mt@kodachi:~/node-graylog2 (node-graylog2.git::master)$ npm publish | |
Now using NPM under Node.js v0.6.11 | |
npm http PUT https://registry.npmjs.org/graylog2 | |
npm http 201 https://registry.npmjs.org/graylog2 | |
npm http GET https://registry.npmjs.org/graylog2 | |
npm http 200 https://registry.npmjs.org/graylog2 | |
npm http PUT https://registry.npmjs.org/graylog2/0.1.2/-tag/latest | |
npm http 201 https://registry.npmjs.org/graylog2/0.1.2/-tag/latest | |
npm http GET https://registry.npmjs.org/graylog2 | |
npm http 200 https://registry.npmjs.org/graylog2 | |
npm http PUT https://registry.npmjs.org/graylog2/-/graylog2-0.1.2.tgz/-rev/12-492340f10f553812836a3788c41d200d | |
npm http 502 https://registry.npmjs.org/graylog2/-/graylog2-0.1.2.tgz/-rev/12-492340f10f553812836a3788c41d200d | |
npm ERR! registry error parsing json | |
npm ERR! publish failed SyntaxError: Unexpected token < | |
npm ERR! publish failed <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> | |
npm ERR! publish failed <html><head> | |
npm ERR! publish failed <title>502 Bad Gateway</title> | |
npm ERR! publish failed </head><body> | |
npm ERR! publish failed <h1>Bad Gateway</h1> | |
npm ERR! publish failed <p>The proxy server received an invalid | |
npm ERR! publish failed response from an upstream server.<br /> | |
npm ERR! publish failed </p> | |
npm ERR! publish failed <p>Additionally, a 400 Bad Request | |
npm ERR! publish failed error was encountered while trying to use an ErrorDocument to handle the request.</p> | |
npm ERR! publish failed </body></html> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mt@kodachi:~/node-graylog2 (node-graylog2.git::master)$ /nvm/v0.10.25/bin/npm publish | |
npm http PUT https://registry.npmjs.org/graylog2 | |
npm http 403 https://registry.npmjs.org/graylog2 | |
npm http PUT https://registry.npmjs.org/graylog2 | |
npm http 403 https://registry.npmjs.org/graylog2 | |
npm ERR! publish Failed PUT 403 | |
npm ERR! Error: forbidden Cannot replace previously published version: 0.1.2: graylog2 | |
npm ERR! at RegClient.<anonymous> (/nvm/v0.10.25/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:275:14) | |
npm ERR! at Request.self.callback (/nvm/v0.10.25/lib/node_modules/npm/node_modules/request/request.js:123:22) | |
npm ERR! at Request.EventEmitter.emit (events.js:98:17) | |
npm ERR! at Request.<anonymous> (/nvm/v0.10.25/lib/node_modules/npm/node_modules/request/request.js:893:14) | |
npm ERR! at Request.EventEmitter.emit (events.js:117:20) | |
npm ERR! at IncomingMessage.<anonymous> (/nvm/v0.10.25/lib/node_modules/npm/node_modules/request/request.js:844:12) | |
npm ERR! at IncomingMessage.EventEmitter.emit (events.js:117:20) | |
npm ERR! at _stream_readable.js:920:16 | |
npm ERR! at process._tickCallback (node.js:415:13) | |
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 2.6.18-308.11.1.el5xen | |
npm ERR! command "/nvm/v0.10.25/bin/node" "/nvm/v0.10.25/bin/npm" "publish" | |
npm ERR! cwd /home/mt/node-graylog2 | |
npm ERR! node -v v0.10.25 | |
npm ERR! npm -v 1.3.24 | |
npm ERR! | |
npm ERR! Additional logging details can be found in: | |
npm ERR! /home/mt/node-graylog2/npm-debug.log | |
npm ERR! not ok code 0 |
I have been trying to publish a package since a few hours .. the same problem
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
happening to me as well, but I'm on Windows 7 64bits and Node 0.10.26 / NPM 1.4.4, couldn't find anyone else suffering from the same issue on the entire internet, I looked