Misunderstanding of the RT parameters

[bottyx]

Up

[martin@rootjazz]

I was running 2 accounts to test, Unique items and Share Accross Accounts checked. Each account is running under a different datacenter proxy (not resdientials) from a qualitative proxy provider.

Twitter will know it's a data centre IP. And there is only one reason data centre IPs would be accessing the twitter site: bots. That's it.

Hence, this is very unlikely to be the cause.

Honestly, it probably is. But we can only test. Try the same kind of account, same kind of usage, from your local IP. If the same problems occur, it's likely bot caused. If it does not. We can point more firmly at the IP.

See the issue I'm encountering below but once I get the "This Site Can't Be Reached", the deletion of the token is instant.

That's a server level block of the request. If the proxy just went down, it wouldn't mean the token is deleted after. As it's happened after, twitter server is blocking the request and then forcing you to reset the cookies as it returned a response to delete them.

[martin@rootjazz]

Up

apologies, been off all week more or less with an ill child, sorry

[martin@rootjazz]

Thank you very much for your help!

I've tried many things but it appears the issue isn't the processor but the log in step. Indeed, now, when I "open Acc in session browser", sometimes it doesn't work and it says "This Site Can't Be Reached". At first I thought it was a proxy issue, that the proxy IP got flagged or something but when I get this error, if I open another tab and I try to do another research on Google, it won't work either, so it's more like a browser-proxy issue. Sometimes, it asks me about my proxy credentials even though they are correctly put in the account profile in Twitterdub. Anyway, every time this issue occurs, the auth_token gets deleted for the account in their profile page. But which is even weirder, is that if I try to open again the account after its token was deleted, the ChromeDriver would sometimes reach the X homepage, and sometimes wouldn't. I really don't see what's the real issue and what could be done on my hand.

I sent you the raw logs for one of my accounts that got the "This Site Can't Be Reached" error and got its auth_token deleted just after in its profile.

ok, then this is strange. It sounds like a configuration issue.

With the chromedriver login, TD just passes the IP to the driver to use. It all happens with the driver, nothing to do with me, so should "just" work.

Same for the new browser bridge code.

I am going to be removing the driver browser to use only the browser bridge, if I can clear support back logged from the last week, I will be on that today. If not tomorrow

[bottyx]

ok, then this is strange. It sounds like a configuration issue.

With the chromedriver login, TD just passes the IP to the driver to use. It all happens with the driver, nothing to do with me, so should "just" work.

Same for the new browser bridge code.

I am going to be removing the driver browser to use only the browser bridge, if I can clear support back logged from the last week, I will be on that today. If not tomorrow

Now, when I open the accounts in the browser, or when I'm trying to do the Custom RT Search, everything looks fine but it takes like minimum 25s to actually load the page, which is way too long, and I think that's' why the actions can't go through (I read somewhere else that if the page loads too slowly, the processor marks the action as failed).

I did a speedtest and I am around 1 MB/s upload/download, which is very slow but should allow me to load Twitter pages fast (in around 5-7s, not 25) (not videos tho). The response time is good though, around 650 ms. So I contacted the customer service of my proxy provider, they did all kind of tests and everything work on their hand, the proxies shouldn't be that slow. They told me that they think that the proxy setup for the Chrome Webdriver is the issue. What do you think?

Here is a part of the log, where the error is, might help you:

WARNING error detected: retweet:946e64c2-d324-470d-a528-3f452badc830 ExFailed EX_FAILED: 2398784376598734 TIMEOUT Failed to extract tweet details: https://x.com/artsch00lreject/status/18 ... 8229341352 TweetDetail job:946e64c2-d324-470d-a528-3f452badc830
Failed performloop: 32946238046238746239874623987 : error in bridge processing: retweet:946e64c2-d324-470d-a528-3f452badc830 ExFailed EX_FAILED: 2398784376598734 TIMEOUT Failed to extract tweet details: https://x.com/artsch00lreject/status/18 ... 8229341352 TweetDetail job:946e64c2-d324-470d-a528-3f452badc830

[martin@rootjazz]

Now, when I open the accounts in the browser, or when I'm trying to do the Custom RT Search, everything looks fine but it takes like minimum 25s to actually load the page, which is way too long, and I think that's' why the actions can't go through (I read somewhere else that if the page loads too slowly, the processor marks the action as failed).

1) better proxies would help, as 25 seconds to load a page is slow, and that's all on the proxy

2) turn off media loading: TOOLS > BROWSER > BLOCK MEDIA

3) Increase page load timeout: TOOLS > BROWSER > TIMEOUT

The timeout is for PAGE LOAD, which may not include ALL the components of the page as twitter uses delayed loading. I will check again where the delay and ensure that section is also able to wait

I did a speedtest and I am around 1 MB/s upload/download, which is very slow but should allow me to load Twitter pages fast (in around 5-7s, not 25)

that should be plenty to load the page with no media, can you confirm if you are showing the media?

It may help to understand, if I could test here. If that is ok with you, export the account and send me the details and I can test and try and find ways it can be improved

Code: Select all

support[at]rootjazz[dot]com

They told me that they think that the proxy setup for the Chrome Webdriver is the issue. What do you think?

It's chrome, it should work fine, I doubt it's that tbh

WARNING error detected: retweet:946e64c2-d324-470d-a528-3f452badc830 ExFailed EX_FAILED: 2398784376598734 TIMEOUT Failed to extract tweet details: https://x.com/artsch00lreject/status/18 ... 8229341352 TweetDetail job:946e64c2-d324-470d-a528-3f452badc830
Failed performloop: 32946238046238746239874623987 : error in bridge processing: retweet:946e64c2-d324-470d-a528-3f452badc830 ExFailed EX_FAILED: 2398784376598734 TIMEOUT Failed to extract tweet details: https://x.com/artsch00lreject/status/18 ... 8229341352 TweetDetail job:946e64c2-d324-470d-a528-3f452badc830

When the tweet page loads, there is a data file sent in the background from twitter server to the webpage, TD is intercepting this to extract the details. But it's not being detected. Which would mean
1) it hasn't been received yet
2) it was received and the program failed to detect it.

Does this issue happen everytime? On every tweet URL?

[bottyx]

1) better proxies would help, as 25 seconds to load a page is slow, and that's all on the proxy

2) turn off media loading: TOOLS > BROWSER > BLOCK MEDIA

3) Increase page load timeout: TOOLS > BROWSER > TIMEOUT

The timeout is for PAGE LOAD, which may not include ALL the components of the page as twitter uses delayed loading. I will check again where the delay and ensure that section is also able to wait

Do you have any proxy provider to recommend in particular?
I did turn off the media loading and increased the page load timeout to 30s, but still hasn't helped me to solve my problem here.

that should be plenty to load the page with no media, can you confirm if you are showing the media?

It may help to understand, if I could test here. If that is ok with you, export the account and send me the details and I can test and try and find ways it can be improved

Code: Select all

support[at]rootjazz[dot]com

I just sent you three of my accounts that didn’t work.

It's chrome, it should work fine, I doubt it's that tbh

I tried to open the exact same account with the exact same proxies on Lyra Robotics and it worked well, pages load in 2s and no error or any latencies. That's what makes me think that has nothing to do with the proxies but the ChromeDriver.

When the tweet page loads, there is a data file sent in the background from twitter server to the webpage, TD is intercepting this to extract the details. But it's not being detected. Which would mean
1) it hasn't been received yet
2) it was received and the program failed to detect it.

Does this issue happen everytime? On every tweet URL?

Yeah that's the issue I encounter every single time the processor tries to RT a post. On every tweet URL.

I also noticed that after processing an action (RT), TwitterDub automatically changes the auth_token of every account selected for the action (in the Shared Across Account action) to the auth_token of the first account (selected, checked) in the list. This is very frustrating because I either have to delete and re-import the accounts or manually change the auth_token for each affected account on their Profile Page. It might be part of my issue or a whole other problem to fix...

[bottyx]

Yeah that's the issue I encounter every single time the processor tries to RT a post. On every tweet URL.

I also noticed that after processing an action (RT), TwitterDub automatically changes the auth_token of every account selected for the action (in the Shared Across Account action) to the auth_token of the first account (selected, checked) in the list. This is very frustrating because I either have to delete and re-import the accounts or manually change the auth_token for each affected account on their Profile Page. It might be part of my issue or a whole other problem to fix...

As I told you by e-mail, I tried a new proxy provider and it looks like the loading issue got solved. However, I still have the "error in bridge processing". I sent you the raw logs of the new attempt witht the new proxies. I also still have the auth_token issue mentioned above which is really weird and annoying because the auth_tokens get changed automatically by TD after doing a RT action (C:\Users\u-sic\Desktop\influ-all.csv,rand, Share Accross Accounts, Unique Items, Random Pause: 1 - 1, Max Actions: 1, Repeat Hours: 1, Custom Search --> A User ID or URL --> User retweets --> Items to return for this search stage: 1) and if I don't pay attention, I might think that I use different accounts to execute an action but because the auth_token got changed, the action will be performed by 1 single account (the one to which the auth_token changed on all accounts refers) which will more likely lead to a ban of the account.

[martin@rootjazz]

I tried to open the exact same account with the exact same proxies on Lyra Robotics and it worked well, pages load in 2s and no error or any latencies. That's what makes me think that has nothing to do with the proxies but the ChromeDriver.

Ok it cannot be the proxy then, you said above you sent me some accounts, I haven't been through emails yet, but when I do I will test.
Hopefully you linked to this thread so I know the accounts are related to this issue

Yeah that's the issue I encounter every single time the processor tries to RT a post. On every tweet URL.

Ok, something is clearly not working, if this happens every time.

Where are you using the software? Home machine or a VPS? If a VPS, could I log in and have a test? In case I cannot find any issue with your accounts there, it may be something with the machine, or the machine+account exposing some issue.

I also noticed that after processing an action (RT), TwitterDub automatically changes the auth_token of every account selected for the action (in the Shared Across Account action) to the auth_token of the first account (selected, checked) in the list.

What! That should NOT happen. Is this all shared account actions? Or only occasionally / depending on the options specified? I will need to investigate this ASAP as it sounds like a serious bug

To confirm.
You select 5 accounts to perform a shared followed action of 5 items, 1 item per account.
After the action has completed. All accounts have the same AUTH_TOKEN as the first account?

[bottyx]

Ok, something is clearly not working, if this happens every time.

Where are you using the software? Home machine or a VPS? If a VPS, could I log in and have a test? In case I cannot find any issue with your accounts there, it may be something with the machine, or the machine+account exposing some issue.

I was using the software both on my own machine and on a VPS. But because it didn't work on any of them, I did not renew the VPS service. Waiting for TD to work again before spending $50 in the vacuum. But I do confirm that I had the exact same issues on both machines though.

What! That should NOT happen. Is this all shared account actions? Or only occasionally / depending on the options specified? I will need to investigate this ASAP as it sounds like a serious bug

It does happen for follow, retweet and like shared account actions. Every single time.

To confirm.
You select 5 accounts to perform a shared followed action of 5 items, 1 item per account.
After the action has completed. All accounts have the same AUTH_TOKEN as the first account?

I confirm!!

I sent you an email talking about that problem too, but just in case my logs are 49069.