-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reCaptcha complains about automated queries when running headlessly #44
Comments
There's a patched version of the chromedriver that is designed to be undetectable to things like this. You could try to implement that. |
Me and @bolshoytoaster have been trying to work on this in #25. If anyone else has any ideas, throw em here or at the PR. |
I believe the error may be due to the fact you have sent too many captchas in one day. I encountered it myself working on a non-headless chromedriver. |
If this is the case we could try to make it think we're using a different machine, possibly linking back to #6. |
I haven't tried this in headless mode yet, but I haven't had it block me while using this. I think the captcha blocks you based on browser cookies. Switching VPN servers also fixes it, but obviously that's not a great option. |
@tabrown2000
This increases the amount of times you can do it before getting locked out, it’s useful but unfortunately it’s not a permanent solution. Until we find something better we should use this. |
Yeah I've noticed that too. It lets me run it probably 50+ times before it locks me out, then I have to switch VPN servers. My guess is that the captcha is using multiple factors in conjunction to determine when to lock someone out. |
@tabrown2000 if we use this in conjunction with #6 we should have this problem solved. If we can find some good public proxy servers we can make a array of them to rotate around automatically. That would stop people having to manually switch VPN servers. |
Throwing an issue found during development of #25 here. Recaptcha seems not to like Chrome's headless browser/
The text was updated successfully, but these errors were encountered: