Dashboard artifacts after upgrade to 7.9.0

[Riedl-Taras]

Hello. I upgraded to 7.9.0 self hosted Jira with Starter License, only one 3d party plugin for Git.

And now all dashboards look ugly.

Also a lot of errors in Chrome console about not found CSS.

Chrome console log

Does anyone know what can be the reason and how to fix it?

Thanks.

[Andy Heinzer · Accepted solution]

Hi Taras,

There are two different ways I would expect this kind of problem to appear in Jira:

1) By Proxy
2) By a plugin or script in Jira


Since I think that #1 is more likely, I'd like to know more about your Jira setup.   Do you have a reverse proxy, load balancer, or other firewall like device that sits between your Jira server and the outside internet?   If so, then it might help to first try to bypass this proxy to see if the problem continues.  Steps on how to do this are in How to bypass a Proxy and SSL to test network connectivity


If you can follow those steps, and then access the Jira site on a localhost address/port that does not send traffic through this proxy, I would be interested to learn the results.  This can tell us more about this problem.     


Could you also let us know which version of Jira you upgraded from?    If you have a proxy and you upgrade from any Jira version before 7.3.2 (and you did not have the problem on that version), then I think you could be affected by this documented problem: https://jira.atlassian.com/browse/JRASERVER-64917   If that is the case, I would recommend following the work-around in that bug ticket.  That bug ticket effects environments that are using a Windows based proxy.

[Riedl-Taras]

Hi Andrew, thanks for the reply. It is completely local installation, no access from internet. The company domain is real, but subdomain is local.

This subdomain is configured in Apache running on Ubuntu virtual machine.

<VirtualHost *:80>
 ServerName jira.riedl-gmbh.eu
 ServerAlias www.jira.riedl-gmbh.eu
 ProxyPreserveHost On
 ProxyPass / http://localhost:8800/
 ProxyPassReverse / http://localhost:8800/
</VirtualHost>

<VirtualHost *:8808>
 ServerName jira.riedl-gmbh.eu
 ServerAlias www.jira.riedl-gmbh.eu
 ProxyPreserveHost On
 ProxyPass / http://localhost:8808/
 ProxyPassReverse / http://localhost:8808/
</VirtualHost>

<VirtualHost *:443>
 ServerName jira.riedl-gmbh.eu
 ServerAlias www.jira.riedl-gmbh.eu
 ServerAdmin taras.muravskyi@riedl-gmbh.eu
 SSLEngine on
 SSLProxyEngine on
 SSLProxyVerify none
 SSLProxyCheckPeerCN off
 SSLProxyCheckPeerName off
 SSLProxyCheckPeerExpire off
 SSLCertificateFile "/opt/bitnami/apache2/conf/server.crt"
 SSLCertificateKeyFile "/opt/bitnami/apache2/conf/server.key"
 ProxyPreserveHost On
 ProxyPass / https://localhost:8800/
 ProxyPassReverse / https://localhost:8800/
</VirtualHost>

[Riedl-Taras]

Upgrade was done from 7.6.0

[Andy Heinzer]

Hi Taras,

Thanks for this information.  Could you also share with us any/all <Connector> tags you have in your $JIRAINSTALL/conf/server.xml file? 

My concern is that since this traffic appears to be redirected to port 80 for HTTP traffic, that Jira's server.xml will likely have a completely different port to host its Tomcat site on, and in turn your server.xml should have some pretty specific directives in that connector, such as proxyName, proxyPort, and scheme.   I have seen instances when these are not defined, or defined incorrectly where Jira's site will not load correctly in those cases.

In addition to these steps, do you think you could generate a HAR file in your browser when this page loads?  Steps to do this are in https://confluence.atlassian.com/kb/generating-har-files-and-analyzing-web-requests-720420612.html

We might gain some insight here with this HAR file.

[Riedl-Taras]

HAR files: 

https://www.dropbox.com/s/dinh9tiilz75i6p/har-jira.riedl-gmbh.eu.zip?dl=0

Connector

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

[Andy Heinzer]

Hi,
I thanks for the HAR file, I found a number of 404 errors in it. This is just an indication that the files being requested by the browser are not able to be located.   These all appear to be css and js files.  Which would explain why the pages don't appear correctly.

I also found another interesting URL in your HAR file:
http://jira.riedl-gmbh.eu/mod_pagespeed_beacon?url=http%253A%252F%252Fjira.riedl-gmbh.eu%252Fsecure%252Fadmin%252FEditDefaultDashboard%21default.jspa

This 'mod_pagespeed_beacon' specific URL is not native within Jira by itself, so it must be a product of your Apache environment.  I suspect that this either the mod_pagespeed module is causing the problems, or there is some other configuration on the proxy side that might need to be adjusted to correct this.

There is another KB called Changes in JIRA not Visible Until Manual Refresh in Browser that deals with other problems that can be seen in Jira when using the pagespeed module in an Apache proxy.  

While that KB might not be the exact same problem you are seeing here, I would like to try the same resolution there because I think the source of the problem is this module:

Resolution

Verify if any pagespeed modules are running in the Apache HTTP server by running the following command to list the loaded modules (Linux Only):

# apachectl -t -D DUMP_MODULES

If any pagespeed module is loaded please work with your System Administrator to disable them

Also, your connector should probably also have the proxyName, proxyPort, and scheme parameters defined in it, since it's clear that there is either a proxy or some other redirect happening here.   In Jira's server.xml I would recommend altering your connector to look like this:

<Connector port="8800" 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="jira.riedl-gmbh.eu" proxyPort="80" scheme="http"/>

This way the Jira site is aware that traffic to it is actually being first directed to another site/address.  Without this, you are likely to encounter other problems with Jira rendering pages due to built in cross site scripting protections.  Please note that after you make changes in this server.xml and save them, you have to restart Jira before these settings will take effect.

[Riedl-Taras]

It is an old VM with obsolete software from Bitnami, and they really had this Apache module. Jira works fine after I disabled it.

Thank you very much.

[Andy Heinzer]

Awesome, glad to hear that helped.