Instagram discussion issue

eyoungmin commented 4 years ago

Please fix it.

stefansundin commented 4 years ago

It's not fixable. They are rate limiting much harder now. If everyone would just stop hammering my free service everyone would just have a better experience.

The only good fix is to host your own RSS Box. It's not that hard, give it a try.

eyoungmin commented 4 years ago

It's not fixable. They are rate limiting much harder now. If everyone would just stop hammering my free service everyone would just have a better experience.

The only good fix is to host your own RSS Box. It's not that hard, give it a try.

I'm hosting it myself. It has the same problem.

stefansundin commented 4 years ago

Try adding a sessionid as described here: https://github.com/stefansundin/rssbox/issues/21#issuecomment-525130553

Maybe I should just disable all requests without one.

eyoungmin commented 4 years ago

thanks!

meyerjom commented 4 years ago

Same problem here with my own heroku hosted env. Did not try the sessionid thing yet.

Ex-Ark commented 3 years ago

I'm also hosting it privately on a dedicated server and getting :

"There was a problem talking to Instagram. Please try again in a moment."

Reading instagram.rb I suspect it has nothing to do with the rate limit , as you have defined custom rate limit error, and this is not the error raised in the output (InstagramError vs InstagramRatelimitError)

Here's the actual instagram response in my case

2020-09-04 15:39:43 - InstagramError - 302: https://www.instagram.com/accounts/login/?next=/web/search/topsearch/%3F__a%3D1%26query%3

Is Instagram refusing all request to anonymous users now ? Why is it redirecting to login page ? To be clear I tried it with a public page URI, I have no problem while using a private browser with no cookie whatsoever

I haven't tried your solution with the sessionid because I think it's not "production ready " to put personal cookie into a public facing webapp. What if I don't want to create an Instagram account at all ?

PS: The log is truncated as defined in your http.rb:138 : truncate the message in order to cut down on log filesize

If you're interested in reducing the logfile you could look into "system level" solutions like logrotate, in order to keep the integrity of data instead.

patrickdrd commented 3 years ago

Try adding a sessionid as described here: #21 (comment)

I'm using sessionid but instagram is complaining about suspicious access the last week, I was forced to change my password 3 times in a week already! is rssbox the culprit? did anyone else have similar issues?

stefansundin commented 3 years ago

Is Instagram refusing all request to anonymous users now ? Why is it redirecting to login page ?

I don't know why they sometimes return 429 and sometimes a redirect to the login page. I suspect there may be two different rate limit protections, perhaps one to just get people to login on the application layer, and then another one at an infrastructure layer that based on IP address that returns 429. This is just a guess though.

I haven't tried your solution with the sessionid because I think it's not "production ready " to put personal cookie into a public facing webapp. What if I don't want to create an Instagram account at all ?

None of this is sanctioned by Instagram so don't ever expect the Instagram feature to be "production ready". lol. And use the sessionid hack at your own risk.

If you're interested in reducing the logfile you could look into "system level" solutions like logrotate, in order to keep the integrity of data instead.

Not possible on Heroku. That's what I optimize the app for by default. You can change things like log truncation on your own.

I'm using sessionid but instagram is complaining about suspicious access the last week, I was forced to change my password 3 times in a week already! is rssbox the culprit? did anyone else have similar issues?

Probably. Use at your own risk.

eyoungmin commented 3 years ago

IFTTT Activity Said:

Applet failed Feedjira::UserFacingFetchFailure

Show details: No details available.

muava12 commented 3 years ago

Any fix for this issue?

stefansundin commented 3 years ago

So I recently implemented some pretty good caching functionality, which has greatly stabilized RSS Box. The app is really responsive now and I am really happy with how well it has restored usability of the website. However, on its own it is not enough to make Instagram work well.

Currently you can only configure one "Instagram sessionid" by setting INSTAGRAM_SESSIONID. And if you configure it and do enough requests quickly enough then Instagram will say that they have detected "unusual activity" from your account and you will have to perform some manual steps to regain access.

Screen Shot 2021-01-14 at 13 15 53

Screen Shot 2021-01-14 at 13 16 10

I have not added a real phone number yet so I don't know if you can continue making requests afterwards. Please comment here with your experience if you try this. Right now rssbox.herokuapp.com is running with INSTAGRAM_SESSIONID unset.

If I could add code that tracks the number of requests that are being sent to Instagram, then we could try to find a request rate that is safe to use without locking out the account. Then I can add some code that allows a lot of session ids to be added (probably using redis?), and the application can "load balance" between the ids to avoid using one too much. It would take some time to implement though.

I would need help from volunteers to help me register a lot of accounts so we can have a collection of instagram session ids. I don't know how many ids we'd need, but the more the merrier. And it's not possible to sign up multiple accounts using email tricks such as using + at the end of the email, or multiple dots. But maybe there's a trick to work around this that someone knows about?

Anyway, we can continue using this issue to discuss the issue. Let's focus on trying to find a solution. (Any unhelpful comment saying "please fix" or similar will be removed.)