Недавний контент r2d2br

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

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...

I think this is possible by increasing the value in the "Timeout waiting for task" property.

Could you kindly say which hardware configuration used in this scenario, please?

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...

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...

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

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.

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

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.

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...

Can you share more details please? I started with 95%+ success rate too, but it quickly down... Maybe I have few proxies for my current workload. How many proxies do you use? How many jobs per minute are requested? Do you use Chrome solution method? Thanks in advance.

I'm interested. Please PM.

Hmm very weird. I rolled back for version 2.10.14.0, waiting for more reviews. 100% timeout tasks with IPV6 in 2.10.15.0, 95%+ successful tasks with same IPV6 proxies in 2.10.14.0.

Only IPv4 proxies are working for me in this new version. All my IPv6 proxies given the error "Timeout for loading element has been exceeded". Even with default config. The previous version 2.10.14.0 are working. PS: The original website has only a IPv4 version, maybe this is the cause?