Bugs in new version 2.10.5.0

  • Автор темы Автор темы Deemer84
  • Дата начала Дата начала

Deemer84

Administrator
Регистрация
10.05.2017
Сообщения
410
Реакции
84
Баллы
28
Bugs, errors and problems in new version 2.10.5.0.
 
Not sure in what thread this should be posted but automatic updates did not worked to update on 2.10.4.0 version and it does not now to update on 2.10.5.0 as well.

When I open log file shows me this:

Код:
Развернуть Свернуть Копировать
18-03-28 15:15:55.252 | Message | Check for updates
18-03-28 15:15:56.360 | Message | Update is not required
18-03-28 16:15:59.321 | Message | Check for updates
18-03-28 16:16:00.804 | Message | Update is not required
18-03-28 17:16:02.934 | Message | Check for updates
18-03-28 17:16:04.006 | Message | Update is not required
18-03-28 17:39:11.917 | Message | Check for updates
18-03-28 17:39:12.964 | Message | Update is not required
18-03-28 17:39:21.274 | Message | Check for updates
18-03-28 17:39:22.114 | Message | Update is not required
18-03-28 17:39:39.701 | Message | Check for updates
18-03-28 17:39:40.506 | Message | Update is not required
18-03-28 17:41:44.151 | Message | Check for updates
18-03-28 17:41:44.968 | Message | Update is not required
 
Not sure in what thread this should be posted but automatic updates did not worked to update on 2.10.4.0 version and it does not now to update on 2.10.5.0 as well.

When I open log file shows me this:

Код:
Развернуть Свернуть Копировать
18-03-28 15:15:55.252 | Message | Check for updates
18-03-28 15:15:56.360 | Message | Update is not required
18-03-28 16:15:59.321 | Message | Check for updates
18-03-28 16:16:00.804 | Message | Update is not required
18-03-28 17:16:02.934 | Message | Check for updates
18-03-28 17:16:04.006 | Message | Update is not required
18-03-28 17:39:11.917 | Message | Check for updates
18-03-28 17:39:12.964 | Message | Update is not required
18-03-28 17:39:21.274 | Message | Check for updates
18-03-28 17:39:22.114 | Message | Update is not required
18-03-28 17:39:39.701 | Message | Check for updates
18-03-28 17:39:40.506 | Message | Update is not required
18-03-28 17:41:44.151 | Message | Check for updates
18-03-28 17:41:44.968 | Message | Update is not required

This is update for modules. No modules were updated.
 
  • Оценить
Реакции: lokiys
CM was working fine, but yesterday I started getting this:

Whatever I try, I always get "Timeout for loading element has been exceeded", though I'n not using any proxies or VPN's. I tried:

1. Change the url or site key.
2. Change built-in browser (FF or Chrome). Tried to set "visible = true" in RC2Instance.exe.config and RC2InstanceChrome.exe.config, but 70% of the time the browser doesn't show up.
3. Tried clean uninstall and reinstall of CM.
4. For the heck of it, I reinstalled Win10, CM was working fine for an hour or two, but same sh!t happens again.
5. Tried to run DiagnosticTracer-64.exe, but it spits out
Error in DiagnosticTracer init
Error in DiagnosticTracer parse params

Anything else I can try? It seems this issue isn't fixed for quite a long time: http://zennolab.com/discussion/threads/bug-v2-10-3-timeout-loading-element.45748/
 
Последнее редактирование:
You should change proxy and use fresh ones.
 
As I said, I'm 100% sure I'm not using any proxies and recaptcha loads fine in a regular browser. CapMonster's built-in browser doesn't even start-up(I set it to be visible). This is really annoying, when you pay money for nothing!
You always use one IP?:be:
Do you think Google let you solve many captchas from the same IP and does not suspect it's bot?
Don't compare CapMonster with regular browser. You have user history in your browser, Google identifies you as real user in it.
 
Sometimes(but rarely), the built-in browser shows up, as you can see, it is not set to use any proxies, but it is not working, whatever URL's or settings I try.
thumb.php

 
I know this perfectly(using my own python script + anti-captcha.com API to set proxies for CM). Everything was working fine, for weeks. But sometimes Sitekey addon stops working (with or without proxies). I'm 99.5% sure, its a bug.
This means that you should change proxies, that you need fresh IP's.
 

Кто просматривает тему: (Всего: 0, Пользователи: 0, Гости: 0)