Github -> Issues -> Here -> Search -> Gateway -> ipfs.io -> dweb.link

Help IPFS
41

Yay, it just started to work properly:

> ipfs dht findpeer 12D3KooWHWen2dsu4QWJE7srfSFduVPKTnGQ8jbx5MtG7iQc7YWD
/ip6/::1/udp/4001/quic
/ip4/192.168.33.135/tcp/4001
/ip6/64:ff9b::689c:1875/tcp/4001
/ip6/::1/tcp/4001
/ip4/127.0.0.1/udp/4001/quic
/ip4/127.0.0.1/tcp/4001
/ip4/192.168.33.135/udp/4001/quic
/ip4/104.156.24.117/tcp/4001
/ip4/104.156.24.117/udp/4001/quic

The only thing is that it advertises an IPv6 address, but doesn’t answer on it (it might be an error).

P.S. You can count the IPv6 inbounds with the following command:

> ipfs swarm peers --direction | grep '^/ip6/.\+\sinbound$' | wc -l
      64
42

That command without the 64 at the end returns 0 inbound ipv6
Not surprised. Last I checked my ISP wasn’t yet supporting ipv6

43

The 64 was my result when I ran it on my own node, sorry. I don’t understand why your node is advertising an IPv6 address then.

An easy way to get rid of it is to remove the 2 ip6 lines from Addresses.Swarm (which is fine, since your node doesn’t use IPv6).

Also, your node has begun to advertise some more ports too, something weird is going on:

> ipfs dht findpeer 12D3KooWHWen2dsu4QWJE7srfSFduVPKTnGQ8jbx5MtG7iQc7YWD
/ip4/104.156.24.117/tcp/4001
/ip4/104.156.24.117/udp/1026/quic
/ip6/::1/tcp/4001
/ip4/127.0.0.1/udp/4001/quic
/ip6/64:ff9b::689c:1875/tcp/4001
/ip6/::1/udp/4001/quic
/ip4/104.156.24.117/udp/4001/quic
/ip4/104.156.24.117/tcp/1024
/ip4/192.168.33.135/tcp/4001
/ip4/127.0.0.1/tcp/4001
/ip4/192.168.33.135/udp/4001/quic
44

Removed the 2 ip6 lines from Addresses.Swarm
With daemon running in cli, is there something I can enter, instead of ctrl-c to exit the daemon, and to restart?

45

Nah, ctl-C is fine. In theory, there’s an “ipfs shutdown” command, but I’ve never had much luck with it.

46

I did an ipv6 connectivity check and it came back as bad for my router IP.
Time to call it a successful day and relax for a while.
Once again, many thanks.

47

My go-ipfs daemon is now saying its config bootstraps and/or peers need updating. I currently have some bootstraps listed with none responding apparently. No peers listed in my config. Where do I find updated info for these sections which should be reliable? It does go ahead and start as is.

48

It’s more likely that your node is unable to communicate at all (I’m not aware of any changes in the bootstrap list).

P.S. Juuust in case you have a really old list, here is a copy of mine:

"Bootstrap": [
  "/ip4/104.131.131.82/tcp/4001/p2p/QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ",
  "/ip4/104.131.131.82/udp/4001/quic/p2p/QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ",
  "/dnsaddr/bootstrap.libp2p.io/p2p/QmNnooDu7bfjPFoTZYxMNLWUQJyrVwtbZg5gBMjTezGAJN",
  "/dnsaddr/bootstrap.libp2p.io/p2p/QmQCU2EcMqAqQPR2i9bChDtGNJchTbq5TbXJJ16u19uLTa",
  "/dnsaddr/bootstrap.libp2p.io/p2p/QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb",
  "/dnsaddr/bootstrap.libp2p.io/p2p/QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt"
],
49

Thanks again for all your help. That list did eliminate the daemon error soon after startup.

50

The node that file was on crashed and there wasn’t a proper backup. The content is being loaded on a new node, including several websites. After the new node is loaded, the new location will be announced at Web3 Only Podcast – Telegram (no need for a telegram account to view)