Jira Logon Failed

[최용구]

Hello. We are using the free version, and when one of our team members attempts to log in to an account with specific space permissions, the login screen keeps spinning indefinitely before displaying the following screen.

We are unsure whether this is something we can resolve ourselves or if Atlassian needs to take action, so we are reaching out.
We would appreciate your response. Thank you.

[Arkadiusz Wroblewski]

@최용구  Hello 🤗 

This error looks much more like a login/session problem than a “space permission” problem.

A key detail is the Hash (17YZ5WN). That’s basically an internal reference Atlassian can use to find the exact failing request in their logs. So keep it and share it if you escalate.

Here’s what I’d try in a practical order (these fix most “spinning login → we ran into a problem” cases in Cloud):

1) Quick isolation test (fastest)

Try logging in with the same account in Incognito/Private mode.

Or try a different browser (Chrome ↔ Edge ↔ Firefox).

If it works in Incognito, the cause is almost always cookies/cache/extensions.

2) Cookies / tracking protection (most common cause)

Atlassian login relies on cookies and redirects (id.atlassian.com). If cookies or cross-site tracking are blocked, the login can spin forever.

Temporarily allow cookies (and if your browser blocks “third-party cookies”, try disabling that for Atlassian).

Add exceptions for: *.atlassian.com, *.atlassian.net, id.atlassian.com.

3) Disable extensions (ad/privacy blockers)

Extensions that block trackers/cookies/scripts often break Atlassian’s auth flow.

Disable ad blockers / privacy extensions (uBlock, Ghostery, etc.) and retry.

4) Clear site data for Atlassian only (not your whole browser)

Clear cookies/site data for:

atlassian.com

atlassian.net

id.atlassian.com Then retry login.

5) Network check (VPN / proxy / firewall)

If the user is on a corporate network/VPN, try:

turning off VPN

trying a different network (mobile hotspot)

6) If it still fails

At that point it’s reasonable to suspect an Atlassian-side issue for that account/session.

[Marc -Devoteam-]

Hi @최용구 

Has the user got a Confluence license, check the user in Atlassian Administration.

Can you or others login normally?

Can the user try another browser or incognito window?