JIRA System Dashboard and menus are blank

[Ryan Duff]

UPDATE:  I have tried accessing the site over http directly to the Tomcat server without any proxy, and the exact same symptoms occur.  This is after a fresh install with all-default configuration.  It appears, then, to have something to do with using the FQDN.

Symptom:

When connecting to JIRA in the browser, the System Dashboard is just a blank screen.  The menus (Dashboards, Projects, Issues, Boards), also have nothing in their drop-downs.

This occurs when I use the FQDN to navigate to JIRA, but everything works fine if I only use the hostname.  ie:  https://hostname.mycompany.internal/jira causes the symptoms, but https://hostname/jira works fine.

In the case where the page is working, there is one notable difference in the source code of the page that is returned (inside Dashboard.jspa).  It contains:

<script>(function replaceLocation() {window.history.replaceState({}, "", "/jira/secure/Dashboard.jspa")})();</script>

Whereas the faulty page doesn't return that line of code.

Configuration:

This is running on Windows Server 2012 R2.  I have the requests proxied through IIS, and it's using a self-signed certificate.  I've added the certificate to the Java keystore, and verified with SSLPoke that it works for both URLs (hostname/jira, and hostname.mycompany.internal/jira).

The IIS server listens on port 443, and uses the Tomcat IIS connector, set up, along with the rest of the config, as per this documentation:  https://confluence.atlassian.com/adminjiraserver071/integrating-jira-applications-with-iis-802593039.html

These are the changes I made to the server.xml file (slight deviation from the above linked documentation to address an error in the JIRA logs regarding XSRF checks):

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

<Connector URIEncoding="UTF-8" enableLookups="false" port="8009" protocol="AJP/1.3" redirectPort="8443" proxyName="hostname.mycompany.internal" proxyPort="443" />

The JIRA "Base URL" is configured with the FQDN.

After much troubleshooting, I'm now running JIRA using the FQDN without any errors appearing in the JIRA logs, but the symptoms remain.  Does anyone have any insight?  I can provide more details if needed / requested.

Thank you.

[Jobin Kuruvilla [Adaptavist]]

Configuration on JIRA side, baseURL and proxyName, are correct. That makes me suspect the IIS configuration. Maybe it is redirecting to the other url somewhere? 

Also, just to confirm, base URL is https://hostname.mycompany.internal/jira, right? It should include the context path in the base url.

[AnnWorley]

Yes, the context path should be included in the base URL.

I found a support ticket where the instance worked fine directly using hostname but not when accessed via the proxy. The proxy turned out to be the culprit but the details of how it was fixed were not on the ticket. I think you are on the right track working on the IIS configuration.