How to run JIRA on a specific IP

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

The content on this page relates to platforms which are not supported. Consequently, Atlassian Support cannot guarantee providing any support for it. Please be aware that this material is provided for your information only and using it is done so at your own risk.

Solution

Problem

JIRA needs to run on a specific IP address.

Resolution

  • Edit the server.xml used by Tomcat which runs JIRA

  • Find the connector you are currently using. The default one looks like:

    Stock connector

    1 <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"/>
  • Add the address property like so:

    Stock connector

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

    ℹ️ Based on information at: http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Standard_Implementation and http://tomcat.apache.org/tomcat-6.0-doc/config/http.html#Standard_Implementation

Updated on April 15, 2025

Still need help?

The Atlassian Community is here for you.