Communication Breakdown error thrown after an upgrade
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Problem
The following error is thrown when browsing JIRA after an upgrade
1
2
3
Communications Breakdown
The JIRA server could not be contacted. This may be a temporary glitch or the server may be down.
Close this dialog and press refresh in your browserThe following appears in the atlassian-jira.log
1
2
3
2016-04-13 09:50:15,038 http-nio-8080-exec-12 ERROR 590x8242x1 19g35zo 62.209.223.98,127.0.0.1 /plugins/servlet/gadgets/dashboard-diagnostics [c.a.g.d.internal.diagnostics.DiagnosticsServlet] DIAGNOSTICS: FAILED
com.atlassian.gadgets.dashboard.internal.diagnostics.UrlSchemeMismatchException: Detected URL scheme, 'http', does not match expected scheme 'https'
at com.atlassian.gadgets.dashboard.internal.diagnostics.Diagnostics.checkExpectedScheme(Diagnostics.java:52)Diagnosis
Environment
Proxy/https/SSL is configured for JIRA
Diagnostic Steps
Configure a bypass connector in your server.xml as per these instructions: bypassing the proxies. Test while connected through this bypass to see if the issue reproduces.
Cause
This is due to a missing or incorrect wrong configuration in server.xml
Solution
Resolution
Configure the SSL configuration again as per Atlassian's best practices:
https://confluence.atlassian.com/jira/running-jira-over-ssl-or-https-124008.html
Note: Atlassian applications allow the use of SSL within our products, however Atlassian Support does not provide assistance for configuring it. Consequently, Atlassian cannot guarantee providing any support for it.
Was this helpful?