Cloudflare checks broken again?

[Moonchild]

About the only thing Cloudflare is expecting is that the browser can run javascript.

A very specific flavor of JavaScript that's clearly not browser-agnostic. This is the problem trying to make clear to webmasters what's happening. They don't understand that Google has made JS a moving target. But CF just tells users "if the browser can run JS, you're good." But that's just not true. Every browser out there can run JS.

[yan242]

I confirm failure with CF on a certain site ! And I need IHG for that site. Thank you for deleting that awful CF failure !

[back2themoon]

Complaining about it here won't help. You should also post your Ray IDs in the relevant Cloudflare Community topic.

[cannonmc]

And just to add insult to injury, when you go to the Cloudflare Community [sic] web site you get this:

"Unfortunately, your browser is unsupported. Please switch to a supported browser to view rich content, log in and reply."

[back2themoon]

Correct, but that's a Discourse issue. There is a working workaround for Pale Moon (to be found here on the forum), but for a quick post there you will need another browser.

[back2themoon]

Ok, here is the quick guide to the Discourse community/forums workaround, which will also fix the Cloudflare Community:

1. Install the Modify HTTP Response extension (go to the Releases section to find the .xpi file)
2. After installing it, go to its Options and paste the code below in Filters:

Code: Select all

[["/discourse|^community\\.|^resource\\.|^forum\\./",["/browser-detect-/",["/.*/g",""]],["/vendor-/",["/(t\\.discourse\\.hoisted|t\\[e\\]|r)(\\?\\?|\\|\\|)=(\\{\\}|\\[\\])/g","$1$2($1=$3)","n??=[]","n||(n=[])"]],["/discourse-/",["e.draft||=t.draft","e.draft||(e.draft=t.draft)","/(t\\.__registry__\\._typeInjections\\.service|[ne]|[fm]\\[e\\])(\\?\\?|\\|\\|)=(\\[\\]|\\{\\})/g","$1$2($1=$3)","(s||=","!s&&(s=","this._details??=this.store.createRecord(\"topicDetails\",{id:this.id,topic:this})}","this._details=this._details??this.store.createRecord(\"topicDetails\",{id:this.id,topic:this})}"]]]]

3. Tick Enable (right above Filters)
4. Restart Pale Moon or refresh Community page

Note that the code above sometimes requires changes, so it may not work at a later date. Updates are usually posted at the relevant topic linked in the previous message). Also note that some Discourse features may still not work e.g. dealing with attached files.

[number101]

I'd been having trouble with a couple of sites (some pages on boingboing.net, login for nytimes.com and washingtonpost.com). Today a few hours ago, everything went down. Midori (FF derivative) worked. Turned out it's something with Private Internet Access (my VPN), Midori bypasses that. Told it not to VPN Palemoon, and everything started working. Maybe some interaction beween CF and PIA? Dunno, but I'm ok for the time being.

[back2themoon]

Issue still occurs here, just tested three websites. No fix yet from Cloudflare.

[Goodydino]

Complaining about it here won't help. You should also post your Ray IDs in the relevant Cloudflare Community topic.

That is impossible to do if the page will not launch.

[back2themoon]

No it isn't, since many posted those IDs already. The ID is visible before logging in.

If by "the page will not launch" you mean the Cloudflare Community, solutions for that have already been provided just a few posts above.

[dim22]

There may be a problem with the Ecmascript version.
If you run this code in the browser console, you can see that it does not support "array.with"
And it will point to version 13.At the same time, there is no such problem in other browsers (Chrome, Firefox).
Perhaps developers need to update Ecmascript

Code: Select all

function getES() {
  var array = [];
  if (!Array.isArray) {return 3} 
  else if (!window.Promise) {return 5} 
  else if (!array.includes) {return 6} 
  else if (!"".padStart) {return 7} 
  else if (!Promise.prototype.finally) {return 8} 
  else if (!window.BigInt) {return 9} 
  else if (!Promise.allSettled) {return 10}
  else if (!"".replaceAll) {return 11} 
  else if (!array.at) {return 12} 
  else if (!array.with) {return 13} 
  else {return 14}
}

var ecmascript = getES()
var year = 1999
if (ecmascript !== 3) {
  year = ecmascript + 2009
}
console.log("Version " + ecmascript + ", Year " + year)

[Moonchild]

I haven't heard of array.prototype.with before now, and it also isn't part of the ECMAScript compat table (which I would expect it to be on if it was a finalized ecmascript feature)
What language standard is this from? We don't support unstable draft proposals in most cases and if CF is demanding support for that they are doing something very wrong.

[digitalaudiorock]

So still broken and so far not so much as an acknowledgement from CF, at least not on that community forum thread.

Moonchild: Have they responded at all to that ticket you entered? Thanks!

[LuftWafflePilot]

It's FUBAR.

[Moonchild]

Have they responded at all to that ticket you entered? Thanks!

Not since I uploaded the HAR file they requested.
They indicated "A Technical Support Engineer will analyze the available information and get back to you."; that was 2 days ago.

They did respond I was just not notified (silently marked solved...? feels like an attempt at ghosting). The response was a form response. I'm angry about that.

Thanks for contacting Cloudflare.

There are several common reasons a Cloudflare-protected website may block or challenge a site visitor:

The visitor’s IP address demonstrated previous suspicious activity online. Review your client IP address for malicious activity at Project Honeypot. If no suspicious activity is observed from the visitor’s IP address after a two-week period, Cloudflare stops challenging the IP address.

The website owner has created a Custom Rule or a Firewall Rule to block specific request.

The visitor’s actions activated a Web Application Firewall Rule enabled by the website owner.

You can find more information here on Understanding Cloudflare Captchas and Challenge Passage.

If you are being blocked or challenged, please get in touch with the website owner to inquire further on which specific reason that occurs.

I will mark this as solved then, but do let us know if you have any further questions or issues by replying to this e-mail or ticket.

Login to join the Cloudflare Community for advice & insight.

(of course I made sure to reply now I saw it... very nonplussed because CF is used in MANY places and their gatekeeping is basically making using the browser impossible for affected sites. It affects me personally for several things too...)

[billmcct]

Ok, here is the quick guide to the Discourse community/forums workaround, which will also fix the Cloudflare Community:

1. Install the Modify HTTP Response extension (go to the Releases section to find the .xpi file)
2. After installing it, go to its Options and paste the code below in Filters:

Code: Select all

[["/discourse|^community\\.|^resource\\.|^forum\\./",["/browser-detect-/",["/.*/g",""]],["/vendor-/",["/(t\\.discourse\\.hoisted|t\\[e\\]|r)(\\?\\?|\\|\\|)=(\\{\\}|\\[\\])/g","$1$2($1=$3)","n??=[]","n||(n=[])"]],["/discourse-/",["e.draft||=t.draft","e.draft||(e.draft=t.draft)","/(t\\.__registry__\\._typeInjections\\.service|[ne]|[fm]\\[e\\])(\\?\\?|\\|\\|)=(\\[\\]|\\{\\})/g","$1$2($1=$3)","(s||=","!s&&(s=","this._details??=this.store.createRecord(\"topicDetails\",{id:this.id,topic:this})}","this._details=this._details??this.store.createRecord(\"topicDetails\",{id:this.id,topic:this})}"]]]]

3. Tick Enable (right above Filters)
4. Restart Pale Moon or refresh Community page

Note that the code above sometimes requires changes, so it may not work at a later date. Updates are usually posted at the relevant topic linked in the previous message). Also note that some Discourse features may still not work e.g. dealing with attached files.

This worked well for me to bypass the browser check. Thanks

[digitalaudiorock]

(of course I made sure to reply now I saw it... very nonplussed because CF is used in MANY places and their gatekeeping is basically making using the browser impossible for affected sites. It affects me personally for several things too...)

There just are no words for this nonsense. Web sites should work, or at least be accessible using browsers that NOBODY HAS EVEN CODED YET...as long as they're written to the proper specs. THAT is how shit is supposed to work. Add this to the growing list of shit that's going on in technology these days that about makes me cry. This is why we can't have nice things.

I just do NOT buy that sites using CF really need whatever CF is doing, or that it couldn't be done in a way that doesn't need to be specifically tweaked for specific browsers. That simply breaks the way the web is supposed to work. Fuck CF.

Tom

[Moonchild]

Well it gets better.

The ticket opened was closed a second time now (by the same person) claiming what I reported was something they don't provide support with, as if I was asking them to fix our browser code. Clearly having some issues with comprehensive reading. Re-opened again with a re-iteration of the issue and then saw that not only was it closed, the rep also had bumped down the ticket priority to the level of regular support requests for someone needing help with a cloudflare website...
I mean, come on. If they think this is not something their department can deal with, then escalate the ticket to the correct department. Not even like I made/opened that ticket myself; it was created by a CF rep for me (and that person clearly understood the problem) in what I assumed the correct department with an appropriate priority (urgent). It's pretty bad when 1st line support has a much better grasp of technical details than 2nd line does...

So now we wait, again.

[DelPiera]

Is this a joke from CF?

I have tried it from multiple systems (Win7, Win10) and multiple browsers (PaleMoon, FireFox, Tor, Edge) and only Egde and Tor display CF pages! (Chrome is not installed on any system, so I can't comment on that)

It is simply horrible what this company is doing!

[RealityRipple]

Welcome to the internet as handled by people who don't understand the purpose of the internet.