-
Notifications
You must be signed in to change notification settings - Fork 38
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 "Error:null" #32
Comments
Log file : log.txt |
thank you! did not see the "getCallerClass is not supported" up to now as i had java8set. with java11 i got it as well, now fxed with #33. why for you it is "error null" i wonder as well. is it a language thing or pop linux java? i tried with
on the first try, with java8, your link worked. subsequent tries did not work. switching the java version did not help. deleting the "save" directory did not help. delete ~/cconfig/ripme directory did not help. i am wondering if i overlooked where ripme stores information - as it worked one time and other time not. or instagram behaves different if one gets content again. did you see such behaviour? in case you as well get a different error now, please change the title of the ticket. |
@iProdigy you fixed that once in RipMeApp#1722 - you v got any ideas? |
Negative. I did not experience that behavior, tried it on my Arch machine and results were identical, could it be related with how Instagram behaves to different user-agents ? I noticed that with a user-agent switcher extension enabled to "Windows / Chrome 87" on my Firefox and Brave Browser, Instagram would sometimes redirect to instagram.com/accounts/login, after clearing cookies and disabling the extension let's me see the page again, granted i could not get this behavior to work 100% of the time so it might just be Instagram being weird. |
@RockyBukake i debugged it briefly and it went into json ripper where the images were there, but the parsing of it is broken. i am not sure when it goes one of the 2 code paths. |
same error for me every time RipMe v1.7.94 in Kali and in Win10 [Java 8.281] |
Same issue, unless I use an instagram session ID. I did get locked out of my instagram a few days ago, and I think it might be related. May want to implement a rate limiter for instagram as well. |
This issue seems to be happening on DeviantArt as well. It did work on Furaffinity though. I'm wondering if there's some kind of firewall installed on these sites that make it harder to rip them? |
@terminalwhoami here they write that before 5000 / hr were accepted, and now 200 / hr: |
Are you still having issues with this? |
@Tush-r I haven't tried without a session ID lately, also don't rip instagram that much. trying to be cautious so they don't ban my account. |
Even without hitting the rate limit i still get these errors |
tried https://github.com/ripmeapp2/ripme/actions/runs/844309842 |
Anyone fixed it? |
Using latest green build. Still getting null.. |
same |
Any Solution? |
you wish |
have you tried with an instagram session ID? |
@soloturn did you ever get around to finding a solution for this? i remember you saying you tried to track it down, but couldn't figure it out. If i don't use a session ID, i get null. if i use one, i can rip a post. This is on windows. |
interesting, @terminalwhoami , you do it like so: RipMeApp#1380 ? |
Expected Behavior
It downloads Instagram posts
Actual Behavior
Ripme displays :
when ran from terminal the output for release 1.7.94 is :
tested with multiple newer releases output is similar :
The text was updated successfully, but these errors were encountered: