Feed doesnt load

Question

Feed doesnt load

Closed this issue 3 years ago · 19 comments

Hi!
thx for this wonderful skript! it worked super nice and fine till today! could it be possible that instagram changed something? It doesn't fetch the post by username... i tried the index.html from the package... just the content example 'by tag' works...

i hope you can help me!
thank you very much
manu

Answer 1 · 2021-01-08T08:15:22.000Z

Hi me too,
Since yesterday, Instagram doesn't work live like that anymore : https://www.instagram.com/xxxxx/, it redirects to https://www.instagram.com/accounts/login/?next=/xxxxx/.
Basically, i think, Instagram doesn't make any more public page.

Knowing that the script uses the public url... hoping that the devs can find an alternative.
It's a big problem for me too.
I try to find an alternative.

Answer 2 · 2021-01-08T08:29:44.000Z

I do not clearly understand your problem because there is no such problem on my side.
Can you provide more information?

Does the script demo work for you?
Have you tried to adjust host parameter of script?

host
String [url]
https://www.instagram.com/
URL where to fetch the data. Useful if instagram changes CORS policy

Are you participating in any "new/next interface" program of IG? For me, your link with .com/accounts/login/?next=/xxxxx/ is redirected to .com/xxxxx/.

Answer 3 · 2021-01-08T12:23:56.000Z

Well, now I can see the same problem.
Despite the new caching approach, I am still able to catch "It looks like YOUR network has been temporary banned" error.

Is 120 min not enough? I will be able to check only in 24 hours:)

But, I still can see the cached IG response. That is good.

Answer 4 · 2021-01-08T16:41:55.000Z

We have also found that this Instagram feed has stopped working, as of today. Will keep an eye on this thread for updates. Fingers crossed for a solution.

Answer 5 · 2021-01-08T17:30:29.000Z

also for me the same error: InstagramFeed.min.js.xhtml?ln=public/js:1 Instagram Feed: It looks like YOUR network has been temporary banned because of too many requests. wait for update. thank you

Answer 6 · 2021-01-08T18:33:14.000Z

The same error is happening to me, this message appears on the console

Answer 7 · 2021-01-08T19:15:57.000Z

pabrul commented 3 years ago

Answer 8 · 2021-01-08T19:19:15.000Z

I get the same error as pabrul.

Answer 9 · 2021-01-11T08:58:27.000Z

@pabrul Same here

Answer 10 · 2021-01-11T09:02:00.000Z

Well, I have just checked. I am unbanned now after more than 48 h. So, we need to increase the caching period. Maybe to 3-6 h.

UPD
I was wrong when I was suggesting 1 h. It looks like IG changes its mind about the allowable frequency of ajax get() depending on the site load.

Answer 11 · 2021-01-11T17:21:37.000Z

The error continues, it remains very unstable for me

Answer 12 · 2021-01-11T17:51:40.000Z

@pabrul
Are you using the latest version 2.0.0?

UPD
It should also be borne in mind that using private mode prevents the cache from being saved and leads to a ban.

Answer 13 · 2021-01-12T07:01:04.000Z

@pabrul
The script takes IG data from the cache (localStorage) if this error is catched. The cache will be updated after temp ban.
If you don't see images, then you didn't have cached data before the temporary ban.
This could be if you are viewing the page in incognito or another browser.

Answer 14 · 2021-01-12T13:07:42.000Z

I dont think the cache fixes the problem. If i look at the examples page only the one where it goes by tags work. The others dont.
So this is an issue with instagram redirecting all requests if you are not logged in and most likely has nothing to do with them banning you for 24h.

Answer 15 · 2021-01-12T13:24:08.000Z

Well, I have just caught a ban again right after looking at the example page.
Today during 6 hours, I have already done 3 reloads of my test page with the script in private/incognito mode (no cache). So the question is, do we have a request rate limit (request per hour) or a max reloads per day (24 h) limit (no mater how frequently)?

And my previous ban lasted more than 24 h. It seems to me, it took at least 48 h.

UPD
And yes, the ban does not affect the TAG.

UPD2
We should take into account, that the current caching logic prevents too frequent access to one 'username' but not to several. At the same time, IG bans us based only on our IP, not on the IP+username.

Answer 16 · 2021-01-12T13:53:21.000Z

@Remling97

So this is an issue with instagram redirecting all requests if you are not logged in and most likely has nothing to do with them banning you for 24h.

When I am not in a ban, the script works perfectly for me regardless of whether I am logged in or not.

Answer 17 · 2021-01-12T14:19:18.000Z

Well, I have just checked. I am unbanned now after more than 48 h. So, we need to increase the caching period. Maybe to 3-6 h.

UPD
I was wrong when I was suggesting 1 h. It looks like IG changes its mind about the allowable frequency of ajax get() depending on the site load.

We will set the default cache_time to 6 hours. Either way, you guys can change that option as you wish.

Answer 18 · 2021-01-18T17:49:40.000Z

@jsanahuja how are you? Did it worked changing the cache_time to 6 hours?

Answer 19 · 2021-01-18T19:01:22.000Z

I am not being banned but it always depends on the use each one gives to this library. Each use case has different requirements so if 6 hours is not enough (or too much) simply change as you need