-
-
Notifications
You must be signed in to change notification settings - Fork 164
Stopped working #103
Comments
My IP is now banned, so I can't do a clear check. But yes, something has changed for me too. I will check later if this new IG behaviour is permanent or only for banned IPs. |
I'm getting the same issue too after a couple of page views Instagram isn't returning any images and in the console I get
|
I'm also seeing the temporary banned message |
@benbracedigital |
Yes I was and I could see the images on a different server this morning but after a couple of refreshes, I get the error message. I've set the |
It seems like 120min is not enough now. The new default and recommended value is 6 hours (360) |
Sure, happy to increase to 6 hours but I would expect it to be cached for 2 hours previously and still work rather than error and not show images within minutes? |
What version of the script do you have? I can see cached images even in the ban. |
version 1.3.6 |
Caching is only available since 2.0.0 |
Ah, thank you. I'll download the latest version and see what results I get. |
But only after the end of the ban. |
I can at least see cached images now. I'm going to deployed to a different (non banned) server to see if that all works. |
Your (browser) IP is banned, not the IP of the server of your page. Personally, I am currently banned on my PC, but I can flawlessly see the script results on my phone with mobile internet. |
Looks to be working. Thanks for your help |
I am finally able to check your issue after my last ban ended. The redirect to IG Login Page is only related to the ban. Now, I am able to open and preview any IG page with only offer to register at the bottom. |
Yeah, it looks like these are tough times. IG has banned me right after the first successful page update. And ban will last 2-3 days, I expect. |
@mahotilo how are you? Is to possible to avoid this issue by using cache_time setting? Thanks! |
The cache_time is the only cure we have, It works. But it is very easy to catch a ban if you simultaneously use the script on different sites and make experiments :) |
I'm kind of on an "eternal ban", because sometimes the feed appears and sometimes not, the same happens with this error, sometimes it appears on the console and sometimes it doesn't, I really don't know what to do anymore :( |
First of all, you should update your script to the latest version 2.0.1 |
Having the same issue, updated to ver 2.0.1 and console reads: Increased Any suggestions to proceed? |
Wait until IG unbans you. Last time, 3 days were enough for me. |
Well, what I have found about the ban from IG.
|
Maybe we should change it to use the same username on all the examples. The tag call doesn't matter because it never gets banned as far as I know |
I also think so.
Or maybe the function should be called only when the corresponding tab is opened? Barcelona should be kept:) |
Mmm, way better
Hahaha, for sure 😄 |
Just have a question for clarification, if i get banned on one page, will i be banned on all pages that use this script, or is the ban on a per page basis? or is it on a per instagram page basis? |
I believe, it is a ban on your IP. Any nonlogged-in requests from your IP are banned by IG during the ban period. |
@mahotilo I noticed this error only for some instagram accounts. Please try the next user name: Update: The error occur when instagram account doesn't have bio. |
This happens when Google responds with an error, because in this case it does not send the header "Access-Control-Allow-Origin" I think this solution is still crude and more logging needs to be added. |
I have checked, there is the same error here. |
This happens when parse_caption() dont finds a caption and returns false in escape_string where the string is expected. |
We should definitely have created a separate new issue for this :) |
Can you do it please? |
Please, let us continue to discuss this error here #120 |
@m0nclous this is because you are running the script without a web server. The solution is setting the 'Referer' header but web browsers won't allow us to do that with Javascript for security reasons |
@thomashdk, I can only quote for you
|
@thomashdk, can you see the script output for the demo page https://www.sowecms.com/demos/jquery.instagramFeed/index.html? |
|
@thomashdk |
@mahotilo i'm getting the images but also all the errors.. Weird.. |
Not exactly. Some of these errors are caused by fair try to load data directly from IG in case they will change their minds. |
@thomashdk, to get rid of such errors in the console, follow this recommendation. |
Hi @mahotilo hmm have already tried with that.. |
Are you using the script with TAG? |
i'm using Username |
@mahotilo If I change the username to "Instragram" I get their feed. If I changed it to my own "thomas___dk" then it dont.. |
Hmm.
|
You don't have the hostname specified? Arh you using this ? |
Yep. But it is not a problem.
I am using version 3.0.3. |
Suddenly instagram feed down ! |
same error in demo and my website https://www.tiktiddies.com/ it's not a problem of IP banned but a problem of "Access to XMLHttpRequest at 'https://www.instagram.com/XXXXXXX/' from origin 'https://www.tiktiddies.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource." |
What is the solution ? |
I think IG changed the policy. Now to see a user page, you have to be logged in. So when you run the script, the GET returns the IG Login Page content.
The text was updated successfully, but these errors were encountered: