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

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

Gadget feed URL not working Edited

Hi,

We upgraded this week from 6.4 to 8.2.1 and then enabled SSL. For some reason some of the home page gadgets dont work now.

We also setup nginx to proxy in the front. JIRA and NGINX have SSL and config is as follows.

NGINX

server {
listen 80 default_server;
listen [::]:80 default_server;
server_name _;
return 301 https://track.example.com;
}

server {
server_name track.example.com;
listen 443 ssl http2;
ssl on;
ssl_protocols TLSv1.2;
ssl_certificate /etc/httpd/ssl/example.com/STAR_blah_com.crt;
ssl_certificate_key /etc/httpd/ssl/example.com/example.com.key;
access_log /var/log/nginx/nginx.access.log;
error_log /var/log/nginx/nginx.error.log;
charset utf-8;
location / {
proxy_pass https://track.example.com:8443;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP $remote_addr;
proxy_redirect off;
# If you want to accept attachments larger than 10mb, update the following line
proxy_connect_timeout 30s;
client_max_body_size 50M;
}
}

JIRA server.xml

<Connector port="8443" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
SSLCertificateFile="/etc/httpd/ssl/example.com/STAR_example_com.crt" SSLEnabled="true"
SSLCertificateKeyFile="/etc/httpd/ssl/example.com/blah.com.key"
SSLCACertificateFile="/etc/httpd/ssl/example.com/STAR_example_com.ca-bundle"
acceptCount="100" disableUploadTimeout="true" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;" scheme="https" secure="true"
proxyName="track.example.com" clientAuth="optional" SSLProtocol="TLSv1.2" proxyPort="443" />

instance_health.PNGbaser_url.PNGhome_page_gadgets.PNG

2 answers

1 accepted

0 votes
Answer accepted
Andy Heinzer Atlassian Team Jun 05, 2019

Hi,

I understand you upgraded Jira from a 6.4 version up to a 8.2 version and since that time the gadgets are not working correctly.   That's a very big upgrade jump to make. For the record we recommend that all Jira versions such as 6.4 and earlier first upgrade to a 7.0.x version before then upgrading to the latest versions.   There are a lot of significant changes in Jira 7.

That said, these two errors are very likely directly related.  Please see the KB How to fix gadget titles showing as __MSG_gadget.   This problem was very common to see for Jira sites starting with the 7.1.0 version of Jira. In this version Jira started to more strongly implement the requirement for the Jira application to be able to reach its own base URL address.  This is used as a means to optimize performance of dashboards and in turn it allows Jira to off-load some of the load to the clientside browser when rendering these gadgets.

That KB explains that there are lots of possible specific causes for this.  But all of them have a common theme: Jira can't reach its own address over your network.   I've seen that caused by routing rules for outbound traffic from the Jira Server itself, or SSL certificate issues.   I suggest trying the diagnosis steps in the KB to help narrow down the cause:

 

  • From the Jira server itself, Jira is unable to communicate with itself via its Base URL (Run curl -v <base_url> to verify)
  • 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

 

The results of these steps should be able to help us narrow the focus here.

Regards,

Andy

Sorry I forgot to answer back. I got it working. when I did curl https://myurl.com I got CA errors. Was using our five year Comodo wildcard SSL which was due to expire next month so got a new one then it worked. guess the old CA cert was not there.

Thank you for the solution!

For maybe others like me: Remember to restart jira!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Software

How to create Jira issus from Excel file?

When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...

4,528 views 22 32
Read article

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