How to Fix Jira Login Screen Looping Back With No Error

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

This article addresses the issue where Jira users are repeatedly redirected back to the login screen without any error message, even when entering the correct username and password. Common causes include misconfigured SSL or proxy settings, browser cache or cookie problems, and inconsistencies in authentication configuration files.

Diagnosis

When logging into Jira you are sent back to the login screen with no error.

This issue starts occurring just after Jira has been upgraded.

Cause

  1. The browser cache has two values for JSESSIONID or if using Crowd, extra values for crowd.token_key.

  2. A software application firewall is blocking Jira.

  3. Multiple Atlassian products are using the same IP Address or hostname, and the same context path, but are listening on different ports. Due to the way the browser stores cookies, their session cookies step on each other, and sometimes that can lead to this issue happening.

Solution

Cause One: Clear your browsers cache and reconnect to Jira.

Cause Two: Ensure there are no software firewalls blocking Jira and the cookie JSESSIONID.

Cause Three: Change the context path of the different Atlassian products so that they are no longer using the same context path, see Logging into another Atlassian application logs me out of JIRA for more information.

Updated on June 4, 2025

Still need help?

The Atlassian Community is here for you.