ActivityTimeline app on Jira DC behind a Proxy server

If you run Jira DC nodes behind a proxy server and have any of the following Jira DC node startup parameters then this article applies to your configuration:

-Dhttp.proxyHost -Dhttp.proxyPort -Dhttps.proxyHost -Dhttps.proxyPort


It is required to configure -Dhttp.nonProxyHosts and -Dhttps.nonProxyHosts Jira node startup parameters for the app to work correctly in this environment configuration. So that Jira nodes do not go through the proxy server when communicating with each other internally (because the proxy host most likely returns an error code as it does not “know” the internal hostnames).

Please follow the following steps to configure each Jira DC node.


1. Open <JIRA_NODE1_FOLDER>/bin/ file (Linux) or <JIRA_NODE1_FOLDER>/bin/setenv.bat file (Windows) for editing.

​2. Find the location where you have any of these parameters:  -Dhttp.proxyHost -Dhttp.proxyPort -Dhttps.proxyHost -Dhttps.proxyPort

3.  Add -Dhttp.nonProxyHosts and -Dhttps.nonProxyHosts parameters with the list of all Jira node hostnames (Jira DC with 3 nodes in this example):

Example:  -Dhttp.nonProxyHosts=node1_hostname\|node2_hostname\|node3_hostname                  -Dhttps.nonProxyHosts=node1_hostname\|node2_hostname\|node3_hostname

If you already have this parameter then please just add all those Jira nodes' hostnames to the existing list after \| symbol.

Please note that hostnames are separated with an escaped pipe symbol: \|

4.  Save the file and restart the Jira DC node.

5.  Repeat the same procedure for every other Jira DC node (2 remaining nodes in this example).


This should solve the inter-node communication issue.


If the issue still occurs or you are experiencing some other problem that is not described here, please don’t hesitate to contact our team at