Base URL mismatches in UPM due to wrong port for HTTPS

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

The following appears in the atlassian-jira.log:

2012-07-09 16:56:03,629 http-8080-3 WARN xxxx 1015x396x1 vj5zf 172.18.127.12,0:0:0:0:0:0:0:1 /rest/plugins/1.0/available/featured [upm.rest.async.AsynchronousTaskManager] Configured application base URL (https://xxx.xxx.xxx.xxx:334/jira) does not match base URL from request (https://xxx.xxx.xxx.xxx:443/jira)

Diagnosis

If your app base URL is HTTPS and doesn't explicitly specify a port, UPM wrongly displays a base URL mismatch warning because it thinks the port is supposed to be 334 instead of 443. This does not disrupt any UPM functionality, it just causes a misleading warning banner to appear all the time at the top of the UPM page.

Cause

This is caused by a bug in UPM 2.4. Please see UPM-2339 for more info.

Resolution

Upgrade to UPM 2.4.1. Please see Upgrading the Upgrading Universal Plugin Manager for more info.

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.