-
Notifications
You must be signed in to change notification settings - Fork 23
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
AWS views proxy checking as an abusive activity #4
Comments
It's not safe to run proxy checking with AWS. They blocked all traffic, had to terminate the instance. |
How much bandwidth did it take per month to run the checker? |
Never measured. |
If not, then can you tell about how the code worked or even share it? Did you request some IP tracking website for all addresses through the proxy connections? |
This comment was marked as spam.
This comment was marked as spam.
the code is in the repo, .sh files |
Where's |
I'm afraid it is not for you if you can't even figure this out. Hint: cd ~/proxy-scraper-checker |
I just didn't bother to do it. |
I didn't. You're misrepresenting the facts. I made this proxy-list for my own personal usage when their repo was down.
This conversation is over then. I don't see the point in your messages. |
Information for consideration
AWS has automatically taken action due to no response from the client:
The text was updated successfully, but these errors were encountered: