Rootjazz

So I just imported 50 new accounts and set them all up with proxies and for some reason it looks like it ignored all the proxies and generated API keys for each account without proxies.

When I login to each account and go to Twitter Data it shows a login from my IP Address and not the proxy.

Not sure why it didnt use the proxies I had inputed for each account? Did I do something wrong?

It should use proxies for everything if set correctly.

Do you stil have the logs?


Did you ONLY generate API keys and authorise with these accounts? Or run other actions?


What version are you on?
HELP > ABOUT

Can you double click the account and check the ACCOUNT PROXY box, is it empty?

I have had the same issue unfortunately, I used proxies too but logging into twitter data shows the API key was initially created on my home IP... that explains how all 600 accounts were banned at once two separate times for me.

same issue +1

that definitely should not be happening. Let me run some tests

its work fine proxies with Authorise accounts,

just happen with generate with API key.

I am not seeing how it is possible to create API keys without using the specified proxy.

Are you sure it was THIS action that ignore the proxy, or perhaps it "could" have been another action you have performed?


I am still running tests, but not found anything ignoring the proxy value

what version you using

use beta test with same issue or i go to lan setting add mine proxies .

I am using the latest / testing version.


Still I cannot replicate this for generate app action.


IF you add a new account
generate app keys

then login to twitter.com and view the data USING THE PROXY in the browser, do you see the local IP?
Do not perform ANY OTHER ACTIONS, this could be the issue. You *think* it is the generate keys action, but the actualy problem is caused by a different action - hence why I cannot replicate?