This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
"You are not connected to any peers. There is most likely some network issue. Fix connectivity." #7556
Labels
M2-config 📂
Chain specifications and node configurations.
Z1-question 🙋♀️
Issue is a question. Closer should answer.
Milestone
I started off running Parity fine, then eventually was only connected to a single peer. This dropped off to 0 peers and now the display shows "You are not connected to any peers. There is most likely some network issue. Fix connectivity."
I'm running:
My issues seems to be identical to #6945 which was marked as "Fixed", though there doesn't seem to be a solution shared.
Here is a log of a run attempt with ./target/release/parity --testnet --config testnet_config.toml
parity-testnet.log
Not sure how typical it is to encounter peers with a different genesis block, but it is happening a lot:
genesis hash mismatch (ours: a3c5…2cb9, theirs: b2a5…6659)
The text was updated successfully, but these errors were encountered: