The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Cloud site creation fails with generic backend error

Vikirna Majumdar
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 31, 2026

I'm trying to create a new Jira Cloud site (via the standard signup flow) but it fails every time with:

"Something went wrong on our end. Please try again. If this keeps happening, contact support."

I've tried:
- Multiple site names (including ones confirmed available)
- Retrying multiple times
- Different browser / incognito

Trace ID: 0517b6c7e5044609ad72b5765a400f94

This happens on the site-creation step itself, so I don't have an existing site, SEN, or EN yet. Any idea what's causing this or how to get past it?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Varun Chillamcharla
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 31, 2026
 
I've seen this exact error reported a few times over the past several days, so it's not isolated to you, genuine backend issue during site provisioning. No active incident on status.atlassian.com today, though there was a broader resolved Jira Cloud/JSM/Confluence disruption on Aug 27.
 
Since you've already ruled out the usual culprits, this needs Atlassian Support at this point, they can trace it using your ID (0517b6c7e5044609ad72b5765a400f94): https://support.atlassian.com/contact/
 
Worth mentioning in your ticket that others have hit the identical error recently too.
TAGS
AUG Leaders

Atlassian Community Events