Are you using a VPN? It might be that changing your exit IP might help. I’ve noticed captchas get harder to pass if your on a VPN that has a lot of traffic trying to pass captchas. Probably DDoS protection.
That’s most likely the problem. In my experience, nearly all tor exit nodes are flagged as such and captchas are nearly impossible to “pass” when using such an exit node. I would try using a free VPN to test. Try protonvpn without an account and see if you can get past the captcha.
Yes, this archive(.)is captcha problem has been there for me since a long time. And the alternative Ghostarchive won’t load in Tor browser.
<span style="color:#323232;">
</span><span style="color:#323232;">Sorry, ReplayWeb.page won't work in this browser as Service Workers are not supported.
</span><span style="color:#323232;">Please try a different browser.
</span><span style="color:#323232;">(Service Workers are disabled in Firefox in Private Mode. If Using Private Mode in Firefox, try regular mode)
</span>
For some of my browsers I do spoof the user agent, for others it is stock. Mull has Privacy Resist Fingerprint enabled for instance, this happens in all the browsers I have loaded. Mull, Smart Cookie Web Preview, Fennec, Iceraven, Cromite, Mulch, Fulguris, Monocles, Privacy, FOSS, DDG.
Just try a default Firefox. Though if you want to use TOR anyways, why not just use TOR browser? It’s the only browser where the starting conditions are reasonably anonymous.
I have the same issue, but without Tor. For me it comes from using Cloudflare/1.1.1.1 as my DNS Resolver. Apparently they’ve been beefing with archive.is over some dns implementation specifics for some time.
Add comment