Content Unreachable

We're having trouble accessing your IPFS content right now.

What happened?

This usually occurs when IPNS name resolution fails or the IPFS peers serving your content are currently unreachable. Don't worry - this is often temporary and can be resolved with a few simple steps.

Troubleshooting Steps

For IPNS Users

If you're using IPNS (InterPlanetary Name System), your naming record might need to be republished or updated.

🔍 IPNS Checker

Check IPFS Content Reachability

Verify if your content is properly distributed across the IPFS network using these diagnostic tools:

🔍 IPFS Checker 🌍 IPNI Discovery

Network Status

Sometimes the issue is temporary network connectivity. Try accessing your content through different gateways.

🌐 Gateway Status

Still Having Issues?

If the problem persists after trying these steps, it might be a temporary network propagation issue.

If you require additional assistance please join our Discord server and create a ticket in the #support-tickets channel and we will get back to you as soon as we can.

📜 Get Help

🚀 Hosted IPFS Services

If managing your own IPFS infrastructure is challenging, consider using hosted services for more reliable IPFS and IPNS hosting:

🚀 Fleek 📁 Filebase

These services handle IPFS pinning, IPNS records management, and provide reliable gateways without requiring you to run your own IPFS node.

If you are already using a hosted IPFS/IPNS service provider please double-check the following:

1Ensure the IPFS content has been uploaded and pinned with the provider.

2Verify all IPNS configurations and ensure the record points to the latest version of your content (CID).

3Consider any provider related outages by checking their service status pages and optionally engaging with support staff who might be able to assist you.

4Confirm the content is reachable by using the IPNS and IPFS checker utilities.

Alternative: Self-Hosted IPNS

If you want to self-host your content and manage your own IPNS record, follow these steps:

1Ensure your IPFS node is running and reachable

Make sure your IPFS daemon is active:

ipfs daemon

Your IPFS daemon should remain online and be publicly accessible for best results. NAT and firewall rules can often lead to your IPFS node becoming unreachable.

2Publish your IPNS record

Ensure that your content has been assigned a CID and is pinned to your node:

ipfs add --cid-version 1 <file|directory>

Pin the CID from the output of the above command:

ipfs pin add ${CID}

Replace ${CID} with your actual IPFS content identifier:

ipfs name publish ${CID}

(Optional) - Each IPNS record has configurable TTL (default 1h) and lifetime (default 48h) settings. Depending on your circumstances you may wish to increase or decrease these values when publishing your record. For example:

ipfs name publish --ttl 5m --lifetime 24h ${CID}

Note - These settings can cause unexpected resolution problems. The default values are usually sufficient in most scenarios.

3(Optional) Configure record republishing

By default, Kubo will republish IPNS records every 4 hours. This setting can be modified in Kubo's configuration. The republishing interval should be set lower than the record liftime:

ipfs config --json Ipns.RepublishPeriod "1h"

4Wait for propagation

IPNS propagation can take several minutes to complete across the network.

5Verify the record

Replace ${IpnsRecord} with the output of the IPNS record from step 2:

ipfs name resolve ${IpnsRecord}

For best results, consider testing IPNS resolution from a different peer in order to verify DHT propagation.

Need more help? Visit the IPNS documentation for detailed information.