how to solved Mismatched URL scheme in JSM 5.6.0

[Denis Rodrigues]

Hello, can anyone help me solve this problem?
please if someone knows some effective way to solve it, I have tried other related topics but still no success
"

Dashboard Diagnostics: Mismatched URL Scheme

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

If you believe this diagnosis is in error, or you have any other questions, please contact Atlassian Support."

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

The problem here is that part of your system is trying to use HTTP and the other part HTTPS.

It is easier to explain with a simple example (this is roughly what I have at home):

• Jira, running on HTTP on a server
  • The Tomcat connector is set up to understand that it is running behind a proxy - specifically one running https, with a path of /jira and on the right ports and domains.
  • The base URL is set to https://mydomain.com/jira
• A reverse proxy that 
  • Exposes https://mydomain.com/jira
  • Is configured to proxy back to the Jira on your server

If you've done an upgrade, the most likely problem is that you did not replay all the changes for https proxying back into the Tomcat's server.xml file.  It thinks it's running Jira on HTTP, but you're using https schemes, proxies and base url.

But if the proxy configuration is wrong, you can get this error as well (the proxy config does not have HTTP or HTTPS in it per application, it's done at a higher level)