Ports used by Atlassian Data Center Applications

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

This page lists the ports used by Atlassian Data Center applications.

We'll indicate if the port needs to be accessible through your firewall as follows:

  • open/public - required for external communication.

  • closed/private - only required for internal communication, for example between data center nodes.

Solution

Outbound ports

Description

Port

Description

Outbound traffic

443

Mostly used for communicating with Atlassian Marketplace and sending analytics data (if you've opted in).

SMTP

25

Used for sending email notifications

Customizing ports

To find out which ports are in use on your server use the netstat command.

If one of the default ports listed on this page is already in use, it may be possible to change it. This is usually done in your application's server.xml file, or via a system property.

See Changing port that your Atlassian application listens on or refer to the documentation for your product.

Bamboo

This documentation is primarily intended for Bamboo Data Center users. As of February 15, 2024, Bamboo will no longer be supported. While some of the information here may still apply to Bamboo, users are encouraged to transition to Bamboo Data Center for continued support and updates. Please ensure you are aware of the differences and plan your migration accordingly.

Application or service

Default port

Access

Bamboo

8085

Open/public

Primary ActiveMQ/JMS

54663

Closed/private (only required for remote agents)

SSL JMS connector (primary JMS connector port number + 1)

54664

Closed/private (only required for remote agents connection over SSL)

Elastic agents JMS connector (primary JMS connector port number + 2)

54665

Closed/private (runs on localhost only, required for elastic agents connection)

Internal Node Communication

9090

Closed/private (only required for inter-node communication in Data Center)

gRPC Internal communication port

9090

Closed/private (only required for other Bamboo nodes in HA setup)

Bitbucket Data Center

Application or service

Default port

Access

Bitbucket

7990

Open/public

Bitbucket SSH

7999

Open/public (only required if SSH is enabled)

Elasticsearch

7992

7993

Open/public

Open/public

Remote Elasticsearch server

9200

Open/public (only required for Data Center)

Hazelcast

5701

Closed/private (only required for inter-node communication in Data Center)

Confluence Data Center

Application or service

Default port

Access

Confluence

8090

Open/public

Synchrony

8091

Open/public if you're running Synchrony standalone cluster, or you have disabled the Synchrony proxy.

Closed/private if Synchrony is managed by Confluence, via synchrony-proxy

Hazelcast (Confluence)

5801

Closed/private (only required for inter-node communication in Data Center)

Hazelcast (Synchrony)

5701

Closed/private (only required for inter-node communication in Data Center)

Cluster base port (Synchrony)

25500

Closed/private (only required for inter-node communication in Data Center)

Multicast port (Synchrony)

54327

Closed/private (only required if you're running Synchrony standalone cluster in Data Center)

See Possible Confluence and Synchrony Configurations for more information on the options for running Synchrony.

Crowd Data Center

Application or service

Default port

Access

Crowd

8095

Open/public

Fisheye and Crucible

Application or service

Default port

Access

Fisheye Crucible

8060

Open/public

Jira Data Center

Application or service

Default port

Access

Jira

8080

Open/public

Ehcache

40001

Closed/private (only required for inter-node communication in Data Center)

Ehcache object

40011

Closed/private (it is set by default in JIRA 7.13.1 or higher, earlier versions of JIRA can use the setting ehcache.object.port = 40011 in the cluster.properties file)

Tomcat Control Port

Tomcat is the application server that runs most Atlassian products. By default the control port is 8000.

Although we don't recommend running multiple applications on the same server, if you attempt to do this, you'll need to change the control port in the application's server.xml file, to ensure it is unique for each application.

Default database ports

You should check the documentation for your particular database or version.

Database vendor

Default port

PostgreSQL

5432

MariaDB

3306

Microsoft SQL Server

1433

MySQL

3306

Oracle

1521

Not all of the databases above are supported for every Atlassian product, so be sure to check the documentation for each product to find out which databases are supported.

Default LDAP ports

To setup an external user directory in Jira, follow instructions on Connecting to an LDAP directory.

Service

Default port

LDAP

389

LDAPS (SSL/TLS)

636

You should also check the recommendation from each identity provider.

Default SMTP (mail server) ports

Most Atlassian applications will have a mail server configured, for sending notifications. Mail servers are usually configured to use port 25.

Updated on April 17, 2025

Still need help?

The Atlassian Community is here for you.