Error: routing: not found when executing "dht findpeer" command

I am basically following the steps in this blogpost: regarding interacting with the DHT.

So I basically run this:

ipfs dht findprovs QmW2WQi7j6c7UgJTarActp7tDNikE4B2qXtFCfLPdsgaTQ

and out of the peers it returns I now run

ipfs dht findpeer <cid>

But this always result into Error: routing: not found after about a couple of minutes.

What am I doing wrong?

What am I doing wrong?

tried a couple of more PeerId and running ipfs dht findpeer against those resolved. Explanation is that although the DHT knows the content can be found on the listed nodes, some might currently be offline.

You’re correct. If you run ipfs dht findpeer and can’t find the peer, chances are the peer is offline.

Hey. Referring to this issue . If the node is online and ipfs dht findpeer still results in Error Routing what would be the solution to it.
Also can we on default show our public ip in multiaddrs or to other node when ipfs id outputs liat of addrs.
Please guide.

@stebalien @dadepo.
Anyone if could possibly guide.

I’m having trouble understanding what you’re saying.

@stebalien referring to this link “checking address part” it says your third address must be public ip. How can we enable it? what would be the cases that it will show your public ip address in ipfs id addresses list.
In my case only local ip is in the list and on default it never showed public ip for addresses list.