Possible reason of suspension

[martin@rootjazz]

you seems missed my recent post about troubles while liking(possibly)

I don't see this posted above? Maybe you mean a different thread? If so, please if you are posting a new issue in a new thread that you think is related to a previous thread you made, please do link. I don't remember specific threads to specific users all the time so I may not be aware

Here is a flow i found.

Code: Select all

16:21:57: tweets: 173
16:21:57: Tweets: 173 from: 104 profiles
16:22:00: Paused for 2secs
16:22:00: Got enough: 1/1
16:22:00: Results: 1
16:22:04: return results: Timeline 1
16:22:04: Login: Success validate:
16:22:04: 200
https://twitter.com/
16:22:05: CaptchaFlowCheck
16:22:05: 401
https://twitter.com/i/users/prompts

16:22:05: prompts request returned null!
16:22:05: Already logged in: Account
16:22:05: cookieslogout:
guest_id: ...

here is an error i talking about. logout for some unknown reason getting 401
and after this account become suspended in a moment it trying to like

The 401 is just a return on a request that may return or may not (same as in the browser). That 401 shouldn't be causing any issues. And the logs show the login as successful.


Again, it would be useful for you to test as described above with an account you have confirmed (on the proxy) can login manually through the browser




Regards,
Martin

[axisar]

I don't see this posted above? Maybe you mean a different thread?

viewtopic.php?f=30&t=9606#p61835

can login manually through the browser

forget about it for a time. the main reason is an infinite suspend

EDIT: forget about everything bellow. it appears in all log files for some reason...
and i mostly told about this:

Code: Select all

16:22:05: cookieslogout:

Code: Select all

16:22:05: 401
https://twitter.com/i/users/prompts

16:22:05: prompts request returned null!

this part appears from time to time with different error codes in all action logs.

[martin@rootjazz]

EDIT: forget about everything bellow. it appears in all log files for some reason...
and i mostly told about this:

Code: Select all

16:22:05: cookieslogout:

oops, that is a terrible choice of term on my behalf. It doesn't mean "logout" how you think it does. It means "this is a log output of the current cookies".
Out in this instance is short for output.

I have changed the term used for future update to avoid confusion

Code: Select all

16:22:05: 401
https://twitter.com/i/users/prompts

16:22:05: prompts request returned null!

this part appears from time to time with different error codes in all action logs.

yes as explained above, on login, twitter calls that page, it might have content, it might not

[axisar]

Okay. Another connected problem i guess. Because behavior is the same.
The story:
Yesterday my account was call locked. While i tried to unlock it, i made many tries and twitter block ability to unlock for some time.
And the problem
During this time TD MADE 72!! new logins during 12 hours including not working hours, i.e. 72 logins in about 3 or 4 hours . https://i.imgur.com/ijPjQWO.png . EACH ACTIVITY MAKING A LOGIN RETRY.
And yes. All logins from same place and same IP with same browser and etc.
And please dont tell me its okay, because its not.

[martin@rootjazz]

Okay. Another connected problem i guess. Because behavior is the same.
The story:
Yesterday my account was call locked. While i tried to unlock it, i made many tries and twitter block ability to unlock for some time.
And the problem
During this time TD MADE 72!! new logins during 12 hours including not working hours, i.e. 72 logins in about 3 or 4 hours . https://i.imgur.com/ijPjQWO.png . EACH ACTIVITY MAKING A LOGIN RETRY.
And yes. All logins from same place and same IP with same browser and etc.
And please dont tell me its okay, because its not.

Please submit logs so I can see what happened.

Also detail what actions you are running. Type of actions / options.

Sounds like the program didn't detect the failed login requires user input (receive a phone call) and didn't flag the account for blocking. I need to see the logs so this can be detected and added




Regards,
Martin

[axisar]

Sounds like the program didn't detect the failed login requires user input (receive a phone call) and didn't flag the account for blocking. I need to see the logs so this can be detected and added

Account was marked as failed last login all the time.
is there any special logs per action i have to know? Or only log.date.action.ID.log?

[martin@rootjazz]

Sounds like the program didn't detect the failed login requires user input (receive a phone call) and didn't flag the account for blocking. I need to see the logs so this can be detected and added

Account was marked as failed last login all the time.

Yes but some fails are different. A normal fail will not lock the account. A specific fail (blocked / suspended / requires manual intervention) should block the account locally.

is there any special logs per action i have to know? Or only log.date.action.ID.log?

If it happened in the last 7 days, just submit logs:
HELP > LOGS > SUBMIT

then send your logs ID - the first 4 numbers is sufficient (displayed after successful uploading of logs)





Regards,
Martin

[axisar]

sad but i set 1 day for logs.
just saved files with account name appearance and date was changed on vps.
So i can share only these saved files, thats why i`m asking about more logs what can disclose the problem. because mostly files log.date.actionID.log not have any error descriptions.

[axisar]

65513 and 62993 same logs
hope data kept
acc name ellar****

[axisar]

Another account just suspedned.
Resubmitted logs
ID 17893
acc EleNo***