5 points | by ksec 14 hours ago
8 comments
Latest Update. This seems to be an issue specifically on macOS installed with OpenCore patcher. And something to do with Metal detection.
FTR I recently ran into this when trying to log into Cloudflare itself.
I eventually worked out it was the Disable HTML5 Autoplay extension in Ffx.
I'm offering this more as a clue than a solution (bc I see you've plowed thru your ext's).
Some recent related discussions:
https://news.ycombinator.com/item?id=42577076
https://news.ycombinator.com/item?id=42953508
Interestingly on Firefox I tried changing the User Agent from version 138 ( Latest Firefox ) to 135. And it doesn't work.
I think it uses some sort of features detection to identify if you are really using that browser.
I think these challenges depend on IP too, so one possibility is that you share IP range with some especially nasty bot, so try VPN/Tor also.
It works on Firefox and Chrome so I dont think it is IP specific. But just in case I used a VPN and still dont work.
What if you change the user agent in Safari via the Debug menu? Same?
Yes tried that already. Changed it to Firefox ( Because it worked on Firefox ) and still the same.
But this actually reminded me to try it on Orion using the same webkit engine. Turns out the same issue and blocked as well.
Latest Update. This seems to be an issue specifically on macOS installed with OpenCore patcher. And something to do with Metal detection.
FTR I recently ran into this when trying to log into Cloudflare itself.
I eventually worked out it was the Disable HTML5 Autoplay extension in Ffx.
I'm offering this more as a clue than a solution (bc I see you've plowed thru your ext's).
Some recent related discussions:
https://news.ycombinator.com/item?id=42577076
https://news.ycombinator.com/item?id=42953508
Interestingly on Firefox I tried changing the User Agent from version 138 ( Latest Firefox ) to 135. And it doesn't work.
I think it uses some sort of features detection to identify if you are really using that browser.
I think these challenges depend on IP too, so one possibility is that you share IP range with some especially nasty bot, so try VPN/Tor also.
It works on Firefox and Chrome so I dont think it is IP specific. But just in case I used a VPN and still dont work.
What if you change the user agent in Safari via the Debug menu? Same?
Yes tried that already. Changed it to Firefox ( Because it worked on Firefox ) and still the same.
But this actually reminded me to try it on Orion using the same webkit engine. Turns out the same issue and blocked as well.