ERROR_CAPTCHA_UNSOLVABLE - <Could not recognize>

[r2d2br]

For a few days now, I've been getting some new errors at Capmonster.
When trying to solve some RecaptchaV2, I receive in the program feed the message <Could not recognize>, and in the reply from "res.php", the message "ERROR_CAPTCHA_UNSOLVABLE".
Apparently it is a random error, but the frequency seems to be increasing a lot.
It happens at least in versions 2.10.16.1 and 2.10.16.2.
The website does not have the new "data-s" field.
Capmonster with 140 threads, default configuration, proxies never used before.
Method: Chrome.
Is this already a known issue?

EDIT: I got it with the option "Show browser" activated. See the image attached.

 

[VladZen]

For a few days now, I've been getting some new errors at Capmonster.
When trying to solve some RecaptchaV2, I receive in the program feed the message <Could not recognize>, and in the reply from "res.php", the message "ERROR_CAPTCHA_UNSOLVABLE".
Apparently it is a random error, but the frequency seems to be increasing a lot.
It happens at least in versions 2.10.16.1 and 2.10.16.2.
The website does not have the new "data-s" field.
Capmonster with 140 threads, default configuration, proxies never used before.
Method: Chrome.
Is this already a known issue?

EDIT: I got it with the option "Show browser" activated. See the image attached.

Посмотреть вложение 58347

As far as I can see, there is the problem with connection.
Are you sure you have good proxies? what is the type?

 

[r2d2br]

what is the type

IPV6 Http proxies, brand new ones.
I imagine that if the proxy was bad, I would not even receive this message showed in the printscreen.
These proxies still working normally for navigation.

 

[VladZen]

IPV6 Http proxies, brand new ones.
I imagine that if the proxy was bad, I would not even receive this message showed in the printscreen.
These proxies still working normally for navigation.

Then, do you get this error with no proxies?
We recommend residental proxies, btw

 

[r2d2br]

do you get this error with no proxies?

I have trouble reproducing this, because the IP ban comes after few tasks.

 

[r2d2br]

If it is possible to identify this as a "hidden ban", it would be great to treat it as such, so that the proxy's IP is marked in the temporary ban list.

 

[VladZen]

IPV6 Http proxies, brand new ones.
I imagine that if the proxy was bad, I would not even receive this message showed in the printscreen.
These proxies still working normally for navigation.

Does this proxy load google services in usual browser?

 

[r2d2br]

Does this proxy load google services in usual browser?

Yes. I tested with Google search many times with no problem.

 

[VladZen]

Yes. I tested with Google search many times with no problem.

What about google recaptcha? - https://www.google.com/recaptcha/api2/demo

 

[r2d2br]

ReCAPTCHA demo

In this URL, I got the same screen as my screenshot at first post.
Looks like a new way to show that the system has detected suspicious activity.
I was able to use this IP again after a few hours. Perhaps the way is to treat this error as an IP block, so that it can be removed from the list.
However, more research appears to be needed. =D

 

[r2d2br]

UPDATE:
Same Capmonster results (Cold not recognize in GUI, ERROR_CAPTCHA_UNSOLVABLE in http result), but a different message in the Chromium embedded browser, see in attachment.
This occours at the end of process, after show and solve some regular image recaptchas, just when the token should be displayed.
I was unable to reproduce this scenario in my user regular browser.

 

[r2d2br]

It still happening. @VladZen
It seems to be proxy-related, but it seems associated with some detection by google, so I think it is probably enhanced by Capmonster.

More information:
- Cannot reproduce in regular browser using the same proxy.
- It happens only in a specific website (google sitekey)
- It happens only for IPv6 proxies
- From the moment it starts, it happens for several minutes (30-90 at least) in all IPV6 proxies, even virgins. Other sitekeys continue to work with the same IPV6 proxies. IPv4 proxies always work normally.

 

[VladZen]

It still happening. @VladZen
It seems to be proxy-related, but it seems associated with some detection by google, so I think it is probably enhanced by Capmonster.

More information:
- Cannot reproduce in regular browser using the same proxy.
- It happens only in a specific website (google sitekey)
- It happens only for IPv6 proxies
- From the moment it starts, it happens for several minutes (30-90 at least) in all IPV6 proxies, even virgins. Other sitekeys continue to work with the same IPV6 proxies. IPv4 proxies always work normally.

We recommend to use residental proxies not IPv6, to solve recaptcha in CapMonster.
Did you try new version CapMonster 2.11?

 

[r2d2br]

Did you try new version CapMonster 2.11

Yes, I tried. Same results.
By the way, I missing the "new version released" post in english...

 

[VladZen]

Yes, I tried. Same results.
By the way, I missing the "new version released" post in english...

The info about new version 2.11 should be available a little later.