SSL cert broken? #92

Closed
opened 2026-10-05 05:13:26 +02:00 by adam · 4 comments
Owner

SSL cert broken?

Screen Shot 2024-04-16 at 19 53 57
SSL cert broken? <img width="1191" alt="Screen Shot 2024-04-16 at 19 53 57" src="https://github.com/ipfs/ipfs-blog/assets/138401/42523811-0e72-462f-a083-08259c383a41"> <!-- github-sync-id:2246783960 -->
adam closed this issue 2026-10-05 05:13:26 +02:00
Author
Owner
Screen Shot 2024-04-16 at 19 54 52
<img width="1191" alt="Screen Shot 2024-04-16 at 19 54 52" src="https://github.com/ipfs/ipfs-blog/assets/138401/e60c5edb-5f4c-44a2-9167-30311cb5b6ad"> <!-- github-comment-id:2059823033 -->
Author
Owner

Oh wow, this seems to be across all of ipfs.io

Screen Shot 2024-04-16 at 19 57 23
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 -->
Author
Owner

@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.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).

@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 -->
Author
Owner

@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)

> @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 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/ipfs-blog#92