Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

From August 14th, 2024, Cloudflare hostnames will no longer connect to IPFS #1865

Closed
wants to merge 1 commit into from
Closed

From August 14th, 2024, Cloudflare hostnames will no longer connect to IPFS #1865

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 2 additions & 0 deletions docs/concepts/public-utilities.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,8 @@

Additionally, there's a community-maintained [tool for finding and testing public gateways](https://ipfs.github.io/public-gateway-checker/) such as the one operated by Cloudflare: `https://cf-ipfs.com`.

Please note that all traffic using the `https://cf-ipfs.com` or `https://cloudflare-ipfs.com` hostnames will continue to work without interruption and be redirected to ipfs.io or dweb.link until August 14th, 2024. After this date, the [Cloudflare hostnames will no longer connect to IPFS](https://blog.cloudflare.com/cloudflares-public-ipfs-gateways-and-supporting-interplanetary-shipyard). To ensure no service interruption, all users must switch to using ipfs.io or dweb.link as soon as possible ahead of the transition date. If you are using either of the Cloudflare hostnames, please be sure to switch to one of the new ones promptly to avoid any service disruptions.

Check failure on line 41 in docs/concepts/public-utilities.md

View workflow job for this annotation

GitHub Actions / pr-content-check 

[vale] reported by reviewdog 🐶
[ipfs-docs-style.PLNSpelling] Did you really mean 'hostnames'?

Raw Output:
{"message": "[ipfs-docs-style.PLNSpelling] Did you really mean 'hostnames'?", "location": {"path": "docs/concepts/public-utilities.md", "range": {"start": {"line": 41, "column": 95}}}, "severity": "ERROR"}

Check failure on line 41 in docs/concepts/public-utilities.md

View workflow job for this annotation

GitHub Actions / pr-content-check 

[vale] reported by reviewdog 🐶
[ipfs-docs-style.PLNSpelling] Did you really mean 'hostnames'?

Raw Output:
{"message": "[ipfs-docs-style.PLNSpelling] Did you really mean 'hostnames'?", "location": {"path": "docs/concepts/public-utilities.md", "range": {"start": {"line": 41, "column": 248}}}, "severity": "ERROR"}

Check failure on line 41 in docs/concepts/public-utilities.md

View workflow job for this annotation

GitHub Actions / pr-content-check 

[vale] reported by reviewdog 🐶
[ipfs-docs-style.PLNSpelling] Did you really mean 'hostnames'?

Raw Output:
{"message": "[ipfs-docs-style.PLNSpelling] Did you really mean 'hostnames'?", "location": {"path": "docs/concepts/public-utilities.md", "range": {"start": {"line": 41, "column": 571}}}, "severity": "ERROR"}

## Delegated Routing

While IPFS Gateways are immensely helpful in doing all the heavy lifting of finding providers for CIDs and retrieving them, they can be a choke point for retrieval and a point of centralization.
Expand Down
Loading