Dashboard Diagnostics: Mismatched URL Scheme

This is a clean/new install and not an upgrade. We are getting the following error on the dashboard:

JIRA is reporting that it is using the URL scheme 'http', which does not match the scheme used to run these diagnostics, 'https'. This is known to cause JIRA to construct URLs using an incorrect hostname, which will result in errors in the dashboard, among other issues.

The most common cause of this is the use of a reverse-proxy HTTP(S) server (often Apache or IIS) in front of the application server running JIRA. While this configuration is supported, some additional setup might be necessary in order to ensure that JIRA detects the correct scheme.

The following articles describe the issue and the steps you should take to ensure that your web server and app server are configured correctly:

- Gadgets do not display correctly after upgrade to JIRA 4.0

- Integrating JIRA with Apache

- Integrating JIRA with Apache using SSL


Our f5 passes the https/443 request to our apache layer via http/80 and apache has instructions to proxy the request to the host where Jira standalone is running.

5 answers

0 vote
Janet Albion Atlassian Team Feb 28, 2013

Hi Derek,

Have you tried setting the proxyName and proxyPort in the JIRA's server.xml so that it will be aware of the proxy ? It's something like

scheme="https" proxyName="jira.example.com" proxyPort="443"

When the load balancer sends the request to one of 5 servers, how do you specify the proxyName? Can you have multiple servers listed in proxyName?


When the load balancer sends the request to one of 5 servers,

Mind to clarify more on the 5 servers of the above statement? Did you meant that you have multiple JIRA server? Elaborate more on the statement may help other user to understand your problem better as I'm not really familiar with load balancer. ;)

We have 5 httpd servers that proxy the request back top the one jira instance.

We have a load balancer (f5) that manages the pool of apache servers. When/If one gets overloaded, it removes that server form the pool and directs the balanced/ratioed traffic to the other 4 until the 5th recovers at which time it gets added back to the pool.

This resolved it for me:


For this:


The proxy_server is the domain that jira answers on, not the name of the server(s) actually doing the proxy-ing.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

561 views 1 18
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