Instagram\Exception\InstagramAuthException Unknown error, please report it with a GitHub issue. Client error: `POST https://www.instagram.com/accounts/login/ajax/` resulted in a `429 -` response: {"message": "", "spam": true, "status": "fail"}

[rahul7yadav]

Hi @pgrimaud , I used your instagram feed code and it's working on my localhost and I uploaded my code on server and after 12 hours it's suddenly stop working and showing error like: Instagram\Exception\InstagramAuthException Unknown error, please report it with a GitHub issue. Client error:POST https://www.instagram.com/accounts/login/ajax/resulted in a429 -response: {"message": "", "spam": true, "status": "fail"} Please take look and let me know how to fix it .

Thanks!!

[volkv]

I can confirm such behavior. Probably caused by Instagram protocol recent updates

[ollea]

Tried with 3 different accounts and got the same issue

[rahul7yadav]

I think Instagram block my server IP for next 24 hours after this error gone automatically .

[pgrimaud]

Hello @rahul7yadav, @volkv, @ollea

Sorry for the delay. Do you share an account with temp blocked account ? Because I can't reproduce it.

You can DM me : https://twitter.com/pgrimaud_

Thanks

[ollea]

Hello, thanks for your response. It's now solved, actually the hosting server was considered as spam by Instagram as they received too much queries and were returning HTTP 429 - too many requests. We had to wait a few days before they reconsider the hosting server as ham again.

[ollea]

Actually the problem came back:

Unknown error, please report it with a GitHub issue. Client error: `POST https://www.instagram.com/accounts/login/ajax/` resulted in a `429 -` response:
{"message":"","spam":true,"status":"fail"}

This website is on a shared server, so other clients use the same IP to get different Instagram accounts medias, have you any idea to solve this? Thanks in advance

[brimacbain]

Also having the same issue- I've implemented caching, grabbing new items from the feed every 60 minutes only. Doing some testing now and seeing what the changes here are!

[ghost]

Hello. Is there a solution to this problem? Is there a script that can change the IP?

[dwainscheeren]

Got the same issue here on a fresh DO server.

[fiction13]

Also having the same issue.

[shawnsquire]

It definitely seems linked to Instagram blocking whole sections of known servers, likely entire IP blocks. A fresh run on my local computer loads fine, but the first run on Digital Ocean results in a permanent 429. It seems like the way around it is to proxy through an IP not included in a prohibited list, like how restyler/instagram-php-scraper uses RapidAPI.

[ranaharoon]

I got the same problem, The most preferably script seems to be working locally just. This is tested if you send few requests fastly like pagination using endCursor then your ISP IP gets banned or restricted, restarting router works again. I've tested with 3 different Hosting accounts, once i uploaded to shared server it showed problem because instagram considered it a suspicious login attempt which requires security code on mobile or email. then i used another instagram login account for live after login into my browser then executed script on shared hosting. it worked only for few requests. This time it was 429. So my all 3 different hosting IPs got restricted while i used sleep(2) before any endCursor requests. There should be a proper solution for it.

[karrarjasim]

Same problem here!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[dwainscheeren]

Please re-open still not fixed.

[livevasiliy]

Have same error launch on Heroku server, on localhost, not errors.

[volkv]

Instagram is blocking bot-suspicious IPs from login. Any ideas how to bypass this?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[andressavw]

Also having the same issue.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[harshshah8996]

Also facing same issue. Is there any update or how to fix it?