It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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?


1 answer

1 accepted

0 votes
Answer accepted

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

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!

Thanks, it helps to me as well

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

260 views 1 2
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you