Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Dashboard error gadget.common.error.500


after all the updates on the way from JIRA V6.1 to JIRA V8.4 I got an error on the dashboard of the activity stream gadget "gadget.common.error.500".

Also this error I found in error.log:

2019-09-11 09:00:58,224 http-nio-8080-exec-11 ERROR jira_admin 540x632x2 1jmz0yk  /plugins/servlet/gadgets/makeRequest [c.a.g.r.internal.http.HttpClientFetcher] Unable to perform a request to: https://<domain>/jira_neu/rest/webResources/1.0/resources

JIRA works behind an Apache proxy and both are configured like

SSL certificate is signed and imported correctly in Apache.

Whats going wrong here?


2 answers

1 accepted

3 votes
Answer accepted
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 18, 2019

Hello Heiko,

Sorry to hear you are facing a problem.

Per the description of your error, it seems that you are being impacted by the problem mentioned in the article below:

Jira activity stream gadget throws gadget.common.error.500

basically, an invalid or absence of a certificate can lead to such errors. Could you please double-check if you are using the correct certificate? Also, check if the correct baseUrl is set in the System -> General Configuration.

If that's not the problem, I checked another customer facing the same problem after configuring direct SSL with self-signed certificates in JIRA 8.0.1 tomcat. As you can see in this thread, he managed to fix it by adding his self-signed ca and server certificates to tomcats JRE Keystore:

keytool -importkeystore -destkeystore cacerts -srckeystore /opt/certs/servkeystore.p12 -srcstoretype pkcs12 -alias tomcat -deststorepass changeit -srcstorepass <yourstorepass> -validity 3650
keytool -importkeystore -destkeystore cacerts -srckeystore /opt/certs/keystore.p12 -srcstoretype pkcs12 -alias ca -deststorepass changeit -srcstorepass <yourstorepass> -validity 3650

Let me know if those suggestions work for you.

Hello Petter,

in point of fact, it was the missing certificate. I found it out yesterday!

But: My original problem was, that on the server is also installed Java. So the default TrustStore was located in the Java directory and not in the JRE Directory of JIRA.

In the first step I uninstalled Java, put the server certificate in the TrustStore and it works!

Thanks a lot, now we can start to mirgrate JIRA 6.1 to 8.4 ;-)

My references:


Like # people like this
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 19, 2019

Thank you for providing us the steps you took to solve your problem, Heiko!

Have a nice day and please don't hesitate to contact us again in case you need any help!

Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 18, 2019

Thanks, it helps to me as well

So, apropos of this, I have a question.

Our Jira instance sits behind a proxy. SSL is terminated at the proxy server, not on the Jira server. The SSL certificates we use are Let's Encrypt certificates, and it's a bit of a pain to go grab the certificates and add them to Jira's keystore every three months. Is there another option for people whose Jira instance sits behind a proxy? Thanks

Like # people like this


We are using Active Directory CA for our certificate and we made sure to import our root CA certificate into the JKS file. The certificate is a wildcard certificate for our domain.

Reading the answer by Petter we checked the certificate using the curl -v and found that the server doesn't have our root CA installed so we planted it in /usr/local/share/ca-certificates and ran sudo update-ca-certificates and restarted Jira.

Though it solved other issue we have, it did not solve the gadget.common.error.500 message in the dashboard.

We are after an upgrade to Ubuntu 20.04 LTS and Jira Server 8.5.5.




I've got the same problem in my Jira installation. My Jira instance is created using docker-compose, but temporarily without valid SSL certificates, I will have it soon. Is there any way to enter these certs by running modified docker-compose script? If so, what should I put to my script?

TIA :)


Suggest an answer

Log in or Sign up to answer