Changing port that your Atlassian application listens on
This article only applies to the Atlassian server platform. Learn more about the differences between cloud and server.
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
Locate and edit its server.xml
Below a list of its location for each one of the Atlassian's applications:
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 or on Linux.
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:
- DRAFT - Proxying Atlassian Tools
- Bind Bitbucket Server to a port over 1024 and then configure iptables to redirect traffic from port 80 to the higher port.