Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/reference/diagnostic-tools.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,15 +18,15 @@ Here are several tools you can use to investigate and diagnose common issues wit

## IPFS check

[IPFS Check](https://check.ipfs.network/) helps determine the retrievability of a CID from IPFS Mainnet, either from a specific peer given a multiaddress, or from multiple providers.
[IPFS Check](https://check.ipfs.network/) helps determine the retrievability of a CID from IPFS [Mainnet](../concepts/glossary.md#mainnet), either from a specific peer given a multiaddress, or from multiple providers.

@[youtube](XeNOQDOrdC0)

Each error type output by the tool can indicate a solution to your problem:

- **Could not connect to the multiaddr** indicates that machines on the internet cannot talk to your machine. Fix your firewall, add port forwarding, or use a relay.
- **Could not find address in the DHT** indicates that your machine is either not connected to the Amino DHT (even as a client), or it is not advertising the address that you are using to test.
- **Multihash not advertised in the DHT** indicates that your machine has not advertised that it has the requested content in the Amino DHT. If you're using Kubo, enable the [Accelerated DHT Client](https://github.com/ipfs/go-ipfs/blob/master/docs/experimental-features.md#accelerated-dht-client).
- **Multihash not advertised in the DHT** indicates that your machine has not advertised that it has the requested content in the Amino DHT.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rationale: we know there could be other reasons, such as people just unknowingly disabling announcements via lowpower profile (ipfs/kubo#10524).

Let's remove this kubo-specific suggestion, as it may do more harm than good (we know that it makes Kubo-based gateway perform worse with accelerated client enabled (notes))

- **Peer has not responded that it has the CID** indicates that your node cannot find the block that you believe it has, or that there may be some other sort of network latency.

## CID inspector
Expand Down