Can't acces the Dashborad Warning Gadget feed URL

[Samuel Tinapp]

Hey

I have problems to configure Jira. I can't acces the dashboard.

The warning from Jira:

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.

My setup:

Jira-container, nginx-container, postgresql-container. All connected to a docker network. Only the nginx-container is accesable from outside through port 80.

docker run --name nginx -v $1:/etc/nginx/nginx.conf:ro -p 80:80 --network jira-conf-post-nginx -d nginx:1.1

docker run -d --name jira --network jira-conf-post-nginx -v $1:/var/atlassian/jira-app -v $2:/var/atlassian/jira-home jira

docker run --name postgres --network jira-conf-post-nginx -d postgres

nginx configuration:

worker_processes 1;

events { worker_connections 1024; }

http {

    sendfile on;

    upstream docker-jira {
        server jira:8080;
    }
    server {
        listen 80 default_server;

        location /jira {
                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_pass http://docker-jira/jira;
            client_max_body_size 100M;
        add_header X-Frame-Options ALLOW;
       }

    }

}

The interesting parts from jiras server.xml:

 <Connector port="8080"
           proxyName="42.4.92.179"
           reverseProxy="80"
                   maxThreads="150"
                   minSpareThreads="25"
                   connectionTimeout="20000"
                   enableLookups="false"
                   maxHttpHeaderSize="8192"
                   protocol="HTTP/1.1"
                   useBodyEncodingForURI="true"
                   redirectPort="8443"
                   acceptCount="100"
                   disableUploadTimeout="true"
                   bindOnInit="false"/>

<Engine name="Catalina" defaultHost="localhost">
            <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true">

                <Context path="/jira" docBase="${catalina.home}/atlassian-jira" reloadable="false" useHttpOnly="true">


                    <Resource name="UserTransaction" auth="Container" type="javax.transaction.UserTransaction"
                              factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60"/>
                    <Manager pathname=""/>
                    <JarScanner scanManifest="false"/>
                </Context>

            </Host>

I can acces jira login through 42.4.92.179/jira but after the login only a white screen.

Jira log:

An error occurred when performing the Gadget feed URL healthcheck
org.apache.http.conn.ConnectTimeoutException: Connect to 42.4.92.179:80 [/42.4.92.179] failed: connect timed out

I hope someone can help me

[Koen Gillard]

Hi Samuel

Did you add /jira to the Base URL of Jira?

KR, Koen Gillard

[Samuel Tinapp]

Hey, I thought I did this with:

   <Context path="/jira" docBase="${catalina.home}/atlassian-jira" reloadable="false" useHttpOnly="true">

path="/jira" Am I wrong?

Kindly Regards

Samuel

[Koen Gillard]

Hi Samuel

Setting the path in the server.xml is only one part of the config which needs to be done

Another part is https://confluence.atlassian.com/adminjiraserver071/configuring-the-base-url-802593107.html

KR, Koen Gillard

[Samuel Tinapp]

I don't really get which part do you mean :).

[Koen Gillard]

To configure the Base URL:

Choose Administration > System.
Choose General Configuration in the left-hand panel.
Choose Edit Settings.
Enter the new URL in the Base URL text box.
Choose Save.

[Samuel Tinapp]

Ahh ok it's correct ( http://42.4.92.179/jira

[Daniel Eads]

Hey Mona!

I recommend asking a new question using the Ask the Community button up top. That ensures we get the right info to help you without confusing this older thread.

Cheers,
Daniel

[Tomaž K.]

Hello Mona,

I have the exact same problem. If you found out what was the problem, could you please share it with us.

Regards,
Tomaž

[Alexander Grimstad]

Hi! 
I have the exact same problem, with the same implementation as described. Can someone please look into this issue? :-)