Changing port that your Atlassian application listens on
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Problem
You may wish to change the port that your Atlassian application listens on from the default one to a different value if another application is already running on any of the default ones as that will cause Tomcat (and therefore your Atlassian application) to fail during startup.
Here is a list of default ports for each one of the Atlassian applications:
| Application | Connector Port | Server Port |
|---|---|---|
| JIRA | 8080 | 8005 |
| Confluence | 8090 | 8000 |
| Bitbucket Server | 7990 | 8006 |
| Bamboo | 8085 | 8007 |
| Fisheye/Crucible | 8060 | - |
Solution
To change the default ports above:
Stop your Atlassian application
| JIRA applications | Use these commands from the JIRA installation directory:
On Windows, use:
|
| Confluence | Use these commands from the Confluence installation directory:
On Windows, use:
See also Starting Confluence Automatically on System Startup. |
Bamboo Server | Use these commands from the Bamboo installation directory:
On Windows, use:
See also Running Bamboo as a service. |
| Bitbucket Server | # service atlbitbucket status # service atlbitbucket stop # service atlbitbucket start |
| Fisheye | Use these commands from the Fisheye installation directory:
On Windows, use:
|
| Crucible | Use these commands from the Crucible installation directory:
On Windows, use:
See also Running Crucible as a Windows service. |
| Crowd | Use these commands from the Crowd installation directory:
On Windows, use:
See also Installing Crowd as a Windows Service. |
Locate and edit its server.xml
Below a list of its location for each one of the Atlassian's applications:
The location of your server.xml file depends on your application, operating system, and installation location.
Common default installation locations for Atlassian applications are:
- Linux:
/opt/atlassian/<application-name> - Windows:
C:\Program Files\Atlassian\<application-name> - Windows:
C:\Atlassian\<application-name>
The default locations of server.xml files for Atlassian applications are:
| Application | server.xml location |
|---|---|
| JIRA applications | <install-path>/conf/server.xml |
| Confluence | <install-path>/conf/server.xml |
| Bamboo | <install-path>/conf/server.xml |
| Bitbucket 5.0 and later | N/A, replaced by Please read through Migrate server.xml customizations to bitbucket.properties |
| Bitbucket Server 4.0 – 4.14 |
|
| Stash 3.8 – 3.11 |
|
| Stash 3.7 and earlier | <install-path>/conf/server.xml |
| Fisheye | The Fisheye configuration file is config.xml, but see Configuring the Fisheye web server. |
| Crucible | As for Fisheye. |
| Crowd |
Note that |
<install-path> refers to where the application was installed on your system.
Locate the Connectors
Find the following lines in server.xml:
<Server port="8006" shutdown="SHUTDOWN">
...
<Connector port="7990" protocol="HTTP/1.1"
connectionTimeout="20000"
useBodyEncodingForURI="true"
redirectPort="8443"
compression="on"
compressableMimeType="text/html,text/xml,text/plain,text/css,application/json"/>
You need to modify both the server port (the default is 8006) and the connector port (the default is 7990) to ports that are free on your machine. The server port is required by Tomcat but is not user-facing in any way. The connector port is the port you use to access Bitbucket Server. For example, in the snippet above, the URL would be http://example.com:7990/.
You can use netstat to identify free ports on your machine. See more information on using netstat on Windows.
If you are using a firewall, you should ensure that it is configured to allow HTTP or HTTPS traffic over the connector port you have chosen.
If you are running your Atlassian application on a Linux server and want to bind to privileged ports (those below 1024, for example port 80), you will need to start Bitbucket Server as root in order to successfully bind to the port. As this is not recommended, you should alternatively consider:
- Bind Bitbucket Server to a port over 1024 and then configure iptables to redirect traffic from port 80 to the higher port.