200 accounts working problem

[Fahad]

Hi,

I had to start a new thread because the problem I got is I think one of a kind.

So.. I have 218 accounts working in one version on VPS.. and I have 100 proxy.. every two accounts share one proxy.. and there is 18 accounts without proxy.

I checked process one action per account and process one action per IP.

I have right now 3 different actions for every account:
1- Follow
2- Like
3- Retweet

The setup is like this:
1- Every 10 accounts share one action.. so there is 3 actions running 30 accounts.
2- Every action has it's own global log.. so there is no interfere between them.
3- Every proxy has two shift.. one account use it in the morning and one in the evening.. so no interfere here either.
4- The only problem I think I cause is this "maybe action follow would run for account (1) and in the same time action retweet run for account (1).

The problem I got:
1- When I choose a working hours for the process it self with another working hours for the account I got "Consumer processing thread" and all action stop. (I can replicate this if you could worked out.. I just think it isn't possible so I didn't report it)
2- Every time I start the actions I got some account in the account page count as "Failed last login" but when I verify them ((with cookies)) it worked and there is nothing wrong!. ((I run it for 109 accounts and 50 accounts got this error))

So.. Here what I would like to get if it's ok:
1- How to make the share account action work randomly.. not from the first account until the last.
2- If the above not possible.. How can I make a share account action with different order so I can order them by proxy or by name..etc.

As always.. thank you.

Logs_id: logs_71999 - version: 3.0.2.964

[Fahad]

I just found out that the same problem are there in my PC at home.

I only use 1 thread in my PC because there is no proxy.. not like VPS I use 33 threads.

I got 3 accounts counts as failed last login.

Here is the logs_id: logs_51046

[martin@rootjazz]

The problem I got:
1- When I choose a working hours for the process it self with another working hours for the account I got "Consumer processing thread" and all action stop. (I can replicate this if you could worked out.. I just think it isn't possible so I didn't report it)

If you can replicate, can you provide me with instructions so I can replicate here please. That is the quickest and easiest way for me to find / fix any issue

Code: Select all

2- Every time I start the actions I got some account in the account page count as "Failed last login" but when I verify them ((with cookies)) it worked and there is nothing wrong!. ((I run it for 109 accounts and 50 accounts got this error))

You mean the accounts list shows ALL accounts as fine. Then you start the actions and then FAILED LAST LOGIN appears as [x]? Yet no action in the logs reported failed login?

So.. Here what I would like to get if it's ok:
1- How to make the share account action work randomly.. not from the first account until the last.

you mean SHARED ACTION setting on the follow tab (for example)? It should be random by default. Can you confirm the action running and I will check this

Logs_id: logs_71999 - version: 3.0.2.964

checking...

[Fahad]

Hi,

Sorry I write this from my phone so can't get any logs.. etc.

First: To replace it just set a working hours for the account and the same working hours (I think I did make it tge same to test it) for the action.. When you run it it will give you the same thing (I think).

Second: Yes before I run the action the account have been verified and every thing is good.. but after tge action run I have failed last logi for aome account.

BTY: after the last update there have been much improve.. but I test it one times and make tweet actions for many accounts.. some work great.. but some get wired problems.. but when i redo it it worked.

I will try to replicate it again and send the log ASAP.

[martin@rootjazz]

Second: Yes before I run the action the account have been verified and every thing is good.. but after tge action run I have failed last logi for aome account.

Cannot replicate, I would need to see logs of this action to investigate. If could generate specific logs that would be very useful:



Please perform the following:

Open the program. Delete or pause all existing actions. If actions are already running due to autorun on startup, disable autorun at startup and restart the app. All actions must be waiting, then pause all (or delete)


Delete existing logs
HELP > LOGS > VIEW
delete all files in the folder that opens


Perform the action:
***
run your action that shows this issue
***

PLEASE NOTE: Do not perform other actions at the same time. Only use one thread. Do not run any actions after this action.


Then submit logs:
HELP > LOGS > SUBMIT

and let me know the LOGS ID (just the number part is sufficient)




Regards,
Martin

[martin@rootjazz]

The problem I got:
1- When I choose a working hours for the process it self with another working hours for the account I got "Consumer processing thread" and all action stop. (I can replicate this if you could worked out.. I just think it isn't possible so I didn't report it)

Maybe I don't understand, but I can NOT replicate this.

Please detail step by step what you do to cause the issue so I can replicate here

I gave account working hour pattern
I gave action different pattern.
Action didnot run when it should not. Then did when it should.

So please include exact values to set and how please

[Fahad]

The problem I got:
1- When I choose a working hours for the process it self with another working hours for the account I got "Consumer processing thread" and all action stop. (I can replicate this if you could worked out.. I just think it isn't possible so I didn't report it)

Maybe I don't understand, but I can NOT replicate this.

Please detail step by step what you do to cause the issue so I can replicate here

I gave account working hour pattern
I gave action different pattern.
Action didnot run when it should not. Then did when it should.

So please include exact values to set and how please

I just replicate the same error.. now with clear logs also.

The things I do:

1- I set an actions for accounts and work them.. after that ((I got problem with counting account as failed login when it's not)) I pause all actions for test to see whats wrong.

2- After pausing them I remove all working hours from accounts and then redo it

3- After that I make working hours for the actions

4- When I restart the actions from (Pause) it all hang and give the same error

5- Force close TD and start it again and run the action cause the same problem!

6- I export the actions.. if you want I will send you some to test it. (many accounts is with proxy so no worries here)

Here is the log_id: logs_55884


Also

The old problem came again.. and 93 accounts was consider failed last login without having any problem and when verify them they work great!

I will try to see what is the real problem (I think it has to be when one account work in two or more action the same time!) and generate a clear log for it.


Update 1

I got the problem..

The problem is:

1- I have a set of 10 accounts working together.. all have different proxy.

2- I have 4 actions for thees 10 accounts (Follow, Like, Retweet and tweet)

3- They all work together at the same time

4- I check on setting to process one action per account and to process one action per ip

5- Here is the trick!

A- The actions of (Like and retweet) have two chain of searching.

B- The first chain result is provided by the account it self (the account that run the action)

C- The second chain result is provided by randomly chosen account ((((and that sometimes being account that will run at the same time while this action is processing))))

So.. The account is loges in and used while TD think it's free to run an action for.. this will cause Twitter to shut it down and lead TD to think the account as failed on verify to login which stop everything!!!

Log_id: logs_98744

I hope this explain everything and there would be a nice way to solve it..

BTW:

1- I use share across accounts for all 4 actions (follow, like, retweet and tweet)

2- I have 88 actions in total 44 of them would work in day and 44 on night shift.. but when the 44 work every account got unique proxy and unique global log.. so there is no way to cause any bug by the way I set them to work.. only possible way is this one.


Update 2

Apparently.. there is a problem with TD..

If I got account need a recaptcha or changing password.. and I verify login without cookies it will count as successful.

Here is the log:

Code: Select all

06:08:55: Starting: 08/08/2019 06:08 AM
06:08:57: Validate account  via login @@ @@ @@
06:08:57: Login: @@ : @@ Proxy: @@ 
06:08:57: UA: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
06:08:57: Login: get: https://twitter.com/
06:08:57: GET: https://twitter.com/
06:08:58: GET: 200
https://twitter.com/
06:08:58: Login: Get: https://twitter.com/login?redirect_after_login=https%3A/twitter.com/
06:08:58: GET: https://twitter.com/login?redirect_after_login=https%3A/twitter.com/
06:08:59: GET: 200
https://twitter.com/login?redirect_after_login=https%3A/twitter.com/
06:08:59: Login: Post: https://twitter.com/sessions 
06:08:59: POST: https://twitter.com/sessions
06:09:00: POST: 200
https://twitter.com/
06:09:00: Login: Success validate:
06:09:00: * WARNING: 'We have detected unusual activity on your account. For your security, your account has been locked until you change your password.'
You *may* additionally be required to receive a SMS on the assigned phone number for the account: 
06:09:00: Scraping Daily stats for: @@
06:09:00: Current time: 06:09:00
06:09:00: Now: 2019-08-08 0609 Start: 2019-08-08 2100 End: 2019-08-09 0700
06:09:00:  Account Can run: 06:09:00  start: 21:00:00 / stop: 07:00:00
06:09:00: UserDetails: https://mobile.twitter.com/@@ with: @@  Proxy: @@ 
06:09:00: Scrape from users: 1
06:09:00: Scrape details from: 1 inputs
06:09:00: Set headers
06:09:00: Set CsrfToken
06:09:00: Set AuthorisationBearer
06:09:00: Getting user details for :1 ids
06:09:00: GET: https://api.twitter.com/1.1/users/lookup.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&include_mute_edge=1&include_can_dm=1&skip_status=1&screen_name=@@
06:09:01: GET: 403
https://api.twitter.com/1.1/users/lookup.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&include_mute_edge=1&include_can_dm=1&skip_status=1&screen_name=@@
06:09:01: FAILED GET: (307306) 403
https://api.twitter.com/1.1/users/lookup.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&include_mute_edge=1&include_can_dm=1&skip_status=1&screen_name=@@
06:09:01: * WARNING: Request failed with Twitter response: To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.
06:09:01: error: deserialising: ofPnFtGdR type: List`1
06:09:01: {"errors":[{"code":326,"message":"To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.","sub_error_code":0,"bounce_location":"https://twitter.com/account/access"}]}
06:09:01: ERROR: scrape users from ID :Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.Collections.Generic.List`1[LibTwitterJsonData.JsonUser]' because the type requires a JSON array (e.g. [1,2,3]) to deserialize correctly.
To fix this error either change the JSON to a JSON array (e.g. [1,2,3]) or change the deserialized type so that it is a normal .NET type (e.g. not a primitive type like integer, not a collection type like an array or List<T>) that can be deserialized from a JSON object. JsonObjectAttribute can also be added to the type to force it to deserialize from a JSON object.
Path 'errors', line 1, position 10.
06:09:01: No users found for: https://mobile.twitter.com/@@
06:09:01: * FAILED: UserDetails: https://mobile.twitter.com/@@ with: @@
06:09:01: 0
<null>
<null>
06:09:01: * ERROR: scraping stats: Object reference not set to an instance of an object.
06:09:01: * SUCCESS: @@ @@ validated successfully
06:09:01: FAILED VERIFY: 

06:09:01: SUCCESS VERIFY: 
https://mobile.twitter.com/@@
06:09:01: 1 accounts validated out of 1
06:09:01: Started: 08/08/2019 06:08 AM
Finished: 08/08/2019 06:09 AM
ID: c39f7162-9877-4524-a928-a074fc82b79d
06:09:01: Action ran for: 0hr:0min:5s
06:09:01: finished processThread: acverify c39f7162-9877-4524-a928-a074fc82b79d

And here is the log of trying to update account location (it say Completed)

Code: Select all

06:25:05: Current time: 06:25:00
06:25:05: Now: 2019-08-08 0625 Start: 2019-08-08 2100 End: 2019-08-09 0700
06:25:05:  Account Can run: 06:25:00  start: 21:00:00 / stop: 07:00:00
06:25:05: Starting: 08/08/2019 06:25 AM
06:25:06: Checking account: @@
06:25:06: Current time: 06:25:00
06:25:06: Now: 2019-08-08 0625 Start: 2019-08-08 2100 End: 2019-08-09 0700
06:25:06:  Account Can run: 06:25:00  start: 21:00:00 / stop: 07:00:00
06:25:06: Update Details:  with: @@  Proxy: @@
06:25:06: Update Details preperform: 
06:25:06: PreTokens: تبوك
06:25:06: Current time: 06:25:00
06:25:06: Now: 2019-08-08 0625 Start: 2019-08-08 2100 End: 2019-08-09 0700
06:25:06:  Account Can run: 06:25:00  start: 21:00:00 / stop: 07:00:00
06:25:06: UserDetails: https://mobile.twitter.com/@@ with: @@  Proxy: @@
06:25:06: Scrape from users: 1
06:25:06: Scrape details from: 1 inputs
06:25:06: Set headers
06:25:06: Set CsrfToken
06:25:06: Set AuthorisationBearer
06:25:06: Getting user details for :1 ids
06:25:06: GET: https://api.twitter.com/1.1/users/lookup.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&include_mute_edge=1&include_can_dm=1&skip_status=1&screen_name=@@
06:25:07: GET: 403
https://api.twitter.com/1.1/users/lookup.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&include_mute_edge=1&include_can_dm=1&skip_status=1&screen_name=@@
06:25:07: FAILED GET: (591727) 403
https://api.twitter.com/1.1/users/lookup.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&include_mute_edge=1&include_can_dm=1&skip_status=1&screen_name=@@
06:25:07: * WARNING: Request failed with Twitter response: To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.
06:25:07: error: deserialising: pPa8fuX9G type: List`1
06:25:07: {"errors":[{"code":326,"message":"To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.","sub_error_code":0,"bounce_location":"https://twitter.com/account/access"}]}
06:25:07: ERROR: scrape users from ID :Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.Collections.Generic.List`1[LibTwitterJsonData.JsonUser]' because the type requires a JSON array (e.g. [1,2,3]) to deserialize correctly.
To fix this error either change the JSON to a JSON array (e.g. [1,2,3]) or change the deserialized type so that it is a normal .NET type (e.g. not a primitive type like integer, not a collection type like an array or List<T>) that can be deserialized from a JSON object. JsonObjectAttribute can also be added to the type to force it to deserialize from a JSON object.
Path 'errors', line 1, position 10.
06:25:07: No users found for: https://mobile.twitter.com/@@
06:25:07: * FAILED: UserDetails: https://mobile.twitter.com/@@ with: @@
06:25:07: 0
<null>
<null>
06:25:07: Started: 08/08/2019 06:25 AM
Finished: 08/08/2019 06:25 AM
ID: 9e15e0a5-e5c2-4b67-b1e2-116b5f228987
06:25:07: Action ran for: 0hr:0min:1s
06:25:07: finished processThread: updateaccounts 9e15e0a5-e5c2-4b67-b1e2-116b5f228987

While this one count as (Failed)

Code: Select all

06:16:14: Current time: 06:16:00
06:16:14: Now: 2019-08-08 0616 Start: 2019-08-08 2100 End: 2019-08-09 0700
06:16:14:  Account Can run: 06:16:00  start: 21:00:00 / stop: 07:00:00
06:16:25: Starting: 08/08/2019 06:16 AM
06:16:29: Checking account: @@
06:16:29: Login: @@ : @@ Proxy: @@ 
06:16:29: UA: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
06:16:29: Login: get: https://twitter.com/
06:16:29: GET: https://twitter.com/
06:16:30: GET: 200
https://twitter.com/account/access
06:16:30: Login: Failed validate: 200
https://twitter.com/account/access
06:16:30: Login: Get: https://twitter.com/login?redirect_after_login=https%3A/twitter.com/
06:16:30: GET: https://twitter.com/login?redirect_after_login=https%3A/twitter.com/
06:16:31: GET: 200
https://twitter.com/account/access
06:16:31: Login: Post: https://twitter.com/sessions 
06:16:31: POST: https://twitter.com/sessions
06:16:31: POST: 200
https://twitter.com/account/access
06:16:31: Account appears to require recaptcha which is currently not supported
06:16:31: Response URL: https://twitter.com/account/access
06:16:31: * UNKNOWN ERROR OCCURRED - see logs for more info.
If the problem continues, please submit logs to support.
Account requires captcha solving to unlock - not currently supported. Please log into account and pass verification challenges manually

06:16:36: finished processThread: updateaccounts dfbeee09-bd1b-4c1b-b294-66e16a1f2b45

So there might be an error of my previous conclusion about chain and user being used two times at the same time!

I will give it more investigation and if any new news founded.. I will post here.

[martin@rootjazz]

The things I do:

1- I set an actions for accounts and work them.. after that ((I got problem with counting account as failed login when it's not)) I pause all actions for test to see whats wrong.

2- After pausing them I remove all working hours from accounts and then redo it

3- After that I make working hours for the actions

4- When I restart the actions from (Pause) it all hang and give the same error

5- Force close TD and start it again and run the action cause the same problem!

6- I export the actions.. if you want I will send you some to test it. (many accounts is with proxy so no worries here)

Here is the log_id: logs_55884

checking...

Update 2

Apparently.. there is a problem with TD..

If I got account need a recaptcha or changing password.. and I verify login without cookies it will count as successful.

Fixed

[martin@rootjazz]

Here is the log_id: logs_55884

I cannot find the logs you are referencing in your logs. In future, when you see a real time log that makes you think something is not working. Can you copy that log snippet as well. It will then allow me to search for it in the full app logs which should allow me to find it easily rather than blindly trying to check 100s /1000s of files looking for what you noticed already.

[martin@rootjazz]

recaptcha [x] fix

https://rootjazz.com/twitterdub/updatetesting.html