Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Ask HN: Archive.is Captcha Problems Lately?
13 points by matttah on Aug 10, 2023 | hide | past | favorite | 20 comments
Anyone else having problems lately with archive.is taking you to a captcha, you solve it and then it just keeps redirecting you back to the captcha over and over. Happens to me in chromium, a friend just tried in firefox and had same problem.

Today is happening to me on a link from another thread which was to https://archive.is/gwuFp



Been having this issue for months. In addition, Safari can't connect to the server at all using iCloud Private Relay.

Seems like an OTT security config.


In case anyone comes back to this. I noticed I get redirected to the archive.is domain and that's when I wind up in a captcha loop.

When I get captcha'd, the archive.is resolves to 198.23.187.186

I cleared my DNS server cache and got new IPs for archive.today and archive.ph but the same address for archive.is. I tried the OPs link, got redirected to .is and got captchas.

I cleared DNS server cache again and got 89.253.237.217 for .is (along with more new IPs for .ph and .today). No captchas.


Captcha loop here as well. Both from FF and an ungoogled Chromium with no add ons that I keep just for these situations.

DNS is the unsecured quad9 9.9.9.10

Secure DNS is likewise https://dns10.quad9.net/dns-query

Console shows error 429


And sure enough, if I disable secure DNS and change the DNS server to my ISP's, it works.

Assholes.


Yep, reCAPTCHA is satisfied but then archive.{is,ph,today} still just loops 429 Too Many Requests. Not sure how they arrived at that conclusion; reading HN I probably hit the service about once per day.

Firefox ETP strict, CenturyLink residential


Check your DNS, there are issues using Cloudflare to reach archive.{is | li | today | etc }

Google DNS and others work where Cloudflare does not.


Interesting ...

Using Cloudflare (1.1.1.1) vs. Google (8.8.8.8) I get different IP resolution:

  for u in archive.ph archive.is archive.li archive.vn archive.fo archive.md;
  do
      echo ">>> ${u} <<<";
      host -t A $u 1.1.1.1;
      host -t A $u 8.8.8.8;
  done
Results:

  >>> archive.ph <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.ph has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.ph has address 23.137.248.133
  >>> archive.is <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.is has address 198.23.187.186
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.is has address 23.137.248.133
  >>> archive.li <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.li has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.li has address 23.137.248.133
  >>> archive.vn <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.vn has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.vn has address 23.137.248.133
  >>> archive.fo <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.fo has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.fo has address 23.137.248.133
  >>> archive.md <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.md has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.md has address 23.137.248.133
Cloudflare: Fix your shit.


Nothing to fix. We are responding with what archive.* sends to us. They choose to send us incorrect data.

See: https://news.ycombinator.com/item?id=19828702


And while we're at it: <https://news.ycombinator.com/item?id=37149094>


You can always email me (jgc@) with details.


Email sent, to jgc.org and cloudflare.com, hopefully one of those works.


Why and/or how is Archive Today managing to send Cloudflare different responses than other DNS providers?

I'd suggest you kick your "integrity of DNS" principle in the interest of "rough consensus, working code". And yes, you can do that without passing on user-specific EDNS to AT, who're quite likely to obtain just that information through the subsequent HTTP GET request in any event.


not a technical person, how can I fix this? turned off secure DNS, didn't work, changed IP to Google's, that disabled my WiFi...


i don't use cloudfare..i think..don't know what that is..just my wifi


strangely sometimes it randomly works once.


Currently no luck on android using both brave and chrome.


Yup. Me too. On Firefox.


Confirming Firefox issue here too


I have the issue on Firefox, but not on Chrome.


Yes, seems broken.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: