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: 

gadget.common.error.500 jira system dashboard

Jason Ladew
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!
January 17, 2020

Im getting this error on my main system dashboard after upgrading to the 8.4.1. we are not using nginx. just a https connection through server.xml. we dont have a firewall in place and the server cant curl the base url.

 

I checked the Altassian knowledge base and I couldn't find an answer that would help me.

 

Thank you  

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

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 Champions.
January 19, 2020

This happens when your server cannot reach itself over your network - your statement "the server can't curl the base url" is caused by the same thing.

You will need to configure the network and/or server so that it can see itself.  This is not something Atlassian related, it is purely down to your networking.  You'll need to make the server name resolvable by and not firewalled or blocked to itself.