Instagram QueryError about socialscan HOT 12 CLOSED

@butterflyx Are you still facing this issue? Normally it is caused by too many requests sent in a short period of time. Is that the case or does it occur even with a single query?

As for the proxy, yes I'm afraid only http proxies are supported at the comment. This is a limitation of aiohttp, the library I'm using for executing requests

from socialscan.

@butterflyx Are you still facing this issue? Normally it is caused by too many requests sent in a short period of time. Is that the case or does it occur even with a single query?

As for the proxy, yes I'm afraid only http proxies are supported at the comment. This is a limitation of aiohttp, the library I'm using for executing requests

This still happens, even with a single query and even if sending only one request. Could this be something to do with changes on Instagram side?

from socialscan.

@herecomesharis Instagram is still working well on my own computer and on Travis so it is difficult for me to troubleshoot this error. What region are you from? Maybe you are being served a different version of Instagram.

from socialscan.

@herecomesharis Instagram is still working well on my own computer and on Travis so it is difficult for me to troubleshoot this error. What region are you from? Maybe you are being served a different version of Instagram.

Hi! Sorry for my late reply, hope you will see this.
I'm from EU. To highlight the issue I pasted everything from my console so you can check it out - https://pastebin.com/1bi1Q9RY
Maybe I did something wrong?

Br

from socialscan.

@iojw : missed this notification as well, sorry!

Yes, this seems an error due to local restrictions of Instagram.
I'm in the EU as well and still get the same error.
Using a VPN to get an IP within the US solves this issue for me.

Maybe worth noticing.

from socialscan.

@butterflyx Oh I see, thanks for checking it out. I’d like to keep this issue open to fix this when I get time. In the meantime, you’ll might have to use to use a VPN to get around this @herecomesharis.

from socialscan.

@butterflyx @iojw
Thank you both for your assistance. Will try it out and hope it works.

from socialscan.

I'm facing the same issue, tried it on my few servers, (all in europe, and i'm also in caucuses), but it worked on one of my servers, which is in middle east.
thanks

from socialscan.

If one of you could run the latest version of socialscan (1.4.0) with the --debug flag and provide the output, it would make it easier to debug this problem.

from socialscan.

i installed it using pip, so i was on 1.3.0, upgraded it from github to 1.4.1, and it works here now.

from socialscan.

@manawenuz I didn't change anything about the code so look like something changed on Instagram's end that fixed it.

from socialscan.

Going to close this for now as it appears to be fixed, do let me know if this issue still occurs for Instagram by providing debug output.

from socialscan.