Issue-1)
confluence throws error about tomcat server.xml configured incorrectly like below when I login. The confluence is 3 node cluster sitting behind AWS ALB. The clustering works all good and I can access confluence with exact same url which appears in the tomcat error message above with same port and protocol. Base url is exactly configured like https://confluence.mydomain:8443.
the EC2 instances are also running o port 8443 and ssl enabled with same certificate as on ALB.
Tomcat config is incorrect
The Tomcat server.xml has an incorrect configuration:
scheme should be 'https'
proxyName should be 'confluence.mydomain'
proxyPort should be '8443'
I have checked and tried out different comibinations specially having line like below in server.xml. As you see there are only 2 connectors and I am using only one with port 8443.
<Connector port="8090" connectionTimeout="20000" redirectPort="8443"
maxThreads="48" maxPostSize="16777216" minSpareThreads="10"
enableLookups="false" acceptCount="10" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol"
scheme="https" secure="true" proxyName="confluence.mydomain" proxyPort="8443"/>
<Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" maxPostSize="16777216" minSpareThreads="25"
protocol="org.apache.coyote.http11.Http11Nio2Protocol"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" URIEncoding="UTF-8"
clientAuth="false" sslProtocol="TLSv1.2" sslEnabledProtocols="TLSv1.2" SSLEnabled="true"
keystoreFile="/etc/vault_agent/keystore.jks" keystorePass="****" keyAlias="cert"
scheme="https" secure="true" proxyName="confluence.mydomain" proxyPort="8443"/>
I am unable to figure out this issue which I strongly believe is linked to 2nd issue below.
Issue-2)
I am unable to create application link between jira and confluence. Again base urls of both are same with which I access them( cname to ALB load balancers) and both are 3 node clusters behind aws ALB.
Invalid OAuth signature
We couldn't connect to confluence, possibly because that instance is behind a misconfigured proxy.
Any help is greatly appreciated.
