here is one. I'm not on my PC so i used a privacy enchanted fork of Mobile Chrome. Enabled WebGL, WebRTC and WASM. Disabled all the fingerprint resistant features i could easily (the only thing messing with your systems could be the HTTP Referrer or Timezone)
Perhaps its a DNS-level issue? Does cloudflare use any google related APIs to provide the integrity check?
I run dnscrypt-proxy and I have seen CloudFlare protected sites reject me based on that. I haven't been able to pinpoint which upstream resolver provider causes it as I have it set to automatically cycle through and it's intermittent enough that I haven't bothered getting to the bottom of it (ie. doesn't happen for several weeks and then happens for 15 minutes or so before resolving).
Perhaps it's one of the default DOH providers being used by Firefox?
https://wiki.mozilla.org/Security/DOH-resolver-policy#Confor...
Presumably not CloudFlare themselves, though.
I'm not a Chrome user, but does Chrome automatically use Google DNS these days?