ripme icon indicating copy to clipboard operation
ripme copied to clipboard
verified publisher icon RipMeApp

e621 ripper broken

Open wingedtwins opened this issue 4 years ago • 3 comments

  • Ripme version: 1.7.95 (e621 Patch)
  • Java version: java version "1.8.0_291" Java(TM) SE Runtime Environment (build 1.8.0_291-b10) Java HotSpot(TM) Client VM (build 25.291-b10, mixed mode, sharing)
  • Operating system: Microsoft Windows [Version 10.0.19043.985]
  • Exact URL you were trying to rip when the problem occurred: https://e621.net/posts?tags=zaush

Expected Behavior

RipMe should be able to access and download the files normally through the auth cookie.

Actual Behavior

Since today, RipMe throws an error that is completely new to me and has never occurred before.

Logging in using auth cookie.
Rip complete, saved to A:\SSD\archive.de.com\rips\e621_zaush
Failed to load https://e621.net/posts?tags=zaush: Status Code 403. You might be able to circumvent this error by setting cookies for this domain

I hope that you can help me. Thanks in advance.

wingedtwins avatar May 26 '21 12:05 wingedtwins

I believe this is a result of e621's DDoS protection. I have gotten this error too, it fixes itself after about half an hour.

Did you go to e621.net while you were ripping on the same device? That's when it seems to occur. My guess is that it thinks you're DDoSing it because of sending multiple requests at once on the same device.

In short, it's not a problem with RipMe, and should go away.

EDIT: I did a little more looking, and yeah, it's to prevent DDoSing. e621 got DDoS'd recently, so they needed to take extra precautions.

jertpack avatar Jun 04 '21 13:06 jertpack

A suggestion would be then to disable the E621 test by default. Currently your standard build/test suite skips 10 tests - E621 tests should be one of those that're disabled by default and made optional tests for e621, especially if DDoS protection is as sensitive as it is.

teward avatar Jun 04 '21 21:06 teward

I believe this is a result of e621's DDoS protection. I have gotten this error too, it fixes itself after about half an hour.

Did you go to e621.net while you were ripping on the same device? That's when it seems to occur. My guess is that it thinks you're DDoSing it because of sending multiple requests at once on the same device.

In short, it's not a problem with RipMe, and should go away.

EDIT: I did a little more looking, and yeah, it's to prevent DDoSing. e621 got DDoS'd recently, so they needed to take extra precautions.

I have noticed that as well. It's just extremely annoying. It would be good if you can somehow get around that.

wingedtwins avatar Jun 05 '21 17:06 wingedtwins