Error Dialing Peers - running full node

I’m using the Persisted Peer field that’s mentioned here https://cosmos.network/docs/getting-started/full-node.html#genesis-seeds But it says in this log `Error creating peer` (cause: Expected field type 496E74657266616365, got 427974654C656E677468` Are these Persisted Field values I’m getting from each node okay? Correct string concatenation of values? https://explorecosmos.network/nodes ``` I[07-22|08:11:17.511] Ensure peers module=p2p numOutPeers=0 numInPeers=0 numDialing=0 numToDial=10 I[07-22|08:11:17.511] No addresses to dial nor connected peers. Falling back to seeds module=p2p I[07-22|08:11:17.511] Dialing peer module=p2p [email protected]:26656 E[07-22|08:11:17.934] Error dialing seed module=p2p err="Error{`Error creating peer` (cause: Expected field type 496E74657266616365, got 427974654C656E677468)}" [email protected]:26656 I[07-22|08:11:17.934] Dialing peer module=p2p [email protected]:26656…

Excerpt (1181 of 3118 characters). Read the whole post on the forum ↗

looks like right values in the string, if you compare to the section ‘Connecting To Peers’ from these Tendermint docs
https://tendermint.readthedocs.io/projects/tools/en/master/using-tendermint.html?highlight=seed%20nodes

There’s an open issue for that: https://github.com/cosmos/cosmos-sdk/issues/1767

thanks I reviewed the GithubIssue and its solution - so I removed addrbook.json and didn’t have any value for private_peer_ids in config.toml. Still getting same error.

The instructions says to use the Persistent Peer value (from cosmos explorer nodes) as seed, but there’s also a persistent_peers field in config.toml so maybe it should go there? If i try that I can get a slightly different error:

I[07-25|12:28:56.926] Dialing peer                                 module=p2p [email protected]:26656
E[07-25|12:28:57.121] Error dialing peer                           module=p2p err="Error{`Error creating peer` (cause: dial tcp 172.31.42.204:26656: i/o timeout)}"

I wanted to find some new addresses to put in config.toml but Cosmos Explorer is down.

I’ll keep posted

The last testnet halted and the explorer is still pointed thwre. We are bringing the network back up today and the explorer should be available again at that time.