Вопрос

In a recent days we experience constant failure on API requestrs

$ curl -v https://api.instagram.com/v1/users/111111/?access_token=123234234.sdjsdjhsdfh1

<html><body><h1>500 Server Error</h1>
  An internal server error occured.
</body></html>

The same request made from other network versus the same IP api.instagram.com (forced by hosts) produces OK response always. As the token is the same that is linked to our client_id I suppose we're not Banned/Abused by someone

$ curl -v https://api.instagram.com/v1/users/111111/?access_token=123234234.sdjsdjhsdfh1

{"meta":{"code":200},"data":{"username":".....

It look like Instagram put the limit to access from Hetzner network their API? Does anybody experience the same troubles? Any help please!!

Это было полезно?

Решение

Instagram had confirmed the issue with API. The resolution will come up.

Here the recent blog post about the issue

http://developers.instagram.com/post/82701625883/api-returning-500-errors-on-specific-ip

Follow up (15/04/2014 17:30 GMT+1): We've been asked by Instagram to send our servers IPs

Follow up (15/04/2014 19:30 GMT+1): Issue is solved. The API reponding within a 500ms

Другие советы

We are having the same issue with API failures at buzzdeck.com, using the Instagram API to collect metrics on user accounts. We're requesting users recent media by page (getting approx 33 items per response even though you can request up to 250), and some page requests work, and some fail - usually the same ones that are failing.

In concordance with what you have seen the issue appears to affect some IP addresses but not others, since some of our servers have been unaffected. We have verified that we're not coming close to API rate limits, and that the Instagram Client app used to make the request makes no difference. We have raised the issue twice with developer support but have had no response from Instagram. Very frustrating!

[EDIT - 15/04/14] Issues have now been resolved by Instagram support, if you're still having trouble it's worth contacting them with the specific IP addresses from which you're making requests

We are running an Instagram API based website on Hetzner since 2011 and experienced this issue once before, solved by contacting Instagram Dev Help center.

Currently having same CURL error with HTTP 500 response. Already contacted again, about a week ago, and said that they are investigating the issue.

Still digging for the solution, and wish to know what causes it.

Possible reasons:

  • Two many requests in a short period of time.
  • You are limited to 5000 requests per hour per access_token or client_id overall. Practically, this means you should (when possible) authenticate users so that limits are well outside the reach of a given user.
Лицензировано под: CC-BY-SA с атрибуция
Не связан с StackOverflow
scroll top