Universal Plugin Manager Fails with UrlSchemeMismatchException error
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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
Symptoms
Attempting to update a plugin using the Universal Plugin Manager in Jira (via the Manage Add-On functionality), results in an error message similar to the following:
"The system attempted to connect to http://xxx.xxxx.xxx/rest/plugins/1.0/pending/f087d359-7220-405b-ae6c-7cedeefdb55d to retrieve the status of your operation, but failed. This can indicate a problem with the base URL configuration of your instance. Try refreshing the page to see if the operation completed, and see UPM documentation for more details about this error."
The following appears in the atlassian-jira.log:
2014-09-30 11:22:08,481 http-bio-8080-exec-5 ERROR tela 682x282x3 1pdxbmh 192.100.10.00,100.100.10.100 /plugins/servlet/gadgets/dashboard-diagnostics [dashboard.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:64)
at com.atlassian.gadgets.dashboard.internal.diagnostics.Diagnostics.check(Diagnostics.java:36)
at com.atlassian.gadgets.dashboard.internal.diagnostics.DiagnosticsServlet.executeDiagnostics(DiagnosticsServlet.java:97)Environment
Jira Data Center on any version from 8.0.0.
Cause
The server.xml used is not configured properly to use a proxy.
Resolution
- Open <JIRA Installation>/conf/server.xml in a text editor.
Make sure that the proxyName and proxyPort are configured with the hostname and port of your reverse proxy (please refer the example below):
proxyName="proxy_url_here" scheme="https" secure="false" proxyPort="port_number_here"/>