gadget feed url health check failed

[Kevin_Leaverton]

Upgraded Jira and now getting "gadget feed url health check failed". Running in Windows environment. I've read articles, but I cannot figure out what is causing this.

Help please.

[Nic Brough -Adaptavist-]

The most common culprit is that the upgrade upgrades the JVM running Jira, which means the client SSL certificate keystore is replaced without a certificate that you applied when you moved to SSL.

Yes, I know, that's a lot of jargon and words to throw around.  The less jargon-y version is "when you set up SSL, there was a step that added stuff to a file in the Jira install.  You need to repeat that step".  Not sure that helps a lot either.

The error message you have is a bit wider - it means "I can't talk to myself over your network".  I'd say SSL is by far the largest problem here, but there are other causes.  Very simple test - log into your Jira server and try "curl <http(s)://yourjiraurl" (if no curl, try wget - it's not often we see an OS that doesn't have one or both).  You'll get a text file with, hopefully, quite a detailed error in it which can tell us a lot more.

[Kevin_Leaverton]

Thanks for the response, Nic.

The issue with SSL cert makes sense, however installing the cert did not change the situation. That's not to say that I installed the SSL cert correctly. I inherited this JIRA implementation after staff turnover and have not really laid hands on it before (dummies guide would be appreciated). 

I executed curl https://<myjiraurl> and received an error:
curl: (7) Failed to connect to <myjiraurl> port 443: Connection refused

[Nic Brough -Adaptavist-]

A connection refused error means your service probably isn't even listening on that port.

I've pointed to SSL as the most likely culprit, but it could be other things.  What, exactly, does your base url look like?  i.e. to get to your Jira, what's the simplest url?  For example  http://myserver.org:8080/jira .  Feel free to change the names of the servers to obscure them (so the one I just gave could be http://xxxxxxxx.xxx:8080/jira), we're interested in the structure of the url

[Kevin_Leaverton]

Got it resolved. The server.xml file had been replaced during the upgrade of Jira. I went back to the previous installation and examined the server.xml file. I noted the differences between the two and made updates to the newer version. It started working after a restart. 

Thanks for your help.