# Not Getting Any Peers

**Status: untested.** This note is based on prior node recovery observations and should be verified before treating it as a confirmed fix.

Likely fix for "installed node software but no peers":

1. If peer exposure looks correct but the node still cannot catch up, consider restoring from a verified recent snapshot taken from a current working node, then let the node resume normal peer discovery and readiness checks.
2. For the newer RC node stack, the peer port is `8150/tcp`.
3. Make sure the host firewall allows inbound `8150/tcp` and, if the node is behind a router, forward public `8150/tcp` to the node host.
4. If using an older pre-RC node stack, check that stack's documented peer ports and advertised external address instead of assuming the newer RC port.
5. When the RC stack was known to work, the node listened on `8150/tcp` and peer count came up with fresh peers. So after fixing exposure, let the installer/readiness wait finish rather than killing/restarting it early.

## Evidence Trail

- Prior RC package inspection recorded `8150/tcp` as the BlockDAG P2P port for node peers.
- After allowing the RC P2P port, reruns showed the node listening on that port and discovering fresh peers.
- A separate non-mining RC node also used the same P2P port and discovered fresh peers once healthy.

Short answer: if peer exposure looks correct but the node still cannot catch up, restore from a verified recent snapshot from a current working node. Also check, forward, and allow `8150/tcp` for current RC node software, and confirm the advertised/external address matches the host's current routing.