Skip to content
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

How to solve a CAPTCHA Challenge #473

Closed
bhavyaagg opened this issue Aug 22, 2017 · 7 comments
Closed

How to solve a CAPTCHA Challenge #473

bhavyaagg opened this issue Aug 22, 2017 · 7 comments

Comments

@bhavyaagg
Copy link

In case of CAPTHA Challenge, i am getting "Please upgrade to a supported browser to get a reCAPTCHA challenge."

example

How should we solve the CAPTCHA Challenge?

@bhavyaagg bhavyaagg changed the title How to pass through a CAPTCHA Challenge How to solve a CAPTCHA Challenge Aug 22, 2017
@icarusmiles
Copy link

Well you can set a different userAgent, however you may still get prompted to do an actual CAPTCHA, which I have no clue how to automate. The whole purpose of them is to obviously avoid bot access.

@Garbee
Copy link
Contributor

Garbee commented Aug 22, 2017

As @miles-collier pointed out, you don't automate captcha's. They are put into place specifically to prevent automated access to various resources. If that's a problem for you, you need to disable the captcha in a test environment. If you aren't in control of the site in question, then you're out of luck for automating around them. If captcha's could be automatically bypassed, they wouldn't be effective in doing their task.

@sandysandeepkumar
Copy link

sandysandeepkumar commented Dec 17, 2018

<input aria-invalid="false" class="jss153 jss138" id="lCaptcha" name="captcha" placeholder="49 + 24 =" type="text" value=""> ``

how to handle with puppetter headless chrome

@Garbee
Copy link
Contributor

Garbee commented Dec 17, 2018

@sandysandeepkumar Please read the previous comments in this thread. They detail why Puppeteer can't help with captchas and how you need to handle them if applicable. If you aren't in control of the site, then there is nothing that can be done. It's up to you to figure out on your own.

@nicoandmee
Copy link

nicoandmee commented Dec 17, 2018

@sandysandeepkumar Please read the previous comments in this thread. They detail why Puppeteer can't help with captchas and how you need to handle them if applicable. If you aren't in control of the site, then there is nothing that can be done. It's up to you to figure out on your own.

are you sure? because i can solve all amazon captcha using tesseract/ocr with some degree of error. puppeteer provides all the resources you need to automate captcha solving, both using something like tesseract, and a 3rd party provider like an anticaptcha. i dont think captchas are very effective at stopping bots haha. to the person who posted this, feel free to reach out to me outside of puppeteer repository if you need help!

followup- recently to combat the newest recaptcha, i am using the puppeteer api to inject a script on load that will fire the callback to grecaptcha (thus making it useless). there may not be a .solvecaptcha but its pretty easy to write one

@Garbee
Copy link
Contributor

Garbee commented Dec 18, 2018

because i can solve all amazon captcha using tesseract/ocr with some degree of error.

Which seems to fall specifically in...

It's up to you to figure out on your own.

That isn't something puppeteer can or will provide to do for people.

I'm not saying automatically solving them is impossible. I'm simply saying helping bypass them isn't something in the scope of this project.

@berstend
Copy link

Purely from a technical standpoint I might add that the recaptcha error originally reported here is due to to the lack of out-of-process iframes support (#2548).

Puppeteer should definitely not try to aid in captcha solving but thrive to support all kinds of web content on par with regular Chrome. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants