Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Can't create an account. #119

Closed
trusktr opened this Issue · 28 comments
@trusktr

Every time I try to create an account, I get an error saying "There was a problem! The server said: Failed creating account. CouchDB said: not_found".

This is what I'm trying:
username: trusktr
password: VaLiDpAsSwOrD123 <--alphanumeric only
password: VaLiDpAsSwOrD123 <--alphanumeric only
email: jp@keepskatinbro.com

Everything is valid. Is the email address causing it?

@eu-ge-ne

+1 I'm getting the same error

@sitnin

Same here

@isaacs
Owner

Found the issue. Shoudl be fixed now.

@isaacs isaacs closed this
@sitnin

it works, thanks! )

@eu-ge-ne

Still getting this error: There was a problem! The server said: Failed creating account. CouchDB said: not_found

@dustMason

+1 also seeing this issue now

@isaacs isaacs reopened this
@isaacs
Owner

Ok, I can't reproduce this, and restarting the server seems to fix it, so it's kind of tricky.

To the next person who encounters this: Please view source, and look at the very last line. It'll be something like this:

<!-- pid=51791 worker=9 fbaabc9a75ac1080c0ab12332a1a5bb07fd57497 https://npmjs.org:10009 -->

Include that in the bug report, and it'll be a lot easier to track down. Thanks!

@nicholascloud

I am experiencing this issue now. Trying to create a new npm account, and I get the error:

There was a problem! The server said: Failed creating account. CouchDB said: not_found

Here is the HTML snippet you requested:

<!-- pid=56741 worker=236 9b7439041220d0731993b73086be5537a341f2b7 https://npmjs.org:10036 -->
@simoncrabtree

I get this too;
There was a problem! The server said: Failed creating account. CouchDB said: not_found

pid=9630 worker=17 444b221 https://npmjs.org:10017

@ullmark

Yep, getting it too!

<!-- pid=99400 worker=117 b0e7ee8e51f81c84e1eed567f63c704b322d12d4 https://npmjs.org:10017 -->

@isaacs
Owner

Ok, tracked this down to a bug in couchdb that results in the admin account getting its token prematurely invalidated.

Just restarted the cluster, so it should work for the next week or so until I get a chance to put a workaround in place. Sorry for the inconvenience.

@ullmark

@isaacs Thanks NP, I was able to create my account yesterdays!

@nicholascloud

Yup, I got my registration to go through last week as well. Glad you tracked down the culprit, though.

@jorritd

I do not want to spoil the party but again "There was a problem! The server said: Failed creating account. CouchDB said: not_found"

@kitsonk

Getting it too...

<!-- pid=33938 worker=67 b0e7ee8e51f81c84e1eed567f63c704b322d12d4 https://npmjs.org:10067 -->
@nkuttler

Same problem

<!-- pid=72469 worker=5 7759ed21d5d6da24f50ff0a3ce6e41d6f898d116 https://npmjs.org:10005 -->
@CMTegner
<!-- pid=93125 worker=6 7759ed21d5d6da24f50ff0a3ce6e41d6f898d116 https://npmjs.org:10006 -->
@vizio360

still can't create account

<!-- pid=67935 worker=13 7759ed21d5d6da24f50ff0a3ce6e41d6f898d116 https://npmjs.org:10013 -->
@obradovic

Hi there, same issue. Just piling on, I guess ;)

<!-- pid=68179 worker=9 7759ed21d5d6da24f50ff0a3ce6e41d6f898d116 https://npmjs.org:10009 -->
@lafikl

got it too

<!-- pid=41531 worker=11 7759ed21d5d6da24f50ff0a3ce6e41d6f898d116 https://npmjs.org:10011 -->
@CMTegner

Not sure if you want us to continue to post these, but I'm still getting the same problem today:

<!-- pid=69031 worker=12 7759ed21d5d6da24f50ff0a3ce6e41d6f898d116 https://npmjs.org:10012 -->
@obradovic

@all fyi things seem to work on the command line - npm adduser

@CMTegner

@obradovic thanks for the tip!

@nkuttler

Thanks obradovic! That works indeed.

@christiangenco

@obradovic's tip of using npm adduser worked for me because that actually showed the error I was having in signing up for an account:

npm WARN adduser Incorrect username or password

From the web, I was getting no error - it would just show me a blank account creation form again. I tried another username and it worked (the one I was trying was taken).

@rockbot
Owner

@christiangenco is this still an issue? Since your comment is from 7 months ago, I'm hoping it's been fixed and i'm going to close this issue - if that's not the case, feel free to reopen!!

@rockbot rockbot closed this
@christiangenco

@rockbot The web interface looks like it still doesn't show errors, so it's still an issue (though perhaps a separate one?).

@rockbot
Owner

Yes, please create a separate issue, and we'll look into it!

Thanks :-D

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.