Cloudflare checks broken again?

[digitalaudiorock]

Operating system: Linux and Windows:
33.0.1:
64-bit:
Problem URL: https://1337x.to:

Starting just today I see I can't get past the Cloudflare checks trying to access https://1337x.to. It just goes into a loop that keeps re-prompting with a checkbox. I have a subscription to another site that uses that Cloudflare BS and it's doing the same.

Has any else seen this on other sites? I suspect someone will. I'm using Gentoo Linux here, but it's doing the same with Windows as well.

Wow do I wish everyone would stop using that crap.

Tom

[back2themoon]

Confirmed on other sites. Here we go again.

[digitalaudiorock]

Confirmed on other sites. Here we go again.

I figured as much. If I recall correctly(?) the last tine this happened it was broken in Waterfox as well. I just tested that with the latest version and that's NOT the case this time. Waterfox gets past it.

I know I really should just boycott any sites that allow those assholes to be the world's browser police, but this always affects sites for which there just are no replacements. No words for how this pisses me off,

Tom

[Moonchild]

Everyone who runs into the captcha failing please contact cloudflare about this. make sure they get enough requests for fixing this so they take note. include the "ray id" at the bottom when you do.

[back2themoon]

Post your "Ray IDs" here please:

https://community.cloudflare.com/t/brow ... ain/626885

[digitalaudiorock]

Everyone who runs into the captcha failing please contact cloudflare about this. make sure they get enough requests for fixing this so they take note. include the "ray id" at the bottom when you do.

I contacted a site I subscribe to that uses it and they're going to email them at least.

That cloudflare community site is just about as awful as everything else about cloudflare. I'm not sure which category would be the best place to report that. It probably makes sense to report it once and for others to reply to that. For reference, here are the threads that were started the last two times they pulled this shit:

https://community.cloudflare.com/t/brow ... ken/381029

https://community.cloudflare.com/t/brok ... ork/518036

So this is apparently an annual thing...2022, 2023 and now. FFS.

Tom

[back2themoon]

I'm not sure which category would be the best place to report that. It probably makes sense to report it once and for others to reply to that.

See previous message. Contacting separate websites is not the way to go.

[digitalaudiorock]

Post your "Ray IDs" here please:

https://community.cloudflare.com/t/brow ... ain/626885

Your reply came in just before I posted the above. Thanks for starting that!

Pardon my ignorance here, but what exactly is that Ray ID and how do I find it?

Tom

[back2themoon]

When a website refuses you and goes into a loop, that ID is visible at the bottom of the page.

[digitalaudiorock]

When a website refuses you and goes into a loop, that ID is visible at the bottom of the page.

Ahhh...yup. I see that. Thanks!

Tom

[Moonchild]

UPDATE: After jumping through a dozen hoops I now have an open priority ticket with CloudFlare tech support as well (since I have an account with them) to get it resolved. Fingers crossed.

[Kand_in_Sky]

confirmed
endless loop in PM & Basilisk, works in LibreWolf 116 & Thorium 109

[Basilisk-Dev]

Did some tests with different user agents, this doesn't seem to be a case of bad user agent sniffing. Using a Firefox user agent doesn't fix it. Removing the Goanna slice does not fix this either.

[Moonchild]

it's probably doing some JS tomfoolery (since everyone knows how to spoof UAs and bots do it all the time, it's not an effective measure) and since JS is extremely unforgiving about functions not being present or having different parameters (especially in the strict mode that every and their uncle enforces everywhere) it likely aborts *somewhere* and then as a result defaults to "check failed". CF knows what they changed, we don't. They have the information to fix it, we don't.

[KlarkKentThe3rd]

For me, it happens sometimes, but only

on 4chan

. Elsewhere Cloudflare checks normally work.

[Moonchild]

It only affects their captcha, as far as i can tell. not all site checks trigger that

[Enobarbous]

Off-topic:
What a "wonderfully informative" error in the console...

Code: Select all

https://challenges.cloudflare.com/cdn-cgi/challenge-platform/h/g/orchestrate/chl_api/v1
v1:1
Error:          v1:1:485842
/.*.*=.*/      v1:1:485842
/.*.*=.*/      v1:1:485842
function ()   v1:1:485842
function ()   v1:1:485842
<a>             v1:1:485842
<a>             v1:1:485842
: 1

For what?

[digitalaudiorock]

It only affects their captcha, as far as i can tell. not all site checks trigger that

Interestingly, with the sites I have issues with, over the past week they started occasionally (though note always) prompting with that checkbox when they weren't doing so before. At that point however they did work when that was checked. So they've clearly been screwing with stuff. There really is a special place in hell for all this.

Tom

[KlarkKentThe3rd]

Okay, NOW it is happening to me. An endless verification that never verify. On a certain website.

I'm sure they will fix it on their end soon, but it's still annoying.

[cannonmc]

All of the above. Two regular sites that use Cloudflare not available.

It is ironic that we can contact Cloudflare (who don't care, it seems, that they are blocking access to their 'clients) but we can't access the sites that Cloudflare is meant to protect.

Just in from one site owner:
"So the browser is getting stuck and not going past the Cloudflare test?
About the only thing Cloudflare is expecting is that the browser can run javascript.
If you know how to use developer mode and the browser has it, it should show you where the javascript is failing."

I have no problems elsewhere with javascript. I think we should tell site owners what Cloudflare is doing to their customers even if Cloudflare just take the money and run, it seems