RipMeApp / ripme

Downloads albums in bulk
MIT License
3.67k stars 624 forks source link

Rule34.xxx cookies/site captcha #1980

Closed GhostlyFunBun closed 2 years ago

GhostlyFunBun commented 2 years ago

Ripme version: v1.7.95 Java version: <Version 8 Update 321 build 1.8.0_321-bo7> Operating system: <!-- (Windows Version 21H2 Build 19044.1645> Rule34.xxx

Expected Behavior

I normally use RipMeJar for bulk ripping rule_34 artist, its really my goto. Its worked perfectly even a couple of months ago (I think Early April late March?). I put the link in, files come out, simple. I should note I never needed to sign into this site either if that is useful information at all.

Actual Behavior

The issue I started having starting earlier today is the new Rule34.xx site update, adding a captcha before being able to access the site, Im not sure when this was added since the last time I ripped anything from there is was a few months ago. Now every time I try to rip anything from Rule34.xxx I get this error "Status Code 403. You might be able to circumvent this error by setting cookies for this domain". Im no genius with code, so I really dont know what is causing this, my best guess is the new captcha on the site.

I tried to set up the cookies for the site in the properties file but I just kept getting the same error, the code I was adding was "cookies.host = key1=val1; key2=val2" filling in all the appropriate data where needed. I don't know if Im just adding the cookie data wrong, if its the wrong data, or if Im just going at this wrong entirely so Im asking for help here.

Any help would be incredible, I was losing my mind spending hours trying to get around this captcha or whatever the issue is (whatever it is it affects downloadthemall too) so I would just like to have some closure at this point. Thanks in advance, Ill try to respond to any replies as fast as I can.

GhostlyFunBun commented 2 years ago

The issue has been solved, I feel really goofy for typing all this up now.

The captcha was the issue, and it was solved by playing around in my VPN settings, sorry for posting this :(