☰
×
Login Register an account
Top Submissions Explore Upgoat Search Random Subverse Random Post Colorize! Site Rules Donate
6

Fixing infinte captca on archive.today (Firefox browswer)

submitted by chrimony to TellUpgoat2 1.6 yearsNov 13, 2023 07:36:04 ago (+7/-1)     (TellUpgoat2)

For some reason DNS over HTTPS breaks the site. You can add exceptions for archive.today to fix it:

Settings->Privacy & Security->(scroll to DNS over HTTPS)->Manage Exceptions...

Add:
--
archive.is
archive.ph
archive.today


12 comments block

sort by: hot new top old low

[ - ] bobdole9 4 points 1.6 yearsNov 13, 2023 11:13:59 ago (+4/-0)

TellUpgoat2: not owned by Conspirologist

Most succinct sub description...good work.

[ - ] BoozyB 2 points 1.6 yearsNov 13, 2023 08:09:18 ago (+2/-0)

I get captcha loops on archive using Brave.

[ - ] chrimony [op] 1 point 1.6 yearsNov 13, 2023 11:38:17 ago (+1/-0)

Since this is DNS related, I would check who your DNS provider is. Check my comment elsewhere for hints: https://www.upgoat.net/viewpost?postid=6552183422815&commentid=6552345ea1406

If you want to rule out Brave, I would try ungoogled-chromium.

[ - ] BoozyB 2 points 1.6 yearsNov 13, 2023 12:29:17 ago (+2/-0)

Tried some options, here's what I learned. I have 1.1.1.1 running on my phone.
On Brave
I get the captcha loops in wifi and also when I turn off WiFi and use the phone signal.
On Firefox
captcha works fine on phone signal but not on my wifi with 1.1.1.1 running.
So I guess I'll use Firefox if I want to see archive sites.
I have a couple other obscure browsers installed, I might test those later.

[ - ] FuckShitJesus 2 points 1.6 yearsNov 13, 2023 07:54:19 ago (+2/-0)

"For some reason"

You mean.. for security reasons..?

[ - ] chrimony [op] 3 points 1.6 yearsNov 13, 2023 09:36:14 ago (+3/-0)

Well it wasn't obvious what security reasons there would be for DNS over HTTPS to cause archive.today to shit itself, but I did some digging and found this:

"Archive.is’s owner is intentionally blocking 1.1.1.1 users."

https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

It appears archive.today doesn't like Cloudflare DNS because Cloudflare doesn't allow archive.today to geolocate users. So maybe solving a captcha is a compromise, but then it's just an infinite loop of captcha. That's shit.

[ - ] bobdole9 2 points 1.6 yearsNov 13, 2023 11:16:23 ago (+2/-0)

It appears archive.today doesn't like Cloudflare DNS because Cloudflare doesn't allow archive.today to geolocate users.

Have they stated why they would need to geolocate someone whose requesting to archive something from the web? Some sort of enforcement on behalf of governments?

[ - ] chrimony [op] 1 point 1.6 yearsNov 13, 2023 11:21:29 ago (+1/-0)

I don't anything beyond the article I linked. If I had to guess, it's to deal with bots or other pests. But then again, I don't see why they need DNS to do what.

[ - ] DieselForever 1 point 1.6 yearsNov 13, 2023 18:07:06 ago (+1/-0)

Makes me glad I never bothered with fixing this and just stopped clicking on archive.is links

[ - ] chrimony [op] 1 point 1.6 yearsNov 13, 2023 22:53:38 ago (+1/-0)

I don't disagree. Did the same for months. I'll keep the fix for when I'm curious enough to click, but I won't upvote or use the site to archive.

[ - ] Conspirologist -2 points 1.6 yearsNov 13, 2023 12:08:24 ago (+1/-3)

Why so butthurt, little kike piece of shit?