Topic on Talk:Main Page

I've refreshed, cleared the cache, rebooted...none of the photos are loading (just showing the broken photo icon).

Please check that you can access the CDN server and that nothing is blocking it: cdn2.pbc.wiki

If the CDN is blocked by your browser, firewall, antivirus, ad blocker, or network, the photos may not load properly.

I'll check that but this is the first time it's happened, which makes me wonder if some update to the site (perhaps the CDN server itself) affected things. Thanks for the suggestion.

FYI -- from some testing I did, this is what I'm being told:

That Xfinity Advanced Security warning is a strong sign you should not proceed—especially since the site also fails over HTTPS with ERR_SSL_PROTOCOL_ERROR. Between (1) broken TLS, (2) needing to fall back to plain HTTP, and (3) your ISP security system flagging it as unsafe, this looks like a risky/misconfigured CDN endpoint at best and potentially malicious at worst. The safe move is to stop trying to load it over HTTP, don’t download anything from that site, and if you need the content, ask the site owner to fix their CDN/HTTPS configuration (or use a different trusted mirror).

The Xfinity Advanced Security page and ERR_SSL_PROTOCOL_ERROR together usually mean Xfinity's filter got in the way. On a normal web connection that filter can show its own warning, and on HTTPS the same block often just breaks the connection, which is the error you hit. That does not mean the image or the CDN is unsafe. The summary you were given took those two symptoms and jumped to the worst reading.

Easy ways to confirm it yourself:

Open image link on a phone using cellular data, so it skips your home Xfinity filter.

• Certificate check: https://www.ssllabs.com/ssltest/analyze.html?d=cdn2.pbc.wiki
• Google Safe Browsing: https://transparencyreport.google.com/safe-browsing/search?url=https%3A%2F%2Fcdn2.pbc.wiki%2F
• VirusTotal: https://www.virustotal.com/gui/domain/cdn2.pbc.wiki

You should see a valid certificate and no malware listing. The images are fine to load. If Xfinity still blocks it only on your connection, the block page usually has a link to report a wrong classification.

Oh, to be clear, I don't think you all are trying to pull a fast one w/ malware or anything. :) I will look at the block page and see if I can resolve this.

Weirdly enough, I can see the photo used for the Leo Louis draft page, but nothing else.

Thanks for looking into it. The Leo Louis photo is most likely still in the browser cache.

Please run the commands below on the same connection where the images fail. They use your normal DNS resolver, so leave out 8.8.8.8 and 1.1.1.1.

Windows (Command Prompt or PowerShell):

nslookup cdn2.pbc.wiki

nslookup -type=AAAA cdn2.pbc.wiki

curl.exe -4 -I https://cdn2.pbc.wiki/w/images/8/8b/Damien_Stone.jpg

macOS / Linux:

dig +short A cdn2.pbc.wiki

dig +short AAAA cdn2.pbc.wiki

curl -4 -I https://cdn2.pbc.wiki/w/images/8/8b/Damien_Stone.jpg

On a normal connection the result is:

A record: 78.107.238.103 AAAA: empty. This host has no IPv6 address. On Windows, nslookup often prints Non-existent domain for that AAAA query anyway. That line only means “no IPv6 address”, as long as the first command shows 78.107.238.103. curl: HTTP/1.1 200 and content-type: image/jpeg If the A address is different, or curl reports an SSL error, that output is what Xfinity needs for a wrong-classification report. The block page usually has a link for that.