Comment by ttctciyf
2 years ago
Interesting read!
For a while now, I've had infrequently occurring arcane cert/SSL issues connecting to archive.ph and its siblings, but trying a couple of links from the article I find I can't get past an endless cycle of "one more step" captcha protection - tried clearing all cookies and revisiting an old url, but to no avail.
archive.today is the "official" name, which redirects to the domain of choice (right now archive.md, at least for me).
archive.is is blackholed in many places.
Change your DNS - you are using CF
Are you suggesting the cert problem is DNS related or the new captcha issue?
DNS was ISP, not 1.1.1.1, and I get the same behaviour after switching to 8.8.8.8.
Archive.* sabotages their DNS records when Cloudflare queries for them. They don't like that Cloudflare doesn't do EDNS forwarding so they broke their service for people using 1.1.1.1.
That said, I have the same problem. Even hard coding the IP address I resolved through Google doesn't seem to work. I'm guessing their sabotage may have backfired and is causing issues beyond their intentional scope?
2 replies →
>I've had infrequently occurring arcane cert/SSL issues <> Same error page as https://news.ycombinator.com/item?id=37009598
Edit of formatting for readability.
Who is your ISP's DNS provider?
Do they run their own resolver, or rely on an extant service?
3 replies →
I'm using Quad 9 and getting the same results. Who is the right DNS provider?
if you can't trust your isp than either find someone that you can trust (by verification) or run your own resolver.
there was a recent move from the eu to have an eu-centric public resolver which brought up the question if/how the big players address country specific filtering requirements which in turn might have shed some light on the fact that gog/cf didn't care; until now.
1 reply →