Problem
The icm-relayer's P2P client needs port 9651 for outbound connections, but avalanchego is already bound to 9651 on the same host. Running the relayer on a validator or RPC node causes failed to create app request network: failed to connect to any bootstrap nodes.
The ansible role deploys the relayer to the first RPC node by default, which has avalanchego running.
Options
- Deploy to a node without avalanchego (monitoring node)
- Document that the relayer needs a dedicated host or use separate P2P port
- Use the relayer's TLS cert from a different identity than the host's avalanchego
What Worked
We ran the relayer on the monitoring node (no avalanchego) with:
- Fresh staking certs generated by a temporary avalanchego instance
manually-tracked-peers with validator public IPs- Public Fuji API for
info-api and p-chain-api
allow-private-ips: true
The ansible role should support deploying to a non-avalanchego host.
Problem
The icm-relayer's P2P client needs port 9651 for outbound connections, but avalanchego is already bound to 9651 on the same host. Running the relayer on a validator or RPC node causes
failed to create app request network: failed to connect to any bootstrap nodes.The ansible role deploys the relayer to the first RPC node by default, which has avalanchego running.
Options
What Worked
We ran the relayer on the monitoring node (no avalanchego) with:
manually-tracked-peerswith validator public IPsinfo-apiandp-chain-apiallow-private-ips: trueThe ansible role should support deploying to a non-avalanchego host.