This section contains the default port values for CloudBees CD/RO servers and CloudBees Analytics servers, along with a list of additional ports available for use. There is also information about avoiding and resolving port conflicts.
Ensure your firewall is open for these ports. These port values apply to all Product and OS versions.
Transport Layer Security (TLS) has replaced Secure Sockets Layer version 3.0 (SSLv3) on the CloudBees CD/RO server and the CloudBees CD/RO web server. |
Default server ports
CloudBees CD/RO servers use the following ports:
Port | Used by |
---|---|
8000 |
CloudBees CD/RO server |
8443 |
CloudBees CD/RO server (SSL port) |
80 |
CloudBees CD/RO web server |
7080 |
CloudBees CD/RO web server when installed on Linux platforms without root privileges. |
443 |
CloudBees CD/RO web server (SSL port). You can also use this port for access to the application server API (XML-, JSON-, and REST-based). |
7443 |
CloudBees CD/RO web server (SSL port) when installed on Linux platforms without root privileges. |
6800 |
Port used by the CloudBees CD/RO agent for HTTP communication on the localhost network interface. |
7800 |
CloudBees CD/RO agents (By default, this is an HTTPS port.) |
61613 |
STOMP port used for transferring log files when using the EC-FlowLogCollector plugin, by |
8200 |
Artifact repository server (By default, this is an HTTPS port.) |
8900 |
CloudBees CD/RO built-in (default) database. You can change this port number by using the |
Default CloudBees CD/RO services ports
The Java Service Wrapper uses the following ports to communicate with a Java virtual machine (JVM):
Port | Used by |
---|---|
127.0.0.1:32000 |
CloudBees CD/RO agents |
127.0.0.1:32001 |
CloudBees CD/RO server |
127.0.0.1:32002 |
Artifact repository |
Default CloudBees Analytics server ports
The CloudBees Analytics server uses the following ports:
Port | Used by |
---|---|
9201 |
CloudBees Analytics server to retrieve data. |
9301 |
Used by the CloudBees Analytics service for internal communication between nodes within the cluster. |
Default CloudBees CD/RO ZooKeeper ports
The following ports are assigned to ZooKeeper in the default CloudBees CD/RO Kubernetes Helm charts:
Port | Used by |
---|---|
53 |
ZooKeeper network policy |
2181 |
CloudBees CD/RO server |
2888 |
ZooKeeper server |
3888 |
ZooKeeper server replicas |
Additional ports
The following ports are available for use.
Port | Description | Server | Client | Comment |
---|---|---|---|---|
22 |
Universal (proxy) agent |
Proxy agent |
Proxy target |
Default when used |
25 |
SMTP mail server |
CloudBees CD/RO server |
Default |
|
138 |
SMB/CIFS |
Workspace storage |
CloudBees CD/RO agent/apache |
Optional |
139 |
SMB/CIFS |
Workspace storage |
CloudBees CD/RO agent/apache |
Optional |
389 |
Active Directory or LDAP server |
Active Directory or LDAP |
CloudBees CD/RO server |
Default |
445 |
SMB/CIFS |
Workspace storage |
Agent/apache |
Optional |
465 |
SSMTP mail server |
CloudBees CD/RO server |
Default |
|
636 |
Active Directory or LDAP server |
Active Directory or LDAP |
CloudBees CD/RO server |
Default |
1433 |
Database |
SQL Server |
CloudBees CD/RO server |
Default when used |
1521 |
Database |
Oracle |
CloudBees CD/RO server |
Default when used |
2049 |
NFS |
Workspace storage |
CloudBees CD/RO agent and apache |
Optional |
3306 |
Database |
MySQL |
CloudBees CD/RO server |
Default when used |
5445 |
Apache ActiveMQ |
Only when CloudBees CD/RO server is clustered. |
Peer CloudBees CD/RO server in the cluster. |
Only when CloudBees CD/RO server is clustered. |
5446-5449 |
JGroups |
Only when CloudBees CD/RO server is clustered. |
Peer CloudBees CD/RO server in the cluster. |
Only when CloudBees CD/RO server is clustered. (The two for TCP and two for Failure detection account for the four JGroups ports.) |
9500 |
Avoiding port conflicts
If you are using ports to install CloudBees CD/RO components on a system and the port is already in use, take one of the following actions:
-
Select a different web server or application port.
-
Uninstall the existing web server or application.
-
Disable the existing web server or application.
-
Reconfigure the existing web server or application to use another port.