Jira System Dashboard and menus are blank

Ryan Duff April 27, 2017

 

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:  http://hostname.mycompany.internal causes the symptoms, but http://hostname 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.

The JIRA installation is fresh with an MSSQL database connection, and all other settings are default.  It's running over port 8080 HTTP.

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

Thank you.

2 answers

1 accepted

1 vote
Answer accepted
Ryan Duff April 28, 2017

I found something closer to the root cause of the issue, but I still don't know exactly why it isn't working.

These symptoms only occur if I browse to the FQDN (https://hostname.mycompany.internal/jira) from the server that's running JIRA.  If I browse to it from another machine on the network, the site works fine.

Since browsing to the site on the server itself isn't a requirement for me to administrate the server, I consider this issue resolved for me.  However, if anyone has any insight as to why this is happening, for others who might see this thread, feel free to chime in.

Thanks.

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 27, 2017

When you say the base url is the FQDN, does that url include the port 8080?  Or have you stuck it behind a proxy that forwards from the FQDN to the actual full location?

Suggest an answer

Log in or Sign up to answer