Port Usage

CloudBees Flow uses certain ports by default. Make sure your firewall is open for these ports. This section contains the default port values and information about avoiding port conflicts.

Transport Layer Security (TLS) has replaced Secure Sockets Layer version 3.0 (SSLv3) on the CloudBees Flow server and the CloudBees Flow web server.

Default Server Ports

CloudBees Flow servers use the following ports:

Port Used by


CloudBees Flow server


CloudBees Flow server (SSL port)


CloudBees Flow web server


CloudBees Flow web server when installed on Linux platforms without root privileges


CloudBees Flow web server (SSL port)


CloudBees Flow web server (SSL port) when installed on Linux platforms without root privileges


Port used by the CloudBees Flow agent for HTTP communication on the localhost network interface


CloudBees Flow agents (by default, this is an HTTPS port)


Preflight file transfer port, other file transfer, event notifications, or other messaging


Artifact repository server (by default, this is an HTTPS port)


CloudBees Flow built-in (default) database. You can change this port number by using the ecconfigure --databasePort <port_number> option or the --databasePort installer argument.

Default CloudBees Flow Services Ports

The Java Service Wrapper uses the following ports to communicate with a Java virtual machine (JVM):

Port Used by

CloudBees Flow agents

CloudBees Flow server

Artifact repository

Default DevOps Insight Server Ports

The CloudBees Flow DevOps Insight server uses the following ports:

Port Used by


DevOps Insight server to retrieve data from Elasticsearch


Used by the Elasticsearch service for internal communication between nodes within the Elasticsearch cluster


Logstash to receive data from CloudBees Flow


Used by the Logstash service for the Logstash monitoring APIs

Avoiding Port Conflicts

If you are installing a CloudBees Flow server and your web server or other application uses the same ports as the CloudBees Flow host, you must take one of the following actions:

  • Select different web server or application ports

  • 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

Copyright © 2010-2020 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about. Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.