JIRA Displays an Error Banner about the incorrect Tomcat config
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
Symptoms
JIRA displays the following message to administrators:
Tomcat config is incorrect
The Tomcat server.xml has an incorrect configuration:
scheme should be '<recommended scheme>' proxyName should be '<recommended proxyName>' proxyPort should be '<recommended proxyPort>'
Cause 1
This message appears when Jira attempts to check that the URL you are using to access Jira is the same as Jira's base URL, but cannot complete the check because of a problem with your proxy configuration. This is usually because:
a
proxyNameandproxyPortare present in your<install-directory>/conf/server.xmlfile but you are not using a reverse proxy.you are using a reverse proxy, but the values for
proxyNameandproxyPortare incorrect in your<install-directory>/conf/server.xmlfile.
Cause 2
This message can appear also if there's an active duplicate connector in server.xml. I.e. it would appear like this:
Notice the connector ports are the same which is incorrect
Resolution
Cause 1
If you are not using a reverse proxy, make sure the proxyName and proxyPort attributes are not included. Your connector should look similar to the example below if you are not using a reverse proxy:
1
2
3
4
<Connector port="8080" connectionTimeout="20000" redirectPort="8443"
maxThreads="48" minSpareThreads="10"
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol" />If you are using a reverse proxy, make sure the the proxyName and proxyPort attributes have correct values for your reverse proxy. Your connector should look similar to the example below, and the recommended settings will be displayed in the warning.
1
2
3
4
5
<Connector port="8080" connectionTimeout="20000" redirectPort="8443"
maxThreads="48" minSpareThreads="10"
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol"
proxyName="www.example.com" proxyPort="80" scheme="http"/>If you still see this error after checking your server.xml, check your proxy configuration is also correct. The following pages provide example configurations.
Proxying Atlassian server applications with Apache HTTP Server (mod_proxy_http)
Proxying Atlassian server applications with Microsoft Internet Information Services (IIS)
How to configure Amazon Web Service Application Load Balancer with Confluence
Cause 2
Either change the connector port on one the connectors, or comment out the redundant connector and restart Jira
Workaround for Cause 1:
If the Base URL check continues to detect a problem, you can disable the check in your site:
Go to ⚙ > Add-ons > System
Disable the Jira Base URL plugin system add-on.
The base URL warning should no longer appear.
ℹ️ Please keep proxyName value in lower-case and must match the Base URL of the JIRA instance. For example, a proxyName of ServerName will not match a Base URL of http://servername.com. To fix this, change the proxyName to servername.com
Was this helpful?