A newer version of this documentation is available.

View Latest

Network Configuration

Couchbase Server uses specific network ports for communication between server components and with the clients accessing the data stored in the Couchbase Server cluster.

The ports listed in the following table must be open on the host for Couchbase Server to operate correctly. Couchbase Server configures these ports automatically, but you must verify that any firewall configuration allows communication on the specified ports for each usage type. If this is not done, the node can experience difficulty in joining a cluster, including acting as a cluster of one node rather than joining the intended cluster.

The following table lists the ports used for different types of Couchbase Server network communication:

Node-to-node

Couchbase Server uses these ports for communication between all nodes within the cluster. These ports must be open to enable nodes to communicate with each other.

Node-to-client

These ports should be open between each node within the cluster and any client nodes accessing data within the cluster.

Cluster administration

Couchbase Server uses these ports for administration via the REST API, command-line clients, and web browsers.

XDCR

These ports are used for XDCR (Cross Datacenter Replication) communication between all nodes in both the source and destination clusters.

Port Description Node-to-node Node-to-client* Cluster administration XDCR v1 (CAPI) XDCR v2 (XMEM)

8091

Used by the Couchbase Web Console for REST/HTTP traffic.

Yes

Yes

Yes

Yes

Yes

8092

Used to access views, run queries, XDCR and update design documents.

Yes

Yes

No

Yes

Yes

8093

Used by query services for REST/HTTP traffic.

Yes

Yes

No

Yes

Yes

9100

Internal index admin port (-adminPort).

Yes

No

No

No

No

9101

Internal index scan port (-scanPort).

Yes

No

No

No

No

9102

Internal index HTTP port (-httpPort).

Yes

No

Yes

No

No

9103

Internal index build port (-streamInitPort).

Yes

No

No

No

No

9104

Internal index build port (-streamCatchupPort ).

Yes

No

No

No

No

9105

Internal index maintenance port (-streamMaintPort).

Yes

No

No

No

No

9998

Internal REST port.

No

No

Yes

Yes

Yes

9999

Internal GSI port used by the internal administrators.

Yes

No

No

No

No

11207**

Used by smart client libraries to access data nodes using SSL. This is a memcached SSL port.

No

Yes

No

No

Yes when SSL is used

11209

Internal Bucket Port.

Yes

No

No

No

No

11210**

Used by smart client libraries or Moxi to directly connect to the data nodes. The XDCR client uses this port as well as the SDKs. This is a memcached port.

Yes

Yes

No

No

Yes

11211

Used by pre-existing Couchbase Server and memcached (non-smart) client libraries (such as Moxi).

No

Yes

No

No

No

11214

Used for SSL XDCR data encryption.

No

No

No

No

Yes

11215

Used for SSL XDCR data encryption.

No

No

No

No

Yes

18091

Used by the Couchbase Web Console for REST/HTTP traffic with SSL.

No

Yes

Yes

No

Yes

18092

Used to access views, run queries, XDCR and update design documents with SSL.

No

Yes

No

No

Yes

18093

N1QL SSL port

Yes

Yes

No

Yes

Yes

4369

Erlang Port Mapper ( epmd )

Yes

No

No

No

No

21100 to 21299 (inclusive)

Node data exchange.

Yes

No

No

No

No

  • bi-directional

    • This port has to be open for GOXDCR to connect to target memcached.

Port 11213 is an internal port used on the local host for memcached and triggering manual compaction. The port is not used for communication between cluster nodes. For firewall purposes, you do not need to take port 11213 into consideration. However, if another service is listening on this port, the Couchbase Server service will not start.