-
Notifications
You must be signed in to change notification settings - Fork 482
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
Received HTTP Error 429: Too Many Requests #36
Comments
Hi @Jay1508 - thanks for taking the time to submit an issue. Unfortunately, the number of search requests is still too many in a given time period. I'm working on a branch now that when it detects this, backs off for some time. Still tweaking it, but a minimum of 30 minutes may be necessary. For now, I'd try tuning up It's just one of those tools that requires patience and takes a few days to run. |
Thanks opsdisk for your reply. I have heard about using exponential back off as a possible solution. 30 minutes seems a lot to me. I have received the 429 response code after 10ish dorks. There are now almost 6000 dorks in the database. I havent tried my luck with bank of proxies yet. |
It used to be 10 minutes or so, but I had to wait almost 30 minutes during some unofficial testing a few weeks ago. It may be that you get penalized more if it keeps flagging your IP. Having multiple proxies you can go through spreads the requests and cuts down on the total time, but it's bit more to manage and costs a few bucks. Going to close this one out, but let me know if you have any other issues or questions. |
Hi,
I have received this http error message after 10 searches: HTTP Error 429: Too Many Requests. I have used a high delay (-e 30.0). I have tried to change my IP but no joy!
Any ideas how I can solve this.
thank you
Jay!
The text was updated successfully, but these errors were encountered: