Go-ipfs no peer connections

My node machine ran out of disk space and that has been resolved. Rebooted after that… Since then after starting ‘ipfs daemon’ I have zero peer connections. Searching thru help I haven’t found a solution. Already ran 'ipfs-update install latest`, even though I already had the latest. Advice to resolve the following will be much appreciated. The following is displayed when attempting to start daemon:
Initializing daemon…
go-ipfs version: 0.8.0
Repo version: 11
System version: amd64/linux
Golang version: go1.15.8
2021/05/08 19:09:22 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Receive Buffer Size · lucas-clemente/quic-go Wiki · GitHub for details.
Swarm listening on /ip4/
Swarm listening on /ip4/
Swarm listening on /ip4/
Swarm listening on /ip4/
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /ip6/::1/udp/4001/quic
Swarm listening on /p2p-circuit
Swarm announcing /ip4/
Swarm announcing /ip4/
Swarm announcing /ip4/
Swarm announcing /ip4/
Swarm announcing /ip6/::1/tcp/4001
Swarm announcing /ip6/::1/udp/4001/quic
API server listening on /ip4/
Gateway (readonly) server listening on /ip4/
Daemon is ready
2021-05-08T19:25:56.036-0500 ERROR reprovider.simple failed to reprovide: failed to find any peer in table

‘ipfs swarm addrs’ generates the following:
12D3KooWHWen2dsu4QWJE7srfSFduVPKTnGQ8jbx5MtG7iQc7YWD (6)
QmNnooDu7bfjPFoTZYxMNLWUQJyrVwtbZg5gBMjTezGAJN (1)
QmQCU2EcMqAqQPR2i9bChDtGNJchTbq5TbXJJ16u19uLTa (1)
QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ (2)
QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb (1)
QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt (1)

Resolved by adding a peer which must have restored the peer table

Hello! I have exactly the same problem:

2021-05-09T17:24:04.383+0200 ERROR reprovider.simple failed to reprovide: failed to find any peer in table

I don’t know much about the terminal, until now I only used IPFS Desktop on my MAC, but since there are 0 peers I have decided to install it via CLI in the terminal.
Can you please tell me how can I add a new peer to solve this problem?

Thank you.

In IPFS Desktop, select PEERS in the left sidebar.
Select + Add Connection in the upper right corner.
In the popup field paste the following:

That will add a peer to the peer table and allow the IPFS daemon to start properly with a swarm of peer connections


So does that mean that out of the box none of the bootstrap lists are working?

I had this originally:

  "Bootstrap": [

…but no peers at all. Running with

IPFS_LOGGING=verbose ipfs daemon

just showed a whole bunch of dns resolution errors and “dial” failures.

after adding yours, it all came up ok.

It has worked!! Thank you!

1 Like

Had the same problem this morning on a different Linux machine which did not run out of disk space. Also running go-ipfs latest version. Corrected by adding peer with command
ipfs swarm connect address, instead of using GUI

It happened about 8-hours ago with the node running and over 800 peers. It caused my daemon to loose all peer connections.

If this happens to any of my 3 other nodes which haven’t yet experienced the problem, is there some troubleshooting data I can capture to help?

1 Like

I’m not sure but I believe your issue is the same as this, maybe you could offer some input? Node failed to negotiate security protocol and can't connect to any node. · Issue #8120 · ipfs/go-ipfs · GitHub

It seems that the peer table is either being corrupted or deleted. Manually connecting to a peer either corrects or replaces the peer table. There is nothing in the messages generated about a security protocol.

If this happens again one thing you should check is running ipfs swarm connect on each of the peers in your bootstrap list (ipfs bootstrap list) and reporting the results (e.g. were the connections successful, do you start to accumulate more peers, etc.)

If everything starts working again then it’s likely there’s some kind of bug in go-ipfs. However, if those connections fail then it likely means you’re having trouble with the bootstrap nodes which could have a variety of causes (your ISP blocking the nodes, DNS issues for the peers with DNSAddrs, issues with the bootstrap nodes, etc.) which can then start to be diagnosed.

1 Like