Rootjazz

It seems to be an issue with cookies/login but TD says it's a proxy connection issue. I verified all the accounts without "cookies" checked and they were successfully verified. No more network error Just an update for anyone else experiencing the same simply verify them without cookies and...

+1

TD sends messages to the same people in repeat believing they are new followers. I checked and I messaged some people 10 times believing they are new followers lol

All the antivirus software and firewalls are turned off. I am not on any VPN. I can confirm that the proxies and accounts work as with the very same proxies through "Open ACC in session browser" I can use the accounts via the same proxy that I get the "network failure" error. The...

Hello Martin, Right after the migration of twitter.com -> x.com I began to receive "Network Failure" error on all my accounts. They all use proxy and I receive this error in the raw logs but if I open the accounts via the Browser it just logins to the accounts and they open normally so the...

+1

I've managed to recover them from a 10-day old backup. For some reason, the accounts were renamed to _FAILED_LOAD and thus TD wouldn't recognize them. Screenshot for reference: https://prnt.sc/igW8OiyY7fsE I found the same accounts in working condition in a previous backup and I moved them to dbacco...

Hello, Last night in my TD instance I had 283 and today I woke up to 129, I had to check my backup accounts file inside -> Roaming\rootjazz\Twitterdub\database\backup\accounts and the latest 7 days backups all contain 283 accs each. Even inside my Roaming\rootjazz\Twitterdub\database\dbaccount I hav...

Same problem here, can't send DMs

* ERROR: Direct Message: Invalid JavaScript property identifier character: |. Path '', line 1, position 3.

I tried increasing threads +1 and I've got the same results, still not executing. Nothing changed. If it turn AUTO RUN off and I start them manually, they execute once, and then they are left on "waiting" until I start them manually again. I migrated to a new instance of TD and the issue i...

I've got the same problem happening again, last time I solved it by exporting all my accounts, exporting all the actions, and installing them into a clean-new TD Instance.

Any idea how to fix that besides transferring everything again? This time it happened on version 3.6.2.8