Chronos, no peers available

Support
13

Chronos “No Peers” Emergency Fix

Overview: If your Chronos node is stuck at “0 peers,” it is likely a “Cold Start” discovery issue. Since Chronos uses a single bootstrap node, you need to manually point your machine to a reliable “anchor.”

Step 1: Get the Peer Multiaddr

You need the address of a stable node (either yours or a trusted friend).

  • Find the ID: Look for Local node identity is: 12D3KooW... in your terminal logs.

  • Format the Address: It should look like this: /ip4/[PUBLIC_IP]/tcp/30333/p2p/[PEER_ID]

Step 2: Update your Startup Command

Add these specific flags to your node execution command. This tells your node exactly where to look for peers.

Bash

# Force discovery via a known node
--bootstrap-node /ip4/[IP_ADDRESS]/tcp/30333/p2p/[PEER_ID]

# Ensure the DSN layer also connects
--dsn-bootstrap-node /ip4/[IP_ADDRESS]/tcp/30533/p2p/[PEER_ID]

# IMPORTANT: Keep the connection alive
--reserved-peer /ip4/[IP_ADDRESS]/tcp/30333/p2p/[PEER_ID]

Step 3: Troubleshooting “Local” Blocks

  • LAN/Private Setup: If your nodes are on the same local network, add --allow-private-ips.

  • Network Congestion: If your ISP is shaky, increase your connection attempts: --out-peers 16.

  • IPv6: If you have a routable IPv6, try using the /ip6/ multiaddr instead of /ip4/ to bypass IPv4 routing bottlenecks.