reCAPTCHAs Detecting SeleniumBase After Chrome Update 132 #3432
-
|
Hello everyone, I’ve noticed a persistent issue after updating Chrome to version 132 while using SeleniumBase for automation. It seems that reCAPTCHA is consistently detecting SeleniumBase and showing captchas for every Google search. This behavior wasn't as frequent before the update. I’ve already tried: Rotating user-agents using --user-agent but no significant improvement. I would appreciate any advice or insights from the community: Has anyone found a reliable workaround for avoiding detection in recent Chrome updates? Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Duplicate of #2977 (comment). reCAPTCHA is different from other anti-bot services because it may throw CAPTCHAs even if not detecting Selenium. Instead of bypassing reCAPTCHA, solve the audio challenge with an external repo: If you think you've found a bug within SeleniumBase, please open another issue with a self-contained repro. |
Beta Was this translation helpful? Give feedback.
-
|
@ALIMURTAZAAMJ recaptcha on google search pages used to work a little differently, unlike regular recaptcha. Google search pages have limits on the number of requests from a single ip address. Try to find them and use a proxy for bypass limits. It used to work.. |
Beta Was this translation helpful? Give feedback.
Duplicate of #2977 (comment).
reCAPTCHA is different from other anti-bot services because it may throw CAPTCHAs even if not detecting Selenium.
Instead of bypassing reCAPTCHA, solve the audio challenge with an external repo:
https://github.com/search?q=pydub.AudioSegment.from_mp3+recaptcha+solver+language%3APython&type=code
If you think you've found a bug within SeleniumBase, please open another issue with a self-contained repro.