npm adduser returns not_found missing incorrectly

[asilluron]

npm http PUT https://registry.npmjs.org/-/user/org.couchdb.user:asilluron
npm http 409 https://registry.npmjs.org/-/user/org.couchdb.user:asilluron
npm http GET https://registry.npmjs.org/-/user/org.couchdb.user:asilluron
npm http 404 https://registry.npmjs.org/-/user/org.couchdb.user:asilluron
npm ERR! Error: not_found missing: -/user/org.couchdb.user:asilluron
npm ERR!     at RegClient.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:272:14)
npm ERR!     at Request.self.callback (/usr/local/lib/node_modules/npm/node_modules/request/request.js:129:22)
npm ERR!     at Request.EventEmitter.emit (events.js:98:17)
npm ERR!     at Request.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/request/request.js:873:14)
npm ERR!     at Request.EventEmitter.emit (events.js:117:20)
npm ERR!     at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/request/request.js:824: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 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 12.3.0
npm ERR! command "node" "/usr/local/bin/npm" "adduser"
npm ERR! cwd /Users/######
npm ERR! node -v v0.10.21
npm ERR! npm -v 1.3.13
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/npm-debug.log
npm ERR! not ok code 0

I can login via npmjs.org

OSX: 10.8.3
Node: v0.10.21
NPM: 1.3.13

[asilluron]

Just replicated on Windows 7 as well with node 0.8.x

[woodb]

Replicated on Mac OS X 10.9 as well. I can login to npmjs.org just fine, though it feels extremely slow.

node --version; v0.10.22
npm --version; 1.3.14

Will add, this is a new account, could replication be slow?

Edit: appears to be working now, according to NPM's Twitter account they have been having server troubles lately.

[smikes]

Is this still a problem for you?

This seems to have been a problem caused by the older registry; since November 2013 the registry code has been updated and the registry is now hosted differently.

We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and open a new issue!)

Thanks!

[othiym23]

Closing as resolved / abandoned.