Forums

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

Can't create an instance

cadida_austriacard
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!
March 13, 2026

Whenever I try to create an instance of Jira or Confluence, I get the following error:
Something went wrong on our end. Please try again. If this keeps happening, contact support. (Issue ID for Atlassian use: Trace ID: e50166b8075a47bfb2f6fdd43fbc6492)

I have tried on multiple days, with different browsers (firefox, chrome) and from different internet connections.

Since I can't create an instance, I'm not on a paid plan (or any plan) and I can't create a support ticket. The AI support chatbot told me to open a community questions since these are monitored.

I really would like to create a new jira and confluence instance, please help 

2 answers

1 vote
Arkadiusz Wroblewski
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.
March 13, 2026

Hello @cadida_austriacard 

based on what you wrote, this does not look like a local browser or network problem.

Since you already tested with different browsers, connections, and on multiple days, but still get the same error with a Trace ID, this looks more like an Atlassian-side provisioning issue.

As you currently cannot open a normal support ticket, I hope maybe a Moderator, Community Leader, or Atlassian team member can help flag this internally to support, because the Trace ID should help with investigating the failed site creation.

I cross my fingers for you 🤞

1 vote
Benjamin
Community Champion
March 13, 2026

HI @cadida_austriacard ,

 

Sorry to hear that. I've notice another post with some issue spinning up a Jira instance. Do you have screen shots or steps you went through to create the instance. I have create them many times in the past and had no issue.

I'll also request the Atlassian team incase it maybe a wider spread issue. For now, any further context and reproducible steps would help.

 

-Ben

Suggest an answer

Log in or Sign up to answer