Hi,
This is a generic error that usually indicates a temporary loading or connectivity issue rather than a specific problem with your content.
You can try the following:
* Refresh the page or open it in a new tab
* Clear browser cache/cookies
* Try an incognito/private window
* Disable browser extensions (especially blockers)
* Try a different browser or network
* Check the Atlassian Status page for any ongoing incidents
If the issue persists for multiple users or over a longer period, contact your site admin or Atlassian Support.
Hope this helps 👍
Hi @Braham Dev
That “Something’s gone wrong” banner in Jira Cloud is unfortunately a very generic UI failure message, it usually means the page couldn’t load one of the required resources (auth/session, an app iframe, a blocked script, or a permission-protected API call).
A good way to troubleshoot it is to isolate whether it’s browser/session related vs Jira/app/site related.
1) First, rule out cookies/cache/extensions (very common)
Because Jira Cloud relies heavily on cookies for session/auth (and many Marketplace apps rely on iframe-based content), cookies and browser privacy settings can absolutely trigger this.
Try opening the same URL in an Incognito/Private window.
If it works there → it’s almost always cookies/cache or a browser extension issue.
If incognito works, try:
Clear cookies + site data for your Jira domain (e.g. yourtenant.atlassian.net) and Atlassian login domains (e.g. id.atlassian.com) and retry
Temporarily disable ad/tracking blockers (uBlock, Ghostery, Brave Shields, etc.)
If you’re on Safari/Firefox/Brave, try Chrome or Edge (less strict tracking protection by default)
2) If this is a Marketplace app page / embedded content
If the error happens when opening an app page (or something embedded in Jira), stricter privacy settings can block third-party cookies or iframe resources. In that case:
Allow third-party cookies for that site (or make an exception)
Disable “block cross-site tracking” / enhanced tracking protection for the Jira site
Re-test in Chrome/Edge
3) Check whether it’s user-specific or site-wide
Does it happen only for you, or for multiple people?
Only you → points to browser/session, permissions, or account-specific issue
Multiple users → could be an app outage, a Jira incident, or a network/security control blocking traffic
4) Quick technical signal (fastest way to pinpoint)
If you can, open browser DevTools and refresh once:
Console: look for the first red error (often CSP/CORS, blocked script, or auth failure)
Network: look for failed requests (401/403/5xx)
401/403 → auth/permissions issue
CSP/CORS → security policy / blocked cross-site resource
5xx → service or app backend issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.