Couchbase Server uses a number of different network ports for communication between the different components of the server, and for communicating with clients that accessing the data stored in the Couchbase cluster. The ports listed must be available on the host for Couchbase Server to run and operate correctly. Couchbase Server will configure these ports automatically, but you must ensure that your firewall or IP tables configuration allow communication on the specified ports for each usage type. On Linux the installer will notify you that you need to open these ports.
The following table lists the ports used for different types of communication with Couchbase Server, as follows:
Node to Node
Where noted, these ports are used by Couchbase Server for communication between all nodes within the cluster. You must have these ports open on all to enable nodes to communicate with each other.
Node to Client
Where noted, these ports should be open between each node within the cluster and any client nodes accessing data within the cluster.
Cluster Administration
Where noted, these ports should be open and accessible to allow administration, whether using the REST API, command-line clients, and Web browser.
XDCR
Ports are used for XDCR communication between all nodes in both the source and destination clusters.
Table 2.1. Getting Started — Network Ports
| Port | Description | Node to Node | Node to Client | Cluster Administration | XDCR |
|---|---|---|---|---|---|
| 8091 | Web Administration Port | Yes | Yes | Yes | Yes |
| 8092 | Couchbase API Port | Yes | Yes | No | Yes |
| 11209 | Internal Cluster Port | Yes | No | No | No |
| 11210 | Internal Cluster Port | Yes | Yes | No | No |
| 11211 | Client interface (proxy) | Yes | Yes | No | No |
| 4369 | Erlang Port Mapper (epmd) | Yes | No | No | No |
| 21100 to 21199 (inclusive) | Node data exchange | Yes | No | No | No |