Configure/run Confluence Data Center behind F5 Load balancer

Seven Cosmos

Hello Atlassian community,

I configure Confluence (Data center) behind an load balancer (F5-Big IP), and load balancer could detect the default port (8090) but not the 443 port (SSL)

I used following configuration in server.xml:

 

<Connector port="8090" connectionTimeout="20000" redirectPort="443"
maxThreads="48" maxPostSize="16777216" minSpareThreads="10"
enableLookups="false" acceptCount="10" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol"/>

<Connector port="443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25"
protocol="org.apache.coyote.http11.Http11NioProtocol"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocols="TLSv1,TLSv1.1,TLSv1.2" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" SSLEnabled="true"
SSLCertificateFile="path\machinename.domain.com.crt"
SSLCertificateKeyFile="path\machinename.domain.com.key"
URIEncoding="UTF-8"/>

 

do I need to use a keystore instead of above configuration, while knowing that in local machine of this Confluence I can open admin console through 443 port (It's showing that's not trusted because it's self signed certificate)

this configuration is working well for other instance of confluence, but not for this new INFRA

Thank's

 

Bert van Dijk _TMC_nl_

Hi @Seven Cosmos ,

 

I think there is a problem with the connector 443. When you start Confluence, have a look at the catalina.out in the %confluence-install-dir%/log . There it will tell you what is wrong. A Java key store is recommended. A self signed certificate is never recommended. Maybe you need to put the root and intermediate certificates in %confluence-install-dir%/jre/lib/security/cacerts ?