Skip to content
You are reading Pantheon development version documentation and some displayed features may not be available in the stable release. You can switch to stable version using the version box at screen bottom.

Configuring Ports

Ports must be exposed appropriately to enable communication. An example port configuration for a Pantheon node on AWS is:

Port Configuration

When running Pantheon from the Docker image, expose ports.

P2P Networking

To enable peer discovery, the P2P UDP port must be open for inbound connections.

We also recommended opening the P2P TCP port for inbound connections. This is not strictly required because Pantheon attempts to initiate outbound TCP connections. However, if no nodes on the network are accepting inbound TCP connections, nodes cannot communicate.

The P2P port is specified by the --p2p-port option. The default is 30303.


To enable access to the JSON-RPC API, open the HTTP JSON-RPC and WebSockets JSON-RPC ports to the intended users of the JSON-RPC API on TCP.

The --rpc-http-port and --rpc-ws-port options specify the HTTP and WebSockets JSON-RPC ports. The defaults are 8545 and 8546.


To enable Prometheus to access Pantheon, open the metrics port or metrics push port to Prometheus or the Prometheus push gateway on TCP.

The --metrics-port and --metrics-push-port options specify the ports for Prometheus and Prometheus push gateway. The defaults are 9545 and 9001.

Questions or feedback? You can discuss issues and obtain free support on Pantheon Gitter channel.
For paid professional support by PegaSys, contact us at [email protected]