Why am I missing gadget metadata?

[Chris Nelson]

We recently migrated from Jira Server v6.<something> running locally to Jira Server v7.11.1#711001 running in AWS.  I had nothing to do with the migration but I'm trying to pick up some pieces that got broken in the process.

The symptom I'm chasing right now is I can't add gadgets to dashboards.  For example:

• I navigate to Dashboards -> My Dashboard
• Click "add a new gadget"

• Click "Load all gadgets"

The Bubble Chart and Introduction gadgets look fine but I see things like "__MSG_gadget.filter.results.description__" and "__MSG_gadget.activity.stream.title__" on all the rest of the gadgets.

I'm aware of the KB article on what seems to be this topic but none of the causes listed there seem to be present in my installation.

[Andy Heinzer]

Hi Chris,

When you run the curl command, are you doing this from the instance running Jira itself?  I ask because the gadget error you see there tends to happen when the Jira application is unable to reach the base URL set for the site for some reason or another.  Sometimes this is because of a routing problem, or the interface Jira is using might have it's http/https outbound requests going through a proxy.   It can be harder to diagnose, because other end users might have no problem reaching the site, but this doesn't necessarily mean that the Jira application has the ability to reach its own site with the network settings it currently has.

In addition to using curl to test this out, there are also other utilities to can try to use from the server running Jira to get more details about this problem:

• Run SSLPoke from the JIRA server itself and see if it returns successfully
• Additionally run the httpclienttest from the JIRA server itself to confirm if the SSL configuration is okay, as this will verify if you're affected by  JRASERVER-47568 - JIRA complains about SNI host Closed

Are you using SSL with Jira? 

[Keri]

Hey Chris,

We’ve seen cases users have had to add a specific rule into their AWS security to allow the Base URL to communicate back to itself.

If you run a curl command against your base url, do you have any errors returned?

curl –v <BASE URL>

Cheers,

Keri

[Chris Nelson]

No, that works.  

curl -v <base url>

shows a web page and adding `>/dev/null` shows some characteristics of the connection but nothing that looks like an error.

[Chris Nelson]

This is still a problem for us.  As noted above, `curl` on the server finds the base URL without a problem.

Reviewing other, old answers about related issues, I see advice to disable and reenable the Steams Plugin.  I've done that before but stumbling around to see if I see something new, I find the version for that plugin and several other System plugins is 6.4.3.  Our Jira Server version is v7.11.1.  Is that a mismatch?  I'd expect the system plugin versions to track the system but maybe I'm wrong.  If iit's a mismatch, how do I get the current plugin version?