Confluence HTTPS issue with ERR_TIMED_OUT

Deleted user June 1, 2018

Hi,

we have confluence running over HTTPS. it was running with self-signed certificate very well. Just trust warning when user access to the site.

So we got CA signed certificate in p7b format which contains Root, Intermediate certificates, certificate for our server.

I imported the .p7b file into Java keystore with below command successfully.

keytool -importcert -alias tomcat -trustcacerts -keystore <KEYSTORENAME> -file certificates.p7b -storetype JCEKS

 I needed "-storetype JCEKS" because "keytool" doesn't get .p7b format certificate basically. it get failed with saying it's x.509 format.

Anyway I imported .p7b certificate chain into my keystore  and restarted Confluence tomcat server.

This is my server.xml and it was working well with self-signed certificate.

<Connector port="8443" 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"
URIEncoding="UTF-8" keystorePass="changeit" keystoreFile="<KEYSTORE_FILENAME>"/>

key storepass is same. keystorefilepath is also same.

 

But after restarted Confluence, it's not responding in web browser. Web browser says time out error.

Any comment for this issue from experts?

Thanks.

1 answer

0 votes
Vickey Palzor Lepcha
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 1, 2018

Is is working when you bypass PROXY using your IP and port ?

Deleted user June 2, 2018

only HTTPS port (8443) is having this issue. other ports are just working fine.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events