Forums

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

Unable to create Jira site – site URL creation fails and support form requires a URL

Adil Gurra
August 3, 2026

Hello,

I have just signed up for Atlassian/Jira, but I cannot complete the creation of my Jira site.

Whenever I try to create the site, I receive the following error:

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

Trace ID: ba390f33c7e141d5b79742f7933bbea1

Date and time of the error: 3 August 2026, approximately 17:35 Europe/Tirane

Attempted site name: procura-al
Expected site URL: https://procura-al.atlassian.net

I have tried again several times, but the same error continues to appear. No Jira site or site URL is created.

I also tried contacting Atlassian Support, but the support form requires me to enter my Atlassian site URL. Since the site creation itself is failing, I do not have a valid site URL and therefore cannot submit the support request.

Could an Atlassian employee please investigate the Trace ID, check whether there is a provisioning issue with my account, and create an internal support ticket for this problem?

Thank you.

1 answer

0 votes
Thanasis Nikolaou
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 3, 2026

Hey @Adil Gurra 

Nobody here on the community side can look up a Trace ID — that needs an actual Atlassian support ticket, so the real problem is getting past the form. A few things that have worked for others in this exact spot:

  • Use the purchasing/billing contact form at atlassian.com/company/contact/purchasing-licensing — it doesn't require a site URL, and signup/provisioning problems submitted there get rerouted to the right team. Paste the Trace ID and timestamp exactly as you have them here.
  • Before that, check admin.atlassian.com and start.atlassian.com while logged in — occasionally the site half-provisions and is actually sitting there.
  • Retry in an incognito window, and try a different site name once. A name that's tied up by a recently deleted site can fail with this generic error instead of the usual "name taken" message.

If the different name works, the issue is the procura-al name specifically, and support can release it for you.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events