Bypass a proxy or SSL to test network connectivity for Jira Server and Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Sometimes it's necessary to test connectivity to a single application from a single workstation. The methods described in this article should only be used if you need to test connectivity from a single workstation. To bypass a Proxy and SSL, you will need to make sure if there is a non-proxy port configured on Tomcat or you should add a secondary connector to Tomcat that allows for an alternate route of communication to the application.
Solution
For this example, let's say
JIRA base URL:
https://jira.atlassian.com
JIRA's internal IP Address:
192.168.1.100
JIRA is configured with a Proxy
Please follow the steps below to bypass SSL and Proxy:
Stop JIRA.
Open JIRA Installation Directory
/conf/server.xml
in a text editor.Verify if the following
Connector port
exist in the file:For JIRA Software version 7.12.3 and above:
1 2 3 4 5 6 7 8 9 10 11 12
<Connector port="8081" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" acceptCount="100" disableUploadTimeout="true" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"/>
For JIRA version lower than 7.12.3
1 2 3 4 5 6 7 8 9 10
<Connector port="8081" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" acceptCount="100" disableUploadTimeout="true"/>
The
Connector port
might be different, as long as the connector is not configured with SSL or Proxy, then you should be able to bypass the Proxy and SSL. In this case, you should be able to access JIRA with the following URL:http://192.168.1.100:<connector
port>
Please backup the current
server.xml
If such
Connector port
does not exist in theserver.
xml file, then please add the connector by copy-pasting the above connector to theserver.xml
. Make sure to use the correct connector syntax (depending on the version of JIRA) and port8081
is not already in use (simply search for 8081 in your connector and use 'netstat -an' command to verify if nothing else is listening on that port. If the port is already used, please use a different port.Start JIRA.
Access JIRA with the following URL:
http://192.168.1.100:8081
Change the
8081
port to the respective value if you have configured the port differently.Change the base URL to http://192.168.1.100:8081
After the test, you should either:
Remove the connector port from the server.xml file.
Restore the content of the server.xml file from the backup server.xml file.
Please take note that you will need to restart JIRA for the changes to be committed.
Was this helpful?