Replies: 7 comments 7 replies
-
|
The problem is Selenium? I'm not 100% sure what changed exactly, but I know our code to find and click the widget, quit working. When I applied the fix I had use Selenium to switch to the iframe, and click the widget there, which works, but it just refreshs to a new checkbox once it fails verification, and it fails even with the GUI versus headless. |
Beta Was this translation helpful? Give feedback.
-
|
The problem is Selenium? I'm not 100% sure what changed exactly, but I know our code to find and click the widget, quit working. When I applied the fix I had use Selenium to switch to the iframe, and click the widget there, which works, but it just refreshs to a new checkbox once it fails verification, and it fails even with the GUI versus headless. |
Beta Was this translation helpful? Give feedback.
-
|
We are doing it tens of thousands of times per hour, we just get the checkbox when using some proxies. We simply time out the attempts, flag the proxy as bad, and switch the proxy out. But if we could beat the check box again we wouldn't have to burn so many proxies. |
Beta Was this translation helpful? Give feedback.
-
|
how to bypass? |
Beta Was this translation helpful? Give feedback.
-
|
this is alredy solved here |
Beta Was this translation helpful? Give feedback.
-
|
there is a new checkbox again |
Beta Was this translation helpful? Give feedback.
-
|
Doesn't work with https://labs.perplexity.ai :( |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We run a production app with Undetected Chromedriver that logs in to the target sites and reads and writes data, and it does this perfectly 20,000 times an hour for us. Usually we run a 99% success rate, using roughly 20000 Residential Proxies. No problems.
But on some proxies we get the Cloudflare "click here if you're human" checkbox. It's now actually a widget in a hidden iframe, but pretty easy to isolate and click. Again, no problem, but...
...2 day ago when they switched from just the widget to the iframe, about 5 to 7% of our runs over certain proxies, trigger the checkbox, but when we click it, it says verifying, and then brings us right back to the click checkbox screen. And it's clearly not detecting mouse movement or any other tricky business because even when we manually click it, we get the same results.
Has anyone else had this issue and figured out a way to drive Selenium around it?
Beta Was this translation helpful? Give feedback.
All reactions