There were too many redirects.

We all just started getting this today when logging into JIRA.

Ver 5.6.2, hosted locally.

Any ideas what's up?

7 answers

1 accepted

1 vote
Accepted answer

Problem seems to have gone away.

That is not the same thing as saying it is fixed, however.

I'm getting the same with Jira 6. I presume I've botched something locally, but it used to work..

Received the following e-mail this morning. But none of the choices apply.

- There is no answer to accept

- I have no answer to give

- The question is clear

- The question is still valid


The following questions of yours are still unresolved:

Please consider one of the following actions:

  • Accept an answer (click the grey check mark)
  • Answer your own question, then accept your answer (find the 'Answer my own question' link underneath your question)
  • Edit your question for clarification
  • Add a comment for more information from an existing answer
  • Close the question, if it's invalid

Please be a good Answers citizen!

Accepting answers on resolved questions earns you Karma points, and increases the chances that Answers' top contributors will answer your future questions. If your question is still legitimate and you'd like to await further answers, please do!

Have you cleared your browser's cache? This is the most usual cause for this. Another cause is a programming error (i.e. infinite loop of redirects to the same pages), but this is not reproductible on my environments ....

The log shows that I am not the only one generating this error.

Curiously if you inspected the network traffic and visited the URL directly it would do the same.

The problem has been resolved as of at least yesterday.

I supect it was a problem with their server configuration.

We had the same problem with our Confluence Server.

Digging a little bit deeper we found two JSESSIONID cookies in the browser, the first (invalid) for the first page visited by the user (with cookie path "/pages/"), the second (good) JSESSIONID cookie for the login (with cookie path "/"). Both cookies were sent with Path = "/" by Tomcat but all browsers ignored this cookie path parameter.

The root cause was a Tomcat setting:


This setting (among others) changes the session handling in Tomcat.  We have removed this setting from Tomcat and the problem disappeared after a restart.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,047 views 4 9
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you