Oh wow, this seems to be across all of ipfs.io
<img width="1191" alt="Screen Shot 2024-04-16 at 19 57 23" src="https://github.com/ipfs/ipfs-blog/assets/138401/7a847f90-bdc8-458a-8c67-3f961992a53a">
<!-- github-comment-id:2059826872 -->
For blog, we now link to https://blog.ipfs.tech (update your bookmarks, the .io version is provided for legacy reasons and redirects to .tech as soon you load it).
@jbenet are you are in a hotel or similar place that uses DNS-based filtering?
Looks like your ISP has set up [OpenDNS filtering](https://support.opendns.com/hc/en-us/articles/227988047-Web-Content-Filtering-and-Security) or [Cisco Umbrella](https://umbrella.cisco.com/products/dns-layer-network-security) and `blog.ipfs.io` is blocked by that, likely because of `ipfs.io`.
Try switching DNS to 1.1.1.1 or 8.8.8.8 and the problem will likely go away.
We will look into reporting false-positive but this type of blocking will keep happening on `ipfs.io` and its subdomains.
This is why we moved most websites to different domains, like `ipfs.tech` (https://github.com/protocol/bifrost-infra/issues/2018)
For blog, we now link to https://blog.ipfs.tech (update your bookmarks, the .io version is provided for legacy reasons and redirects to .tech as soon you load it).
<!-- github-comment-id:2059878817 -->
ipfs.tech is blocked too, FYI. (that's what threw me off)
> @jbenet are you are in a hotel or similar place that uses DNS-based filtering?
ooooh lol, ok, great!
Confirmed with proxies & VPN -- looks like it works fine outside.
false alarm, thank you! 🙇
> https://blog.ipfs.tech/
ipfs.tech is blocked too, FYI. (that's what threw me off)
<!-- github-comment-id:2059902973 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
SSL cert broken?
Oh wow, this seems to be across all of ipfs.io
@jbenet are you are in a hotel or similar place that uses DNS-based filtering?
Looks like your ISP has set up OpenDNS filtering or Cisco Umbrella and
blog.ipfs.iois blocked by that, likely because ofipfs.io.Try switching DNS to 1.1.1.1 or 8.8.8.8 and the problem will likely go away.
We will look into reporting false-positive but this type of blocking will keep happening on
ipfs.ioand its subdomains.This is why we moved most websites to different domains, like
ipfs.tech(https://github.com/protocol/bifrost-infra/issues/2018)For blog, we now link to https://blog.ipfs.tech (update your bookmarks, the .io version is provided for legacy reasons and redirects to .tech as soon you load it).
ooooh lol, ok, great!
Confirmed with proxies & VPN -- looks like it works fine outside.
false alarm, thank you! 🙇
ipfs.tech is blocked too, FYI. (that's what threw me off)