Tomcat config is incorrect error

[Andrew Balmer]

Hello, 

I am getting following error when accessing Confluence via proxy (i get same error when accessing confluence app from the internal network)

Tomcat config is incorrect

The Tomcat server.xml has an incorrect configuration:

scheme should be 'https'
proxyName should be 'confluence.co.uk'
proxyPort should be '443'

According to this link below I am using reverse proxy and under  <install-directory>/conf/server.xml file I have following settings 

https://confluence.atlassian.com/jirakb/jira-displays-an-error-banner-about-the-incorrect-tomcat-config-939940652.html

<Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocols="TLS" SSLEnabled="true"
URIEncoding="UTF-8" keystorePass="Password"
keystoreFile="F:\Confluence\conf\Confluence.keystore"/>

<Connector port="8090" connectionTimeout="20000" redirectPort="8443"
maxThreads="48" minSpareThreads="10"
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol"
scheme="https" secure="true" proxyName="confluence.co.uk" proxyPort="8443"/>

I have also tried following settings but that did not work:

<Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocols="TLS" SSLEnabled="true"
URIEncoding="UTF-8" keystorePass="Password"
keystoreFile="F:\Confluence\conf\Confluence.keystore" secure="true" proxyName="confluence.co.uk" proxyPort="8443"/>

Could someone let me know what could I be doing wrong here? 

[Nic Brough -Adaptavist- · Accepted solution]

In the section "connector port = 8090" why did you set the proxy port to the internal connector port instead of the port the proxy is going to be working on?

The proxy connector settings that the error message is warning you about are for the external user-facing stuff, not the internals.  Try changing it to 443 as suggested