Comment by berkle4455
3 years ago
Cloudfare gets paid when they can deliver session traffic to their clients that A) uniquely identifies users and B) has all the traffic decrypted.
If you can’t meet A&B they don’t want you traversing their network.
3 years ago
Cloudfare gets paid when they can deliver session traffic to their clients that A) uniquely identifies users and B) has all the traffic decrypted.
If you can’t meet A&B they don’t want you traversing their network.
I'm not actively trying to avoid detection (e.g. VPN, Tor, etc.). Another user mentioned Firefox's privacy.resistFingerprinting might be the issue, but I don't have that enabled. Maybe there's something else in Firefox that is avoiding (A), and I'm willing to open a Firefox bug report to investigate that, but the core issue here is CloudFlare blocks without any diagnostic information and its community support forum didn't engage. This HN post has caused some amount of engagement from CloudFlare and hopefully it'll be fixed.