It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Connection timed out when connecting to Jira via HTTPS Edited

Running Jira Server 7.11 on AWS. Attempting to set up HTTPS access for it. Followed the guide for command lines here. Port is added to the security group on AWS, so that shouldn't be an issue. Running Amazon Linux AMI.

Here is my output running netstat

$ netstat -lant | grep 8443
tcp6       0      0 :::8443                 :::*                    LISTEN

When I try and telnet to the ip and port, the connection times out.

Here is the relevant information from my server.xml file

<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
                        maxHttpHeaderSize="8192" SSLEnabled="true"
                         maxThreads="150" minSpareThreads="25"
                         enableLookups="false" disableUploadTimeout="true"
                         acceptCount="100" scheme="https" secure="true"
                         clientAuth="false" useBodyEncodingForURI="true"
                        keyAlias="jira" keystoreFile="/var/atlassian/application-data/jira/jira.jks" keystorePass="changeit" keystoreType="JKS"/>

<Connector  acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150"
minSpareThreads="25" port="8080" protocol="HTTP/1.1" redirectPort="8443" useBodyEncodingForURI="true"/>

When I look at catalina.out, here is the error that comes back.

2018-07-27 20:34:57,381 HealthCheck:thread-2 ERROR [] An error occurred when performing the Gadget feed URL healthcheck No route to host
at Method)
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(
at org.apache.http.impl.execchain.MainClientExec.establishRoute(
at org.apache.http.impl.execchain.MainClientExec.execute(
at org.apache.http.impl.execchain.ProtocolExec.execute(
at org.apache.http.impl.execchain.RetryExec.execute(
at org.apache.http.impl.execchain.RedirectExec.execute(
at org.apache.http.impl.client.InternalHttpClient.doExecute(
at org.apache.http.impl.client.CloseableHttpClient.execute(
at org.apache.http.impl.client.CloseableHttpClient.execute(
at org.apache.http.impl.client.CloseableHttpClient.execute(
at com.atlassian.troubleshooting.healthcheck.impl.PluginSuppliedSupportHealthCheck.check(
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

I am pretty lost here, I've followed most guides for resolving similar issues from this board. Any help would be appreciated.


1 answer

I had this problem and I solved with this article:

The important thing was

In the directory, there is a server.xml file. It includes an example to enable a "https" feature, but you need to change a bit when you use Apache Tomcat ver 8.0.x.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Introducing new features for Jira Software Cloud's roadmap

Hi Atlassian community, A few months ago, we offered a sneak peak of the new hierarchy view on the roadmap. Thank you for all the feedback (and excitement) and for helping us shape the direction of...

22,914 views 101 74
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you