gadget.common.error.500

Noam Lugasi_xjtpw2

We have completed an upgrade to Ubuntu 20.04 LTS and Jira Server 8.5.5. and we have this issue in our system dashboard loading the Activity Stream plugin. We see the error message "gadget.common.error.500" whenever the gadget is loading.

We have Active Directory CA and we produced a wildcard cert for the JKS but we also included the root CA inside the JKS file and in /usr/local/share/ca-certificates/

running curl -v https://jira.ourdomain.com returns "SSL certificate verify ok" so we're quite sure the JKS file and the cert are ok.

We also tried to add the jira.ourdomain.com name in /etc/hosts with the internal IP address as was suggested somewhere and we tried to disable/enable the "Streams Plugin" and re-index and that didn't help either.

Please assist,

Noam.

Earl McCutcheon

Hello @Noam Lugasi ,

Thanks for reaching out and the behavior you are describing defiantly sounds like a invalid or missing certificate issue described in this KB, noting modifying the cert may be a possible solution:

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

I recomend Generating a HAR file as detailed in the KB and looking to see if a matching error is coming up, with a Note of caution do not post the Har file here as it will contain detailed information about your connection that should not be made public, if you need assistance looking over the file contact atlassian Support in the private help desk at support.atlassian.com:

• Generating HAR files and analyzing web requests 

If that's not the problem, checked the following thread where another customer was facing the same problem. He managed to fix it by adding a new self-signed ca and server certificates to tomcats JRE Key-store, basically modifying the cert as mentioned in the KB above as there was an error with the previous cert config:

• https://community.atlassian.com/t5/Jira-Questions/Dashboard-error-gadget-common-error-500/qaq-p/1175383

But if this does not yield any results either, I am wondering if there may be a permissions issue in the directory structure post upgrade causing the application to not be able to see the certificate.

Check out the following KB article and run the permissions modification to verify everything is in order in the file paths:

• How to fix directory permissions in Linux for Jira Server

Regards,
Earl