202937741 - Instagram Bridge failed with error 429
amanijoseph87 opened this issue · 13 comments
Error message: The requested resource cannot be found! Please make sure your input parameters are correct! cUrl error: (0) PHP error:
Query string: action=display&bridge=Instagram&context=Username&u=111111&media_type=all&direct_links=on&format=Atom
Duplicate of #1706
have the same issue
and
#1617 (comment)
does NOT help
Same, worked perfectly till yesterday, And I have been using the method mentioned by @rocky-III for months
Same here it was fine till yesterday
Yup, looks like many of my Instagram feeds are dead. It's probably a matter of time before all of them spit out error 429. Neither #1617 (comment) nor #1818 (comment) fix the problem for me.
Coincidentally or not, I also noticed that the Wayback Machine is no longer able to archive Instagram posts and profiles the same time the feed errors started appearing. Instead, all archival attempts automatically redirect to Instagram's login page.
So I guess something changed on Instagram's end?
Same here for the last few days.
Maybe this info can help with troubleshooting.
I use Heroku.com and when I noticed the Bridge 429 error yesterday I redeployed RSS-Bridge from the Master branch and it immediately started working again.
Again started noticing the Bridge 429 error in my RSS reader today, redeployed RSS-Bridge and it immediately started working again.
Update: Same 429 error again for the last 2 hours, instead of reinstalling I just restarted the RSS-Bridge instance(dyno?) and it is working again.
To me it start to working again today, i didn't change or do anything.
Same, it started working for me even though I changed nothing.
And the Wayback Machine is able to properly archive Instagram posts again. But not Instagram profiles, which still redirect to the login page when I attempt to archive them.
I spoke too soon. Several of my feeds just got error 429'd, while others are perfectly fine. There seems to be no rhyme or reason to this. I'm running Instagram Bridge on Heroku.
There's a problem again.
It seems that Instagram profiles are no longer publicly visible without logging in. This exact thing happened to Facebook two months ago (see #1745) and then fixed itself within a few days. I can only hope Instagram fixes itself as well.
It's not working again. This seems to go back and forth like a yo-yo.