Anyone having 503 error code on twitterdub?

[faxnet]

Hi,

Since yesterday I am having issues login/generating api keys with new accounts I bought.
I tested some with fresh proxies, others with old proxies that are already working well with twitterdub.

With twitterdub sometimes I will get a 503 or sometimes it will just fail without error. I tried manually in browser and I often get the "something is technically wrong" page. So I know it is not a twitterdub issue.

What I want to know is if the problem is coming from my new accounts or twitter itself (503 is when twitter is overloaded but it's been a full day now).
I didn't see anywhere online that twitter status was bad for api etc... only streams.

If anyone had some issues like that please comment here.

Thanks

[faxnet]

After more testing, I concluded that the issue is on twitter side. Issue is happening with an handmade, pva, residential ip account.
the buggy domain is "apps.twitter.com" needs to retrymultiple times to get things working but that can lead to a suspension... so better wait

[bitcoin]

? could you explain a bit more please? :)

[faxnet]

I opened a ticket on twitter and the support confirm that it is happening.
https://twittercommunity.com/t/lot-of-5 ... -com/93413
If we want a faster resolution we need to post more messages there so please do
If you want to test it, just take a lot of accounts in TD and try to verify login (careful because I got some accounts suspended with TD retrying 3 times to login) or you could just try it manually by login in apps.twitter.com and browse randomly clicking on different links. At some point you will get the error page.

? could you explain a bit more please?

[omegasolutions]

Post logs

[martin@rootjazz]

I (careful because I got some accounts suspended with TD retrying 3 times to login) or you could just try it manually by login in apps.twitter.com a

I am unsure why it tries 3 times, probably when coding it, it failed sometimes, but on retry it worked.

IF the consensus is this is bad, I will remove it and the attempt will just fail, and it will be up to you to retry the action.

Let me know what you think

[faxnet]

Hi martin I think this is better as a setting if possible. If not (necessary), putting back to 1 and letting the user retry may be better. Not sure what is the best here. I never got a login fail on twitter when doing it manually, I don't think it is that frequent (at least when using twitter.com and not apps.twitter.com)

I (careful because I got some accounts suspended with TD retrying 3 times to login) or you could just try it manually by login in apps.twitter.com a

I am unsure why it tries 3 times, probably when coding it, it failed sometimes, but on retry it worked.

IF the consensus is this is bad, I will remove it and the attempt will just fail, and it will be up to you to retry the action.

Let me know what you think

[faxnet]

Post logs

Not sure why you need my logs because you could just try it yourself in TD (or in browser), it happens so frequently you will probably get the error on first try
I did retry some logins and they were successful, the remaining new accounts I have right now I dont want to risk them because I already lost around 20 accounts.
But... here they are:

when I tried to generate the api key.

* SUCCESS: verifed account successfully
Setup client details: ***** Proxy: 196.17.***.**
Generated client name: umqqwv6w oz5nrn9tv
Generated client desc: zq8l3wf2 gz3ppsax7 h6dxmccs r9fo2rumn p9pdbsc j79nlww9v
Generated websiteUrl: http://pwt0oiivgkah.com
Generated authRedirect: http://pwt0oiivgkah.com/twitterauth.php
Details generated:
ClientName: umqqwv6w oz5nrn9tv
clientDesc: zq8l3wf2 gz3ppsax7 h6dxmccs r9fo2rumn p9pdbsc j79nlww9v
websiteUrl: http://pwt0oiivgkah.com
authRedirect: http://pwt0oiivgkah.com/twitterauth.php
Get Page: https://apps.twitter.com/app/new with: *****
Get token: ******
Token: JODBXJxFpJhJFPKELVXP8mJQ5hZQHxvIbTrUljoY72I: ******
Post Details:
Update permissions:
Update permissions: appUrl: https://apps.twitter.com/app/new
Update permissions: keysUrl: https://apps.twitter.com/app/new/keys
* FAILED: 394875689204623979802426 : Couldn't extract keys
* FAILED: 394875689204623979802426 : Couldn't extract keys

and another one with login attempt generating a 503

16:58:15: Validate account via login *********
16:58:15: No oauth - attempt to login validate: *********
16:58:15: Login: ********* : ********* Proxy: 23.9 *********
16:58:15: UA: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
16:58:15: Login: get: https://apps.twitter.com/
16:58:15: Login: Get: https://twitter.com/login?redirect_afte ... itter.com/
16:58:15: Login: Post: https://twitter.com/sessions
16:58:16: Login: Failed validate:
16:58:16: * FAILED attempt: 1
16:58:16: Login: ********* : ********* Proxy: 23.9 *********
16:58:16: UA: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
16:58:16: Login: get: https://apps.twitter.com/
16:58:17: Login: Get: https://twitter.com/login?redirect_afte ... itter.com/
16:58:17: Login: Post: https://twitter.com/sessions
16:58:17: * FAILED to POST https://twitter.com/
503
https://apps.twitter.com/
16:58:17: Validate account failed: FAILED to POST https://twitter.com/com - status check: 503
https://apps.twitter.com/: *********

And another one that didnt get a 503 but failed three times and got suspended

16:58:19: Validate account via login ****** ******
16:58:19: No oauth - attempt to login validate: ******
16:58:19: Login: ****** : ****** Proxy: 107.1******
16:58:19: UA: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
16:58:19: Login: get: https://apps.twitter.com/
16:58:19: Login: Get: https://twitter.com/login?redirect_afte ... itter.com/
16:58:20: Login: Post: https://twitter.com/sessions
16:58:20: Login: Failed validate:
16:58:20: * FAILED attempt: 1
16:58:20: Login: ****** : ****** Proxy: 107.******
16:58:20: UA: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
16:58:20: Login: get: https://apps.twitter.com/
16:58:20: Login: Get: https://twitter.com/login?redirect_afte ... itter.com/
16:58:21: Login: Post: https://twitter.com/sessions
16:58:21: Login: Failed validate:
16:58:21: * FAILED attempt: 2
16:58:21: Login: ****** : ****** Proxy: 107.******
16:58:21: UA: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
16:58:21: Login: get: https://apps.twitter.com/
16:58:21: Login: Get: https://twitter.com/login?redirect_afte ... itter.com/
16:58:21: Login: Post: https://twitter.com/sessions
16:58:22: Login: Failed validate:
16:58:22: * FAILED attempt: 3
16:58:22: No more attempts
16:58:22: Validate account failed: Failed to login: Couldn't not validate: 200 https://apps.twitter.com/: ******


Please go to the forum post for more help on creating consumer API keys: viewtopic.php?f=30&t=1635
Started: 15/09/2017 02:37 AM
Finished: 15/09/2017 02:37 AM

[faxnet]

check out this screenshot, all api generation failing, login was ok but api key is failing at different steps because 503 is random

[martin@rootjazz]

Post logs

Not sure why you need my logs because you could just try it yourself in TD (or in browser), it happens so frequently you will probably get the error on first try

Logs never hurt. If submit an issue, submit logs. 9/10 I need them. If you don't post them, then I need to ask for them, depending on time difference that can be 1 day after you submit the issue then I reply, then one day for you to submit logs, then one day for me to see reply. Thus 3 days wasted, when I could have investigated the logs on day1 when I first looked at the issue.

Probably you haven't seen, but at the top of EVERY board on teh forum there is an announcement *** PLEASE READ IF SUBMITTING AN ISSUE*** don't worry, no one reads it but it basically says

Please, read through this post and submit your issue accordingly. Not everything will be relevant to your issue, but have a read as it gives an idea of the information you can provide to help me help you as quickly as possible without delays in having to request additional information

https://rootjazz.com/forum/viewtopic.php?f=23&t=1634



Regards,
Martin

The forum posts, basically lists every single piece I am likely to need to solve the issue first time I look at it (80% of the time).
Sometimes a bug is a bug and effects everyone everywhere everytime. These are easy to fix. Other bugs effect some users, some IPs, some actions ONLY if done in a special way.

Reporting X does not work. Well what do you mean by not work? app crash / app freeze / app doesn't do what you think it should/ app errors / app falsely reports. I need exacts.

I have a problem here are my 20,000 lines of logs. ok, so you noticed something, I don't know what. I cannot read 20,000 logs to guess what you saw as an issue, when you could say "this line I noticed and is a bug". You have now saved me about an hour of guessing your issue and wasting time as I can never guess an issue.

Sometimes a bug only happens with options a,b,c,d. A screenshot lets me test exactly what you did, I can replicate what you did and cause you issue I can solve. If you say "likes don't work" I test likes, they work. But you forgot to say, shared likes with multi search and filter x y z. Now I know and can fix.


Thus, the poster was trying to save time by suggestion you submit knowing I would probaby ask for logs and you could submit before I saw the post