Forums

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

gadget.common.error.500

Соловцов Александр
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!
December 3, 2019

Hello! Can anyone tell me what to do with this mistake?

1 answer

0 votes
Nic Brough -Adaptavist-
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 Leaders.
December 3, 2019

Your Jira server is somehow not able to talk to itself over your network.  It can't resolve its own server name, or has been firewalled off from itself.

Try a "trace route" from the Jira server back to itself.  This will usually tell you why it can't see itself.

Соловцов Александр
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!
December 3, 2019

Thanks for your answer!

Can you give me more information what i need to check step by step.

I am trying to resolve this a littele trouble more than 3 months

Nic Brough -Adaptavist-
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 Leaders.
December 4, 2019

Log into the server and test the routing back to itself.

If, for example, your Jira base url is "https://dave/jira", then try simply "curl https://dave/jira".  I expect you will get an error or a block of text that is an error message, either of which will tell you what is wrong (can't resolve the name, doesn't respond, responds with an invalid url, etc)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events