Topic: Instagram feed not found error

2GirlsTrippin
(@2girlstrippin)

4 years, 7 months ago

The widget was working great from the start – until today. Now I get the error:

“Sorry: – Instagram feed not found.”

A sample of this can be found at http://www.2GirlsTrippin.com. Thanks in advanced for any suggestions.

https://wordpress.org/plugins/alpine-photo-tile-for-instagram/

Viewing 15 replies - 16 through 30 (of 41 total)

← 1 2 3 →

Plugin Author theAlpinePress
(@thealpinepress)

4 years, 7 months ago

Thanks for letting me know. I assume you are using a shared server and perhaps another user got the entire server block (just an unfounded idea, but might explain why it stopped working). Regardless, I’m sorry the plugin, and ever other Instagram plugin, is not working for you.
Best, Eric

wildcatjrotcbooster
(@wildcatjrotcbooster)

4 years, 7 months ago

The host checked everything out and claims that it is a problem with instagram. Says that instagram blocks for having too many requests. It’s odd because it worked at first. They suggested that as I tested it multiple times for different displays that instagram then blocks after multiple requests. The host also sent me links to articles on stackoverflow.

I’m developing a tool for checking the integrity of links in a web page.

I’ve noticed that various Instagram URLs will return a HTTP 500 response in cases where if one were to visit the given URL in a browser one would get a HTTP 200 response accompanied by the expected resource.

This is when requesting regular Instagram URLs as one would do as a browser user and not when using the REST API.

A typical request/response using cURL:

curl -v http://instagram.com/p/YKTkxHBA-P/
* About to connect() to instagram.com port 80 (#0)
* Trying 54.225.159.246… connected
> GET /p/YKTkxHBA-P/ HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: instagram.com
> Accept: */*
>
< HTTP/1.1 500 Server Error
< Cache-Control: no-cache
< Content-Type: text/html
< Date: Tue, 15 Oct 2013 08:31:09 GMT
< Server: nginx
< Content-Length: 87
< Connection: keep-alive
<
<html><body><h1>500 Server Error</h1>
An internal server error occured.
</body></html>
* Connection #0 to host instagram.com left intact
* Closing connection #0
I did for some time get HTTP 200 responses in such cases but am now consistently getting HTTP 500 responses.

This is all specific to a given host; such URLs, even when sending requests with cURL, will return HTTP 200 responses from other machines.

Due to this being specific to the host sending the requests I suspect a form of rate limiting or request filtering by IP is going on, however I can find no documentation to the effect.

Will Instagram officially return a HTTP 500 response as above due to a given IP being denied access?

instagram internal-server-error
share|improve this question
asked Oct 15 ’13 at 8:42

Jon Cram
5,64253767

I’m having the same problem. Is it what you (we) are supposing? Aka when your IP gets “banned” you get 500s? – kitsched Nov 6 ’13 at 7:02
3
@kitsched Yes, I’m assuming that a banned IP gets HTTP 500 responses. That’s the only conclusion I can come to with the information I have available to me. I admit the information I have may well be incomplete. – Jon Cram Nov 7 ’13 at 12:28

Same here, about the suppositions, I mean. I submitted a request / question to them, asking for my IP to be unbanned. I’m curious if anything will happen. Thanks for your answer. – kitsched Nov 7 ’13 at 16:11

@JonCram Same problem here. Did you find the real reason of this error? I can reproduce this error on individual server. All API requests work fine on other servers. It looks like a ban from Instagram, but they didn’t notify about the ban. And sometimes I’m able to make successful request to Instagram API, but it works very rarely… – Michael M. Kalygin Mar 19 at 16:47

I am now suddenly getting this also. It appears it may be an error on Instagram’s side now. I find it odd that it works in my web browser but not on my server though. Using the same URL. – Francis Pelland Mar 19 at 19:34
show 7 more comments
2 Answers
activeoldestvotes
up vote
-2
down vote
I’m almost 100% sure this happens because the domain/IP address is blocked from the Instagram API.

Reason:

Works to get the JSON in the browser. Doesn’t work to get with cURL from webservice.
I copied my exact application from my primary domain (were the application doesn’t work) to another domain. Same application worked.
The strange thing is that you get a “500 Internal Error” back and not a message “Your IP is blocked”.

share|improve this answer
answered Mar 27 at 16:35

Kim
268114
1
But how to explain that sometimes the request is working from the same ip and sometimes not. Moreover, what is the exact criteria for banning?? :-/ – ivicaa Mar 29 at 16:10
add comment

up vote
-2
down vote
This is an IP rate limit. If you want to skip the part where you contact Instagram and wait for the monkey crew they have working over there to fix the problem, simply assign 1000 IPs to your server and loop through them randomly for your requests. You won’t see anymore 500’s.

Cheers.

share|improve this answer
answered Mar 31 at 22:04

user3482950
11

Lots of people start getting these 500’s when you’re testing API integration. Because you’re most likely requesting the same Instagram page data over and over again during testing, Instagram thinks its a bot and promotes the IP address, this is where you start to see 1/10th of your requests being accepted. I stand behind my given answer, it is the easiest way around this issue, as their API is a pile of sh*t with no real support that is ready and willing to help you. – user3482950 Apr 3 at 19:38
add comment

wildcatjrotcbooster
(@wildcatjrotcbooster)

4 years, 7 months ago

Thought I posted the link but dont see it

Plugin Author theAlpinePress
(@thealpinepress)

4 years, 7 months ago

It sounds like the server your website is hosted on has been blocked from Instagram. I test the plugin frequently and so I would be surprised if you got yourself blocked by just changing around the settings. Seems more likely that another user on your server is responsible. But who really knows?
Thank you for passing along the stackoverflow link. It does not look like anyone else was able to come up with a solution though.

nightowl99
(@nightowl99)

4 years, 7 months ago

I am having the same problem again. Worked fine for a while and now stopped, but only on my sites which are hosted on Namecheap. This also affects other Instagram plugins. Sites on other hosts are still fine with no problems.

Hopefully we can find out how to resolve the issue. Thank you, Eric, for hanging in there with us!

2GirlsTrippin
(@2girlstrippin)

4 years, 7 months ago

Me again. It appears that I’m getting that error again.

“Sorry: – Instagram feed not found.”

Any suggestions are greatly appreciated. 🙂

Thanks!

moonlissa
(@moonlissa)

4 years, 7 months ago

Hey there,

I’m receiving the same error message. “Sorry – Instagram feed not found.”

The widget was working well up until the past few days.

Looking forward to any suggestions as well.

Thank you! 🙂

John
(@jpmizell)

4 years, 7 months ago

Not working for me either.

shoshanna
(@shoshanna)

4 years, 7 months ago

Ours stopped working a few days ago, too.

Current PHP version of your server: 5.4.27
Check: curl_init function found.
Check: Plugin failed to connect to Instagram.com.
Code: 500, Message: Internal Server Error.
Check: json_decode function found.
Check: Sample JSON successfully decoded and parsed.

shoshanna
(@shoshanna)

4 years, 7 months ago

Just in case this is useful information, I had the client try to connect with another plugin (Simple Instagram) and he’s unable to authorize the app he set up for that plugin. I’m seeing lots of StackOverflow discussions on various Instagram problems from the last week or so.

Plugin Author theAlpinePress
(@thealpinepress)

4 years, 7 months ago

Hello everyone,

Can someone please delete and reinstall the plugin and then send the output from the Plugin Loading Test on the Plugin Tools page? I have edited the code to simply display more information.

I don’t know if this is relevant to anyone, but Instagram does have an access limit: “You are limited to 5000 requests per hour per access_token or client_id overall.” However, this does not sound like what people are experiencing. Plus, with the plugin’s cache, this should never be a problem.

My best guess is that Instagram has begun blocking the IP addresses of certain servers. With shared hosting services, the activities of one user can sometimes get the entire server blocked. Again, I have no way of verifying that this is the case, but if Instagram is running just fine and you are seeing a 500 error, it means that you are being blocked from accessing Instagram’s servers.

I will continue to search StackOverflow and try to contact Instagram (who never seem to respond). I will let you know if I identify a problem/solution.

Best, Eric
nightowl99
(@nightowl99)

4 years, 7 months ago
This is what I get:
```
Load from the Instagram feed

P0, UTC:23:29:41.3768, Start plugin.
P1, UTC:23:29:41.3783, Enqueue styles and scripts
P2, UTC:23:29:41.3786, Retrieve Photos
P3, UTC:23:29:41.3789, Check cache
P4, UTC:23:29:41.3829, Using get_transient()...
P5, UTC:23:29:41.3845, No cache found
P6, UTC:23:29:41.3845, Check for access_token
P7, UTC:23:29:41.3847, Try accessing Instagram feed
P8, UTC:23:29:41.3848, Use wp_remote_get() (cURL) to make request
P9, UTC:23:29:50.4697, Request complete
P10, UTC:23:29:50.4698, An error occured.
P11, UTC:23:29:50.4698, Code: 500
P12, UTC:23:29:50.4699, Message: Internal Server Error
P13, UTC:23:29:50.4699, Try request again using Alpine's cURL function
P14, UTC:23:29:59.6023, Request complete
P15, UTC:23:29:59.6024, An error occured.
P16, UTC:23:29:59.6024, Code: 500
P17, UTC:23:29:59.6026, Content Received: <html><body><h1>500 Server Error</h1> An internal server error occured. </body></html>
P18, UTC:23:29:59.6026, Failed using wp_remote_get()
P19, UTC:23:29:59.6026, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
P20, UTC:23:29:59.6028, Check Results
P21, UTC:23:29:59.6029, Print Message
P22, UTC:23:29:59.6029, Loading complete
Output

Sorry:

- Instagram feed not found.
Load from cache

P0, UTC:23:29:59.6036, Start plugin.
P1, UTC:23:29:59.6052, Enqueue styles and scripts
P2, UTC:23:29:59.6055, Retrieve Photos
P3, UTC:23:29:59.6059, Check cache
P4, UTC:23:29:59.6060, Using get_transient()...
P5, UTC:23:29:59.6077, No cache found
P6, UTC:23:29:59.6077, Check for access_token
P7, UTC:23:29:59.6079, Try accessing Instagram feed
P8, UTC:23:29:59.6080, Use wp_remote_get() (cURL) to make request
P9, UTC:23:30:8.7053, Request complete
P10, UTC:23:30:8.7054, An error occured.
P11, UTC:23:30:8.7054, Code: 500
P12, UTC:23:30:8.7054, Message: Internal Server Error
P13, UTC:23:30:8.7054, Try request again using Alpine's cURL function
P14, UTC:23:30:17.7950, Request complete
P15, UTC:23:30:17.7950, An error occured.
P16, UTC:23:30:17.7950, Code: 500
P17, UTC:23:30:17.7952, Content Received: <html><body><h1>500 Server Error</h1> An internal server error occured. </body></html>
P18, UTC:23:30:17.7952, Failed using wp_remote_get()
P19, UTC:23:30:17.7952, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
P20, UTC:23:30:17.7954, Check Results
P21, UTC:23:30:17.7954, Print Message
P22, UTC:23:30:17.7955, Loading complete
Output

Sorry:

- Instagram feed not found.
```
I should probably also mention that this particular page gets hardly more that 10 – 20 hits per day.
cissi.wong
(@cissiwonggmailcom)

4 years, 7 months ago

Hi there!

I also have this problem… I just updated to WP 3.9 and with that Instagram stopped working. I’m getting this error:

“P0, UTC:6:57:36.7212, Start plugin.
P1, UTC:6:57:36.7227, Enqueue styles and scripts
P2, UTC:6:57:36.7228, Retrieve Photos
P3, UTC:6:57:36.7231, Check cache
P4, UTC:6:57:36.7246, Check for access_token
P5, UTC:6:57:36.7248, Try accessing Instagram feed
P6, UTC:6:57:36.7248, Use wp_remote_get() (cURL) to make request
P7, UTC:6:57:37.1853, Request complete
P8, UTC:6:57:37.1853, An error occured.
P9, UTC:6:57:37.1853, Code: 400
P10, UTC:6:57:37.1854, Message: Bad Request
P11, UTC:6:57:37.1854, Try request again using Alpine’s cURL function
P12, UTC:6:57:37.6381, Request complete
P13, UTC:6:57:37.6381, An error occured.
P14, UTC:6:57:37.6381, Code: 400
P15, UTC:6:57:37.6382, Content Received: {“meta”:{“error_type”:”APINotAllowedError”,”code”:400,”error_message”:”you cannot view this resource”}}
P16, UTC:6:57:37.6382, Failed using wp_remote_get()
P17, UTC:6:57:37.6382, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
P18, UTC:6:57:37.6383, Check Results
P19, UTC:6:57:37.6383, Print Message
P20, UTC:6:57:37.6383, Loading complete
Output

Sorry:

– Instagram feed not found.”

The site in question is http://www.beyoga.se/, however I have the same plugin up and running on http://www.sanghayoga.se/about/ without problem (although I have not yet updated WP on that site).
Any ideas out there?

charlesspot
(@charlesspot)

4 years, 6 months ago

I similarly updated to WP 3.9 and am now getting the same error message above.

Load from the Instagram feed

P0, UTC:17:3:29.9028, Start plugin.
P1, UTC:17:3:29.9040, Enqueue styles and scripts
P2, UTC:17:3:29.9042, Retrieve Photos
P3, UTC:17:3:29.9044, Check cache
P4, UTC:17:3:29.9053, Using get_transient()…
P5, UTC:17:3:29.9063, No cache found
P6, UTC:17:3:29.9063, Check for access_token
P7, UTC:17:3:29.9064, Try accessing Instagram feed
P8, UTC:17:3:29.9064, Use wp_remote_get() (cURL) to make request
P9, UTC:17:3:30.0347, Request complete
P10, UTC:17:3:30.0347, An error occured.
P11, UTC:17:3:30.0348, Code: 400
P12, UTC:17:3:30.0348, Message: Bad Request
P13, UTC:17:3:30.0348, Try request again using Alpine’s cURL function
P14, UTC:17:3:30.1422, Request complete
P15, UTC:17:3:30.1423, An error occured.
P16, UTC:17:3:30.1423, Code: 400
P17, UTC:17:3:30.1424, Content Received: {“meta”:{“error_type”:”APINotAllowedError”,”code”:400,”error_message”:”you cannot view this resource”}}
P18, UTC:17:3:30.1424, Failed using wp_remote_get()
P19, UTC:17:3:30.1424, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
P20, UTC:17:3:30.1425, Check Results
P21, UTC:17:3:30.1425, Print Message
P22, UTC:17:3:30.1425, Loading complete
Output

Sorry:

– Instagram feed not found.
Load from cache

P0, UTC:17:3:30.1430, Start plugin.
P1, UTC:17:3:30.1440, Enqueue styles and scripts
P2, UTC:17:3:30.1442, Retrieve Photos
P3, UTC:17:3:30.1444, Check cache
P4, UTC:17:3:30.1445, Using get_transient()…
P5, UTC:17:3:30.1448, No cache found
P6, UTC:17:3:30.1449, Check for access_token
P7, UTC:17:3:30.1450, Try accessing Instagram feed
P8, UTC:17:3:30.1450, Use wp_remote_get() (cURL) to make request
P9, UTC:17:3:30.2561, Request complete
P10, UTC:17:3:30.2561, An error occured.
P11, UTC:17:3:30.2561, Code: 400
P12, UTC:17:3:30.2561, Message: Bad Request
P13, UTC:17:3:30.2561, Try request again using Alpine’s cURL function
P14, UTC:17:3:30.3622, Request complete
P15, UTC:17:3:30.3623, An error occured.
P16, UTC:17:3:30.3623, Code: 400
P17, UTC:17:3:30.3624, Content Received: {“meta”:{“error_type”:”APINotAllowedError”,”code”:400,”error_message”:”you cannot view this resource”}}
P18, UTC:17:3:30.3624, Failed using wp_remote_get()
P19, UTC:17:3:30.3624, Check your Instagram feed. If the feed is empty, then the problem is with Instagram. If you see a full page of text, then the problem is with the Alpine plugin or your web server.
P20, UTC:17:3:30.3626, Check Results
P21, UTC:17:3:30.3626, Print Message
P22, UTC:17:3:30.3626, Loading complete
Output

Sorry:

– Instagram feed not found.

jen.coy@att.net
(@jencoyattnet)

4 years, 6 months ago

Eric- I noticed my Instagram widget wasn’t working before I updated to WordPress 3.9. It’s been working great for months up to now. Instead of showing the awesome photos from Instagram on my blog it says “Sorry. Instagram Feed Not Found”. All widgets are updated.

You can see the problem here: http://jennifermccoy.net.

I’m not remotely technically-inclined so I would appreciate very detailed instructions/questions which can be as condescending as you like. I can take it! I’m anxious to send an email campaign to promote my blog but don’t want to send it if this plugin isn’t working. I hope to hear from you soon!

Indebted, Jennifer