Requests to AWS starts throwing [Errno 113] No route to host about cloudproxy HOT 3 CLOSED

The ALIVE checks are a very basic check, essentially Cloudproxy does a proxy request using the deployed proxy, in this case your AWS proxy that is deployed. It does this by calling https://api.ipify.org/ and checks the response is the same as the IP of the proxy you've deployed. Ipify has no limits so shouldn't be causing this.

Is there a chance a local firewall or ISP issues are causing drop outs? When this issue occurs, are you able to use the proxies as normal? Though Cloudproxy may start replacing them all before you can test this I assume.

from cloudproxy.

Thank you for the reply.

I agree that the ALIVE check is an unlikely culprit, other than maybe contributing to congesting the network (45 requests per minute). However, I believe commit 7658129 bypassed the ipify check so fetch_ip() isn't used anymore? Or it might be the Github search tricking me. Regardless, CloudProxy killing instances is more likely due to instances refusing connections and thereby failing the ALIVE check than CloudProxy actually causing the issue.

My main theories was that there is some kind of limit on AWS or that TinyProxy isn't shutting down open connections, causing the EC2 instance to overload and refuse new connections. This is difficult to verify though so I was primarily hoping that maybe this is a known issue. But if I'm the only having the problem, it's more likely to be on my end.

I finally figured out a way to make AWS requests directly from my main application, so I won't have to use a Python Flask script as middleman. This should halve the number of local requests needed, although it doesn't change the number of outgoing requests to AWS. It seems to be working fine for now so this issue can be marked as solved. If the problem continues, I'll just have to dial down the number of requests.

from cloudproxy.

You're right, fetch_ip() isn't used anymore.

Let me know if the issue arises again. I currently do weekly automatic integration to test with all cloud providers. I will look to extend one of the tests and leave it running for a few days, see if I can repeat the error.

from cloudproxy.