-
Notifications
You must be signed in to change notification settings - Fork 1k
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instagram Bridge failed with error 429 solution #1917
Comments
the same problem |
same here on my own docker on my own IP. |
Then let me explain again: the problem with the instagram bridge does currently not seem to be rooted in the bridge itself. The problem seems to be, that Instagram itself delivers different code (or to put it more general "behaves differently"), when your rss-bridge does its request from IP ranges that Instagram has determined to be "hosting" ranges.. IP ranges for server providers as Hetzner for example. I'd categorize that as an anti-spam measure by Instagram. So the thing I tried was (as indicated by others in the original thread) setting up an additional Instagram Bridge behind my home IP address (dial up addresses don't seem to be affected) and the bridge works behind that IP address. Cheers |
the same problem |
same issue with my own docker under/behinde my own IP (only 3 instagram profiles followed) |
Closing as duplicate of #1891 |
Please any Solution , my small business has stopped due to this error
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=9gag&media_type=multiple&direct_links=on&format=Html
This guy @TwizzyDizzy found the solution which is : ' Solved this for myself by setting up a second instance of rss-bridge behind my dial-up IP address. So in my feedreader, for InstagramBridges I use the second instance behind this IP. It works, as obviously dial up IPs haven't been blocked. '
and i can't understand it ! could someone of you help me ?
The text was updated successfully, but these errors were encountered: