Archive.today is having problems

[The Howlers of Mars]

And to make matters worse, whoever configured Archive's Tor address (http://archiveiya74codqgiixo33q62qlrqtkgmcitqx5u2oeqnmn5bpcbiyd.onion/) pointed it at the cloudflare frontend, which is completely wrong, and causes all the Tor visits to first go through cloudflare, which typically tries to block Tor users.

Tor addresses should ALWAYS point at the actual server IP, bypassing clownflare.

Pointing a Tor address to cloudflare breaks things.

For the record, I can find no reason to believe that Archive actually uses Cloudflare. They may have at one point, but it looks like to me they just ripped CF's older captcha page. Look for the clues:

• Use of reCAPTCHA. Even before the modern day, where CF's WAF options use Cloudflare Turnstile, Cloudflare started using hCaptcha, not reCAPTCHA.
• The "CF" page does not have any Ray IDs, your IP, or "Performance & security by Cloudflare". All the CF default pages have this. In addition, this is not what the CF challenge pages look like anymore.
• The HTTP responses have none of the typical Cloudflare headers.
• IPs in DNS aren't Cloudflare.

That's going to be why the Tor address is still showing this challenge, because it's obviously an integral part of whatever their request flow is (perhaps even baked into the application itself?). It's not an intermediate provider.

(also, as a side note: I obviously dislike Cloudflare because of our history with them. But in fairness, CF is not inherently rude to Tor. Where I have been forced to use the CF portal, their analytics are pretty detailed and you can see that Tor is generally allowed to pass. The issue is often retard site administrators who blindly enable their bot fight modes and the like, set the security level to high, etc. Like it or not, Tor is used for abusive traffic, and it can highly vary on how much abuse your specific exit node has. So enabling these modes without considering the consequences very well may disproportionately affect Tor. That's not really Cloudflare's fault, it's doing what you told it to do.)

 

[Ebonic Tutor]

I've had people tell me to change my DNS to googles and other things that supposedly "fix" the issue but nothing has seemed to work for me... Funny this all started after that hit-piece a month or so back.

It is working on TOR for what it's worth.

EDIT: Using the Verisign DNS I was able to get connected to archive.is, but not any of the others.

• Verisign: 64.6.64.6 and 64.6.65.6.

Edit2:

well that's not quite it either... like I got it to work for a second but I'm still not sure why.

 

[Geranium]

I've had people tell me to change my DNS to googles and other things that supposedly "fix" the issue but nothing has seemed to work for me... Funny this all started after that hit-piece a month or so back.

It is working on TOR for what it's worth.

Yeah, despite my suggestion on the previous page to just use Google's DNS, for the past couple of weeks I've been unable to access archive.today on my desktop, just getting the "Welcome to NGINX" page".

For some reason it works fine on my phone, even though the DNS settings are the same. I even copied the exact request from the phone via the browser dev tools and attempted to replay it with curl on the desktop, but it just times out. Very weird.

But the Tor address works fine; I'll post updated versions of my bookmarklets in the Archive Tools thread that work with the Tor address also, and provide both clearnet and Tor archive links.

 

[A. G. Peak]

Yeah, despite my suggestion on the previous page to just use Google's DNS, for the past couple of weeks I've been unable to access archive.today on my desktop, just getting the "Welcome to NGINX" page".

For some reason it works fine on my phone, even though the DNS settings are the same. I even copied the exact request from the phone via the browser dev tools and attempted to replay it with curl on the desktop, but it just times out. Very weird.

But the Tor address works fine; I'll post updated versions of my bookmarklets in the Archive Tools thread that work with the Tor address also, and provide both clearnet and Tor archive links.

I couldn't use it for like a month, but the past two weeks it's been working perfectly (without any changes on my end). This thing is so hard to diagnose, it's all over the place. And people on the internet have been complaining about it for years.

 

[quaawaa]

Yeah, despite my suggestion on the previous page to just use Google's DNS, for the past couple of weeks I've been unable to access archive.today on my desktop, just getting the "Welcome to NGINX" page".

For some reason it works fine on my phone, even though the DNS settings are the same. I even copied the exact request from the phone via the browser dev tools and attempted to replay it with curl on the desktop, but it just times out. Very weird.

That was happening to me until I cleared archive.ph's cookies.

 

[Geranium]

That was happening to me until I cleared archive.ph's cookies.

I'm a fucking retard. Thanks, this worked. (I'll still do the Tor bookmarklets when I have time.)

 

[Ebonic Tutor]

So I got it loading archive.is today... thing is no archived sites will load for me.

 

[A. G. Peak]

About a week ago, after a period where archive.[ li | md | ph | today ] had been loading fine for me, I found myself stuck in the reCAPTCHA loop again.

I came across a comment on reddit pointing to DNS over HTTPS as a possible cause. After adding exceptions for the archive.* domains to Firefox, the site is loading fine. This may not fix everyone's issues, but it's something to try.

If you use Firefox, go to Settings > Privacy & Security > 'DNS over HTTPS' and click 'Manage Exceptions...' Alternatively, you can use the Settings search field to jump straight to the 'DNS over HTTPS' section.

If you don't use Firefox and are stuck in the reCAPTCHA loop, it's worth looking into how your browser handles DNS over HTTPS and if you are able to add exceptions.

 

[Ebonic Tutor]

I know my problem has to do with my anti-virus (ESET) I uninstalled it and the site loaded fine, reinstalled and now it won't open.