I’ve seen some people have some issues with them with some dns providers in the past (mainly cloudflare dns/ 1.1.1.1), as well as with third party cookies disabled. I haven’t gotten captcha looped myself yet, but if you use some privacy things they commonly have issues with them.
That said, I have a lot of tracker blocking and use a vpn 24/7 and haven’t gotten captcha looped, but if you use anything try to disable them temporarily to see if they might be the cause
CloudFlare DNS was the issue. I had been using PiHole as well, but even turning it off wasn’t fixing it. But when you mentioned 1.1.1.1 causing issues, I turned off WiFi and used the mobile phones data connection and it didn’t even prompt once to prove I’m not a robot. Weird that it works like that. Thanks for the help though.
Edit: oo, for anyone interested, archive is the problem, not CloudFlare. Archive’s authoritative dns purposely responds with invalid IP’s to CloudFlare requests because CloudFlare doesnt leak user data along with the request. Archive refuses to resolve those requests. The owner’s claim that it causes difficulty for per-country requirements doesn’t pass the smell test because there are better ways to determine geographic location than DNS request. Makes me kinda not trust archive.today (and it’s other TLDs). I think I’m gonna stick with web.archive.org only and just not view archive.today. sounds like they’re collecting user data.
After some research I found this thread https://news.ycombinator.com/item?id=19828702 which appears to have a higher up in cloudflare responding. Archive.ph cannot be trusted if half of what was said here is true. I commend Cloudflare for not bowing down to stripping away consumer privacy OR manually intervening to correct archive.ph’s bad practice.
I’ve seen some people have some issues with them with some dns providers in the past (mainly cloudflare dns/ 1.1.1.1), as well as with third party cookies disabled. I haven’t gotten captcha looped myself yet, but if you use some privacy things they commonly have issues with them.
That said, I have a lot of tracker blocking and use a vpn 24/7 and haven’t gotten captcha looped, but if you use anything try to disable them temporarily to see if they might be the cause
CloudFlare DNS was the issue. I had been using PiHole as well, but even turning it off wasn’t fixing it. But when you mentioned 1.1.1.1 causing issues, I turned off WiFi and used the mobile phones data connection and it didn’t even prompt once to prove I’m not a robot. Weird that it works like that. Thanks for the help though.
Edit: oo, for anyone interested, archive is the problem, not CloudFlare. Archive’s authoritative dns purposely responds with invalid IP’s to CloudFlare requests because CloudFlare doesnt leak user data along with the request. Archive refuses to resolve those requests. The owner’s claim that it causes difficulty for per-country requirements doesn’t pass the smell test because there are better ways to determine geographic location than DNS request. Makes me kinda not trust archive.today (and it’s other TLDs). I think I’m gonna stick with web.archive.org only and just not view archive.today. sounds like they’re collecting user data.
I was wondering this myself.
After some research I found this thread https://news.ycombinator.com/item?id=19828702 which appears to have a higher up in cloudflare responding. Archive.ph cannot be trusted if half of what was said here is true. I commend Cloudflare for not bowing down to stripping away consumer privacy OR manually intervening to correct archive.ph’s bad practice.
Sad that it’s been this way for 4+ years.
Thank you, that was quite informative. I’m using pihole with 1.1.1.1 as my upstream provider, too.
Yeah I have to change my DNS to Google 8.8.8.8 for it to work. https://community.cloudflare.com/t/archive-is-error-1001/18227/3
https://news.ycombinator.com/item?id=19828317