jira base url connection refused

Edouard Dorcier October 31, 2018

Hi,

we have a jira instance and we want to let people outside of the company network connect to it.

We created a URL and added a F5 in front of the network. I modified the server.xml use Atlassian guidelines adding these attributes to the Connector node :


proxyName="jira-int.mydomain.com"
proxyPort="443"
scheme="https"

and added the certificate to the java cacert. 

Now I can connect from outside the company's network but I cannot connect from the inside and the base URL gadget check fails. Looking into the logs I get this stacktrace :

2018-10-31 10:14:15,657 HealthCheck:thread-5 ERROR ServiceRunner [c.a.j.p.healthcheck.support.BaseUrlHealthCheck] An error occurred when performing the Base URL healthcheck: 
org.apache.http.conn.HttpHostConnectException: Connect to jira-int.mydomain.com:443 [jira-int.mydomain.com/192.168.2.45] failed: Connection refused: connect
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at com.atlassian.jira.plugins.healthcheck.support.BaseUrlHealthCheck.doCheck(BaseUrlHealthCheck.java:53)
at com.atlassian.jira.plugins.healthcheck.support.AbstractSupportHealthCheck.check(AbstractSupportHealthCheck.java:23)
at com.atlassian.support.healthcheck.impl.PluginSuppliedSupportHealthCheck.check(PluginSuppliedSupportHealthCheck.java:51)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)

 Does anyone have an idea of what happens ?

Thanks for your replies.

2 answers

1 accepted

0 votes
Answer accepted
Shankar Asam {Appfire}
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.
October 31, 2018

Hi,

Can you please check the domain resolution internally? and also see if you are able to connect base-url (jira-int.mydomain.com) on 443 successfully. To do that, login to server where jira is hosted and do the below;

telnet jira-int.mydomain.com 443

Check if you are able to connect fine on port 443. If not, then there is port block. You may need to open 443. Typically the above jira-int.mydomain.com should be resolving to your F5 Virtual server. 

-Shankar

Edouard Dorcier November 5, 2018

Hi @Shankar Asam {Appfire}

That was the way... It told me that ports were not available and my whole architecture was somewhat wrong.

 

Thanks again and have a good day.

Suggest an answer

Log in or Sign up to answer