Connection timed out when connecting to Jira via HTTPS

[Brian Goyda]

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"
                         sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2,TLSv1.3"
                         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 [c.a.t.j.healthcheck.support.GadgetFeedUrlHealthCheck] An error occurred when performing the Gadget feed URL healthcheck
java.net.NoRouteToHostException: No route to host
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:75)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
at com.atlassian.troubleshooting.jira.healthcheck.support.GadgetFeedUrlHealthCheck.check(GadgetFeedUrlHealthCheck.java:56)
at com.atlassian.troubleshooting.healthcheck.impl.PluginSuppliedSupportHealthCheck.check(PluginSuppliedSupportHealthCheck.java:49)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

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

[Junio Fernandes]

I had this problem and I solved with this article:

https://dev.to/amezousan/how-to-run-jira-application-over-https-2g2a

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.