-
Notifications
You must be signed in to change notification settings - Fork 3k
Changing my password at npmjs.org has corrupted access from my server #2770
Comments
I have to use the username "PrettyDiff" to log into the account from the website, but the command line will not allow uppercase characters. When I do log into the website it is confused as to whether my account name is "PrettyDiff" or "austincheney" and then it always logs me into a password reset screen. |
Which account would you like to use? It's a requirement to use all-lowercase names now. Old ones were grandfathered in, but npm won't let you set up a new account with those. Step 1: Use npm 1.1.61 and node 0.8. Not version 0.2.x and 0.3.x, which are ancient, and no longer supported by me or the main npm registry. Step 2: Pick an all-lowercase name you'd like to use. Step 3: Tell me what name that is, and I'll reset all your packages to be on that account instead of PrettyDiff. |
Classification: UNCLASSIFIED I would like use the account name "austincheney". Thank you very much, On 09/10/12, "Isaac Z. Schlueter" notifications@github.com wrote:
|
Ok, @austincheney, you're all set. |
Classification: UNCLASSIFIED Austin On 09/12/12, "Isaac Z. Schlueter" notifications@github.com wrote:
|
I've got the same issue, nevertheless, I already published a repository with a new user account. So there's now Gottox and gottox in npmjs. Can I merge my old projectes to the new account and how to delete the old one? |
error from my server:
mailmark@mailmarkup.org [~/public_html]# npm adduser
Username: (austincheney) PrettyDiff
Password: ()
Email: (austin.cheney@us.army.mil) austin.cheney@us.army.mil
npm info it worked if it ends with ok
npm info using npm@0.2.12-1
npm info using node@v0.3.2-pre
npm WARN Sending authorization over insecure channel.
npm ERR! adduser Error: conflict Document update conflict.: -/user/org.couchdb.user:PrettyDiff/-rev/1-d58f4c8dfcc668e3dcac80f9c9882f64
npm ERR! adduser at IncomingMessage. (/home/mailmark/node/lib/node/.npm/npm/0.2.12-1/package/lib/utils/registry/request.js:140:16)
npm ERR! adduser at IncomingMessage.emit (events.js:48:20)
npm ERR! adduser at HTTPParser.onMessageComplete (http.js:110:23)
npm ERR! adduser at Client.onData as ondata
npm ERR! adduser at Client._onReadable (net.js:573:27)
npm ERR! adduser at IOWatcher.onReadable as callback
npm ERR! Error: 409 Could not create user Error: conflict Document update conflict.: -/user/org.couchdb.user:PrettyDiff/-rev/1-d58f4c8dfcc668e3dcac80f9c9882f64
npm ERR! {"error":"conflict","reason":"Document update conflict."}
npm ERR! at /home/mailmark/node/lib/node/.npm/npm/0.2.12-1/package/lib/utils/registry/adduser.js:78:13
npm ERR! at IncomingMessage. (/home/mailmark/node/lib/node/.npm/npm/0.2.12-1/package/lib/utils/registry/request.js:144:14)
npm ERR! at IncomingMessage.emit (events.js:48:20)
npm ERR! at HTTPParser.onMessageComplete (http.js:110:23)
npm ERR! at Client.onData as ondata
npm ERR! at Client._onReadable (net.js:573:27)
npm ERR! at IOWatcher.onReadable as callback
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.
The text was updated successfully, but these errors were encountered: