Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

username requires manual verification on instagram (429). #2

Open
dremara opened this issue Mar 5, 2018 · 7 comments
Open

username requires manual verification on instagram (429). #2

dremara opened this issue Mar 5, 2018 · 7 comments

Comments

@dremara
Copy link

dremara commented Mar 5, 2018

excuse me if this is an easy solve, i'm not a tech buff.
i'm running 100 threads on a list of 70000 words to check for instagram using approx 350 free proxies that all check out as good.

however 95% of my returns are 'requires manual verification on instagram (429).' and there will then be a very brief period where the script works for a few usernames before going back to the 429 error.

i know i'm doing something wrong, i know the answer may be obvious to most, but i'd really appreciate some help with this one.
thanks.
andreas

@dremara
Copy link
Author

dremara commented Mar 5, 2018

oh, also the available names are not outputting properly to available.txt, all lines output read

https://www.instagram.com/accounts/web_create_ajax/attempt/

@yellow
Copy link
Contributor

yellow commented Mar 5, 2018

Can confirm.
But I faced this issue while checking twitters.
I even tried using a single thread but the issue is not solved.

@crock
Copy link
Member

crock commented Mar 16, 2018

@dremara @yellow Yes, I am aware of the issue and am working on creating a caching system to solve this. The issue is due to Instagram's strict rate limits. You can only make so many requests per 15 minute window.

A quick and dirty workaround is to not use more than 2 threads and 300 word lists when checking Instagram or Twitter. All the other services shouldn't have a problem with the 100 threads.

@ZXT-Tech
Copy link

ZXT-Tech commented Jul 11, 2018

@crock the problem is the proxy checker and the whole proxy integration isn't working.

scripts@L2:~/cli-checker$ python3 OGCheckr.py
Checking and filtering out bad proxies...
Starting up threads...
[Thread-0] has started.
notworking is working...
github.com:8080 is working...
something:3128 is working...
is working...
Done.

Searched 4 proxies and filtered out 0 bad proxies in 0.44285035133361816 seconds
Starting up threads...

@crock
Copy link
Member

crock commented Jul 11, 2018

@ZXT-Tech Thank you for bringing this to my attention. I think it's time for me to look into unit testing, so I can catch stuff like this.

@lgg
Copy link

lgg commented May 24, 2020

@crock i have same issue with github and 4 threads.

@crock
Copy link
Member

crock commented May 24, 2020

i have same issue with github and 4 threads.
@lgg

I think GitHub heavily rate limits. You can try using some free proxy lists (like 100 or so) or get a couple of premium "rotating" proxies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants