gadget.common.error.500

[Deleted user]

Hi, 

I updated Jira to lastest version 8.7, but got this message: gadget.common.error.500

Health check message: 

Warning

Gadget feed URL

What does this check do?

Checks if Jira is able to access itself through the gadgets feed URL to ensure that dashboard gadgets will work.

Result

Jira is not able to access itself through the Gadget feed URL. This is necessary so that dashboard gadgets can be generated successfully. Please verify the current Base URL and if necessary, review your network configurations to resolve the problem.

I have NGINX pointed to Jira server, settings as bellow: 

server.xml:

<Connector port="8080" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"
proxyName="jira.domain.xyz" proxyPort="443"/>

in NGINX:

server {
server_name jira.domain.xyz;
listen 443 ssl;

location / {
add_header Front-End-Https on;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;

proxy_pass http://jira.server.ip:8080;
proxy_read_timeout 90;

proxy_redirect http://jira.server.ip:8080 https://jira.domain.xyz;
}

ssl_certificate /etc/nginx/ssl/comodo/live/domain.xyz/domain.xyz.fullchain.crt;
ssl_certificate_key /etc/nginx/ssl/comodo/live/domain.xyz/domain.xyz.key;

I tried to check atlassian-jira.log but couldnt find anything special about gadget.

As I understand: Jira is able to access itself  is the cause. Trying curl -v jira.domain.xyz within jira server but not success. (other server work fine)

* Rebuilt URL to: jira.domain.xyz/
* Trying jira.server.ip..
* connect to jira.server.ip port 80 failed: Connection refused
* Failed to connect to jira.server.ip port 80: Connection refused
* Closing connection 0
curl: (7) Failed to connect to jira.server.ip port 80: Connection refused

Since it worked before updating, I tried copy everything from old server.xml but not success. 

Appreciate any help,

Peter

[Jobin Kuruvilla [Adaptavist]]

First create a filter and then subscribe to it.

https://confluence.atlassian.com/display/JIRA/Receiving+Search+Results+via+Email

For example, to get open issues for last one week with priority 'high', you can create a filter like this:

created >= -1w and resolution = unResolved and priority = "High"