Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to reindex when login is blocked?


We exceeded the number of commiters allowed by our license.

We reduced the number by mapping multiple instances of same committer to one.

But, I think we need to re-index for the above to take effect.

However, I am unable to log in to re-index. Logins appear to be disabled.

What to do?



p.s. note we share username/password between jira and fisheye and I am admin on both.

1 answer

0 votes

Hi @arthur karton,

You are correct that a re-index is required after the history has been rewritten. Here is our guide for Mercurial and Git repositories on this topic:

- Git or Hg Repository exceeds number of allowed Committers


Regarding the login, did you already try to use the administrator password?

Note: this is not a username and you can enter this password by browsing to the http://<FECRU_URL>:<FECRU_PORT>/admin/ URL.


If you don't remember it, this is how it can be reset:

How to reset the Administration Page password in FishEye or Crucible



Caterina - Atlassian

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

#JiraHeroes May '22 Spotlight: Daniel Cave

At Atlassian, we take great pride in the software we ship, and even greater pride in the success our customers achieve when they use our products. #JiraHeroes is our new monthly spotlight series&nbsp...

857 views 0 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you