Skip to content
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

Closed
BOUSNI22 opened this issue Jan 1, 2021 · 6 comments
Closed

Instagram Bridge failed with error 429 solution #1917

BOUSNI22 opened this issue Jan 1, 2021 · 6 comments

Comments

@BOUSNI22
Copy link

BOUSNI22 commented Jan 1, 2021

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 ?

@kheiro2
Copy link

kheiro2 commented Jan 3, 2021

the same problem

@P6g9YHK6
Copy link

P6g9YHK6 commented Jan 4, 2021

same here on my own docker on my own IP.

@TwizzyDizzy
Copy link
Contributor

TwizzyDizzy commented Jan 4, 2021

and i can't understand it ! could someone of you help me ?

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
Thomas

@snipermaroc
Copy link

the same problem

@rpc31
Copy link

rpc31 commented Apr 15, 2021

same issue with my own docker under/behinde my own IP (only 3 instagram profiles followed)

@em92
Copy link
Contributor

em92 commented Apr 19, 2021

Closing as duplicate of #1891
Temporary solution if you have instagram account, #1891 (comment)
or use my instance https://feed.eugenemolotov.ru

@em92 em92 closed this as completed Apr 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants