Mauro Rezende

My 2c, as I have suffered and worked to work around Instagram's unpredictable behavior. My assumption, based on trial-and-error experiments is that Instagram has become much more sensitive to repeated...

Adding to my previous comment, I just got this error (see the image) on my mobile. This pretty much suggests Instagram has added much stricter controls. 

We tested some rotating proxies providers and managed to work around this issue, but it still requires some error handling and backoff-and-retry strategies. Of course, that would mean additional cost.

As I mentioned in a previous comment, success is a hit-and-miss depending on how lucky you are staying below Instagram's decision of what can be downloaded by whom and when,...

See my comment on the other thread for a potential explanation on what's going on. I'm suffering from similar issues, but I believe Instagram is at fault, not Instaloader. https://github.com/instaloader/instaloader/issues/1617#issuecomment-1198201613

I believe this a duplicate of https://github.com/instaloader/instaloader/issues/1617

My 2 cents, and from experience in a production environment, is that Instagram became much more sensitive about the IPs users connect from in the last few of weeks. Especially...

> Yes, technically you could set the proxy-related environment variables programatically for each request, as suggested in [#174 (comment)](https://github.com/instaloader/instaloader/pull/174#issuecomment-577011167). Your assumption that they are at container-scope is wrong. [#174 (comment)](https://github.com/instaloader/instaloader/pull/174#issuecomment-577011167)...

> How you use library with vpn/proxie I use Instaloader as a module with proxy configured via environment variables. It should work if you use it as a command line,...

> This is because the URL is not a text file. To avoid that, I change the code a bit to process only when the response header `content-type` matches `/^text\//`,...