nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA is not able to access itself

Cosylab IT

Greetings,
I get the following warning in the Troubleshooting and support tools part of the system backend:
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 went trough the troubleshooting process but all the tests were good. Also the dashboard gadgets work.
Can the issue identified by this warning, produce any other problems, or can we safely ignore it?

Best regards
Lovrenc Avsenek

Accepted answers

Andy Heinzer

It is possible that this is a false positive, but it's difficult to say that for sure. What version of Jira are you using?

Is your Jira utilizing a reverse proxy and/or SSL? I am curious if you can share what URL your Jira site is accessible at, say something like jira.example.com and then see if that is set as the current Base URL in the system settings, as well as what values you might have in the <connector> tags of your $JIRAINSTALL/conf/server.xml file. This file contains the settings that Jira's tomcat webserver will use to host the site. If you're redirecting traffic to this site via a reverse proxy then there are expected to be parameters here such as proxyName, proxyPort, and scheme that should be defined here as per Proxying Atlassian server applications with Apache HTTP Server (mod_proxy_http).

Cosylab IT

I have done this tests before, but I haven't done the SSL poke from the Jira server directly - which turned out out be where the issue was.

I have added the CA cert to the java trust store and the SSLPoke worked, also the warning is gone now.

Thank you for the assistance.

All comments

Andy Heinzer

It is possible that this is a false positive, but it's difficult to say that for sure. What version of Jira are you using?

Cosylab IT

Hi Andrew,

The details are as follows:

software version: v7.12.0#712001-sha1:ad166f5
Yes, the jira installation is behind a web proxy.
And yes, it is using SSL.

Connector:

        <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"          
        proxyName="support.cosylab.com"
        proxyPort="443"                
        scheme="https"                 
    />

The base url is https://support.cosylab.com, which is also the address on which the site is reachable.

Does Jira perhaps use web-sockets to keep it's widgets updated?

Andy Heinzer

This part of your configuration looks ok to me. Jira is expected to try to reach the base URL from the application itself. In some environments, the network interface the Jira application is using isn't able always to make outbound network connections to addresses like the base url. In cases like that the site can still appear to work for the most part, but functions like dashboard gadgets can't render properly.

I would be interested to see if you can take a closer look at this KB that highlights this problem we started seeing in Jira versions 7.1.x and above. How to fix gadget titles showing as __MSG_gadget

Maybe you are not seeing this exact __MSG_gadget for the titles of your gadgets, but it could still be helpful for you to try to follow the diagnosis steps on that page to better understand your environment.

For example these three tests could provide us more info at the very least:

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

I'm not yet 100% certain if Jira is using websockets, but from my initial investigation it does seem as though this could be possible.

Cosylab IT

I have done this tests before, but I haven't done the SSL poke from the Jira server directly - which turned out out be where the issue was.

I have added the CA cert to the java trust store and the SSLPoke worked, also the warning is gone now.

Thank you for the assistance.

Alexander Zorg

Hi, can u describe how did u add CA cert to ur existing keystore?

Peter Boyle_ou2szn

following.....

Niek Neuij

You add it on the Jira origin server (not the proxy) like this:

keytool -v -importcert -keystore /opt/atlassian/jira/jre/lib/security/cacerts -storepass changeit -file ~/WILDCARD_example_com.crt

dujas

Hi Andy,

I am sufferring this warning as well.

SSLPoke test did fail on both jira servers and proxy server, do I have to add the pem/crt file to the jira server's cacerts?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-service-desk

jira-service-desk-server