5 ms·
Ask HN: Archive.is Captcha Problems Lately?
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 https://archive.is/gwuFp
- alexolog 3y agoCaptcha 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 https://dns10.quad9.net/dns-query Console shows error 429
- alexolog 3y agoAnd sure enough, if I disable secure DNS and change the DNS server to my ISP's, it works. Assholes.
- plssy 3y agonot a technical person, how can I fix this? turned off secure DNS, didn't work, changed IP to Google's, that disabled my WiFi...
- retrocryptid 3y agoYup. Me too. On Firefox.
- Abrownn 3y agoConfirming Firefox issue here too
- 1980phipsi 3y agoI have the issue on Firefox, but not on Chrome.
- riedel 3y agoCurrently no luck on android using both brave and chrome.
- IndoorPatio 3y agoYes, seems broken.
- defrost 3y agoCheck your DNS, there are issues using Cloudflare to reach archive.{is | li | today | etc } Google DNS and others work where Cloudflare does not.
- dredmorbius 3y agoInteresting ... 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.
- jgrahamc 3y agoNothing 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 https://news.ycombinator.com/item?id=19828702
- aendruk 3y agoYep, 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
- WarOnPrivacy 3y agoIn 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.
- 00deadbeef 3y agoBeen 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.