Dashboard Diagnostics: Mismatched URL Hostname

I'm hoping somebody can help me with the following -

We get the error below if JIRA is accessed at http://10.168.45.137:8080/secure/Dashboards.jspa and the system dashboard fails to render.

Dashboard Diagnostics: Mismatched URL Hostname
JIRA is reporting that it is running on the hostname 'jira.companyname.local', which does not match the hostname used to run these diagnostics, '10.168.45.137'.
This is known to cause JIRA to construct URLs using the incorrect hostname, which will result in errors in the dashboard, among other issues.


However if users try to access jira at http://10.168.45.137:8080 the redirect works properly and resolves to http:jira.companyname.local

 

snippet from server.xml -

<Service name="Catalina">
<Connector port="8080"
maxThreads="150"
minSpareThreads="25"
connectionTimeout="20000"
proxyName="jira.companyname.local"
proxyPort="80"
enableLookups="false"
maxHttpHeaderSize="8192"
protocol="HTTP/1.1"
useBodyEncodingForURI="true"
redirectPort="8443"
acceptCount="100"
disableUploadTimeout="true"/>
<!--

 

Snippet from Apache httpd.conf -

ProxyRequests Off
ProxyPreserveHost On

<Proxy *>
Order deny,allow
Allow from all
</Proxy>
<VirtualHost *:80>
ProxyPass / http://localhost:8080/ timeout=600
ProxyPassReverse / http://localhost:8080/
</VirtualHost>

<VirtualHost *:81>
<Location /server-status>
SetHandler server-status
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Location>

 

Why am i going wrong with this?

 

Many thanks

Conor

1 answer

Conor,

 

Try adding:

ServerName jira.companyname.local

 

to your httpd.conf first.  Also, don't forget:

# Put/uncomment this after the other LoadModule directives
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so

 

at the top of the httpd.conf file.  Restart Apache and try again.  If that doesn't work restart Jira, then Apache again and try.  Our server.xml file does not have:

 

proxyName="jira.companyname.local"
proxyPort="80"
And the proxy works fine.
Bryan

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

21,272 views 2 7
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you