CapMonster 2.11.0.0 (10.09.2020)

Owned by ZL Support
Oct 16, 2021
2 min read

Added:

[+] No more limit of threads - instead there's a limit for the number of recognized CAPTCHAs per day. The limit varies depending on the version of the program and the type of CAPTCHA.
[+] Pingback API was implemented for RuCaptcha and AntiCaptcha, so that CapMonster notifies when the CAPTCHA is ready. It is not necessary to pre-register any domains for the pingback
[+] Control of the number of incoming CAPTCHAs. If instance limitation is X and 2*X reCAPTCHAs are waiting for recognition in a queue (not being recognized yet), then by default when trying to add another reCAPTCHA an ERROR_NO_SLOT_AVAILABLE error will be thrown. This behavior can be modified by setting a constant maximum length of queue in the {capmonster_directory}/Settings/globalsettings.settings.json (in the MaxRcTasksInQueue block) file
[+] Proxy is tested before reCAPTCHA recognition using a lightweight process, which allows to save resources by not launching the browser if the proxy is dead. If the test was successful, the result is stored in memory to avoid excessive tests. Tests can be disabled in settings.
[+] Support for a new type of CAPTCHA by Yandex called yandexwave was added
[+] recaptcha.net domain support was added for reCAPTCHA recognition - for countries, where Google is banned or not available (China, Arab countries, etc.)
[+] If the wrong Sitekey or domain were passed during reCAPTCHA recognition, CapMonster will immediately throw an error (ERROR_RECAPTCHA_INVALID_SITEKEY or ERROR_RECAPTCHA_INVALID_DOMAIN accordingly)
[+] Minor corrections were made to the reCAPTCHA v2 recognition algorithm via Chrome, which improves recognition success rate

 

Fixed:

[*] Fixed the error when CapMonster couldn't properly automatically restart after crashing and was throwing an error
[*] Fixed the large number of timeouts that were present during reCAPTCHA v3 recognition when using slow proxy in Chrome
[*] Fixed the error when an unstable internet connection caused the ReCaptchaSitekeyAddon to get disabled for a short period of time
[*] The getcmstatus command now properly supports key transfer via post-parameters in the json format