search

ipfs-cluster / archive-tools

Diverse scripts for archiving and pinning things on Clusters
2 stars 5 forks source link

Unable to join IPFS Websites cluster #10

Closed Luflosi closed 2 years ago

Luflosi commented 2 years ago

To reproduce, execute ipfs-cluster-follow ipfs-websites run --init ipfs-websites.collab.ipfscluster.io, as written on https://collab.ipfscluster.io/. It will output something like:

ipfs-websites.collab.ipfscluster.io will be assumed to be an DNSLink-powered address: /ipns/ipfs-websites.collab.ipfscluster.io.
It will be resolved using the local IPFS daemon's gateway ([::1]:8080).
If this is not the case, specify the full url starting with http:// or https://.
(You can override the gateway URL by setting IPFS_GATEWAY)
Identity written to /var/lib/ipfs-cluster-follow/ipfs-websites/identity.json.
Configuration written to /var/lib/ipfs-cluster-follow/ipfs-websites/service.json.
Cluster "ipfs-websites" follower peer initialized.
You can now use "ipfs-cluster-follow ipfs-websites run" to start a follower peer for this cluster.
(Remember to start your IPFS daemon before)
Starting the IPFS Cluster follower peer for "ipfs-websites".
CTRL-C to stop it.
Checking if IPFS is online (will wait for 2 minutes)...
waiting for IPFS to become available on /ip6/::1/tcp/5001...
2022-10-19T17:04:09.625+0200        INFO        config        config/config.go:362        loading configuration from http://[::1]:8080/ipns/ipfs-websites.collab.ipfscluster.io
reading the configurations in /var/lib/ipfs-cluster-follow/ipfs-websites: unsuccessful request (400): ipfs resolve -r /ipns/ipfs-websites.collab.ipfscluster.io: could not resolve name: "ipfs-websites.collab.ipfscluster.io" is missing a DNSLink record (https://docs.ipfs.io/concepts/dnslink/)

This happens because the there is no DNSLink record on the domain ipfs-websites.collab.ipfscluster.io:

$ dig +short @1.1.1.1 TXT _dnslink.ipfs-websites.collab.ipfscluster.io

outputs nothing, while all other domains listed on the website above do have a DNSLink record.

To fix this, the correct TXT record should be added to the domain again.

Sorry if this is not the correct repo to submit this issue but I don't know where else to report this.

hsanjuan commented 2 years ago

Thanks! I am not sure why dnssimple is doing this, but the TXT records are there. I have re-saved the zone and it has started working (dig @ns1.dnsimple.com TXT _dnslink.ipfs-websites.collab.ipfscluster.i o), but it will take a while to propagate.

Luflosi commented 2 years ago

Yep, it's working now. Thanks for the quick fix!