we have a Problem with the dashboard.
The Activity Stream applet takes ages to load and shows an 504 Gateway Time-out afterwards.
I have searched the logs after an error wich could explain the problem but found nothing.
I checked the application links and they work fine as far as I can see.
Firewall entries are set and I can reach each Server throw the links.
Our Problem is that the Jira Server can't access the Plugins over the Dashbord applet.
What is interesting that it works from time to time an then it fails again.
With the developer tools I couls se that there are indeed:
Failed to load resource: the server responded with a status of 504 (Gateway Time-out)
Sadly I have no clue how to fix that Problem.
Can you try Step 4 from Resolution on Gadgets do not display when failing to access XML specification?
We need to make sure that your server is able to access itself from the URL mentioned in the article.
Of course, be sure to replace the example support.atlassian.com with your own instance URL.
Send us the results of the test.
ok I had a look at resolution with the following results.
1. We use Jira 7.6
2. No firewall restrictions
3. <Connector port="8080"
4. wget test succsesful
Auflösen des Hostnamen »jira.dynacloud.de (jira.dynacloud.de)«... 22.214.171.124
Verbindungsaufbau zu jira.dynacloud.de (jira.dynacloud.de)|126.96.36.199|:8443... verbunden.
HTTP-Anforderung gesendet, warte auf Antwort... 200
Länge: 113068 (110K) [application/xml]
In »»assigned-to-me-gadget.xml.1«« speichern.
100%[===========================================================================================================================================>] 113.068 --.-K/s in 0,001s
2017-11-24 10:37:00 (73,6 MB/s) - »»assigned-to-me-gadget.xml.1«« gespeichert [113068/113068]
Alright, thank you Dirk.
I also found another post where a user had to use 8080 rather than 8443 as his Tomcat wasn't working properly with 8443.
I hope this helps.
as you can See here all is set.
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;
My main problem ist that is works at times and fails at others.
Let`s try to bypass reverse proxy and check if the issue is there. That way we will eliminate Nginx from the equation.
If the problem is still there check the Network tab if the issue is the same and also JIRA logs for the error message at that time.
It is possible that you have a performance issue, so please check if the CPU is spiking at the time, and if it is, check heap usage and increase heap if necessary.
p.s. Intermittent issues like that are porbably releated to the performance.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs