Unable to login to JIRA

[Kota Sreenivasa Shravana Kumar]

Few users are getting the following error while logging into JIRA. Any help is appreciated.

Sorry, your userid is required to answer a CAPTCHA question correctly

Thanks

[jayasingh · Accepted solution]

Login as admin-click on administration-then click on users-then enter the user name those unable to login- then click on Reset Failed Login Count. once u reset ask the user to login with his credentials. hope this will work.

Thanks,

Jai

[Udo Brand]

It seems your JIRA is set up with "CAPTCHA on signup" is set to ON. Please see here

[Renjith Pillai]

Shravana,

Is this resolved?

[Kota Sreenivasa Shravana Kumar]

Thanks everyone. This issue has been resolved.

[Tran Tien Dung]

I cannot login by admin user, it keep require insert Captcha, even I type correct, how to fix it.

[Henning Tietgens]

This might be a cookie problem. See here: https://confluence.atlassian.com/jirakb/the-jira-application-login-is-stuck-on-captcha-validation-457703732.html

Henning

[Alexander Rosenberg]

Even after clearing cookies, I still cannot login as the admin!

[Belinda Tinsley]

Has this been resolved? We have the same issue.

[Alexander Rosenberg]

Unfortunately, I never found a permanent fix or explanation.  I was able to regain access after clicking the forgot password link.

[Belinda Tinsley]

Okay, we cannot configure the email because we cannot login!

[Alexander Rosenberg]

I guess I was just lucky I had configured the outgoing email before running into this issue myself.

[Belinda Tinsley]

you are lucky! We will try to do it from the backend....

[Alexander Rosenberg]

Other than trying to restart JIRA, I don't think you have any other recourse but to contact Atlassian support.

[Belinda Tinsley]

yep, we have done it all.....multiple times.

[Alexander Rosenberg]

I feel for you.  Good luck!

[Belinda Tinsley]

We resolved our issues.

[Alexander Rosenberg]

Great! How? Were you able to configure outgoing emails?

[Belinda Tinsley]

Outgoing emails didn't work. Not sure why but we did hit EVERY brick wall! And are still working on additional issues with this project.

We updated the only user in the DB that had SYSADMIN priv, to have a new PW.