erigon-network-ports

To avoid port conflicts with multiple Erigon instances, you must assign unique network ports to each node. This involves adjusting CLI flags like --port, --http.port, and --ws.port for gRPC, HTTP, WS, and beacon services.

Erigon uses various default network ports for gRPC, HTTP, WS, P2P, and auxiliary services like beacon, caplin, and sentinels. This Skill enumerates these default port bindings and their protocols for clear visibility.

For a second Erigon node deployment, you need to change CLI flags such as --port, --http.port, and --ws.port. Adjusting these ensures distinct bindings per instance and prevents network conflicts.

Yes, this port management reference covers auxiliary services including caplin and sentinels. It documents every port-binding flag, its default, and protocol to ensure deterministic port configurations across all Erigon services.

Deterministic port configurations are needed for Erigon nodes to enable easy cross-instance validation. By enumerating CLI flags and defaults, you ensure distinct bindings per instance and prevent deployment conflicts on the same host.