Base URL warnings on Manage Apps page in Jira
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
While navigating to Manage Apps page, below warning message is encountered about the Base URL misconfiguration
Environment
Jira Data Center
Diagnosis
The following warning message appears in atlassian-jira.log:
1
http-nio-8080-exec-15 WARN admin 778x1498x2 xxxxxxx 0:0:0:0:0:0:0:1 /rest/plugins/1.0/installed-marketplace [c.a.u.core.async.AsynchronousTaskManager] Configured application base URL (https://jira.example.com:443) does not match base URL from request (http://jira.example:80)And the server.xml has the default HTTP connector
1
2
3
4
<Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false"/>Cause
The warning can be noticed in following cases:
The Base URL is configured with HTTPS port 443 and being accessed via HTTP port like 8080
Also, the connector in server.xml file, is pointing to an HTTP connector and proxy configurations are missing which is over HTTPS.
proxyName
proxyPort
scheme
Secure
Solution
Update the Base URL as per the configuration in server.xml. However, if the proxy configurations are missing update the tomcat connector with the same
1
secure="true" scheme="https" proxyName="<subdomain>.<domain>.com" proxyPort="443"Additionally, in case of Helm Chart, update the proxy details in values.yaml file
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
tomcatConfig:
acceptCount: "10"
connectionTimeout: "20000"
customServerXml: ""
enableLookups: "false"
generateByHelm: false
maxHttpHeaderSize: "8192"
maxThreads: "100"
mgmtPort: "8005"
minSpareThreads: "10"
port: "8080"
protocol: HTTP/1.1
proxyName: <subdomain>.<domain>.com
proxyPort: 443
redirectPort: "8443"
scheme: https
secure: trueWas this helpful?