DeviantArt could be deploying a defence mechanism right now

[rautamiekka]

• Ripme version: 1.7.84
• Java version:

java version "1.8.0_211"
Java(TM) SE Runtime Environment (build 1.8.0_211-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.211-b12, mixed mode)

• Operating system: Window$ 10.0.17134.706 Enterprise x64

• Exact URL you were trying to rip when the problem occurred: https://www.deviantart.com/malte279/gallery/?catpath=/
• Please include any additional information about how to reproduce the problem: -

Expected Behavior

Rips normally.

Actual Behavior

Errors out as "No full-size image found for <page URL>". Recently within a week's time RipMe has been consistently expressing strange inability to continue ripping DA after successfully working for a while first.

Take the link given in the template for example: https://gist.github.com/rautamiekka/4a0d947069fc6eb1f23406d5a3989208

At first, it works fine for a time. Then, no matter how many times I abort and restart, it's just reporting no image found although the page works just fine, and the folder-specific log (.\rips\deviantart_malte279_gallery_all) gives good hope in terms of functional links and detection: https://gist.github.com/rautamiekka/3ca0998f09785711e9f3f8fd240ce753

Here's the .\ripme.log: https://gist.github.com/rautamiekka/0e3eea98940072114c8a5e8732b4cd2b

Thus, I'm starting to think DA is deploying a defence mechanism when using RipMe, whatever that mechanism is. I suggest dumping each page RipMe fetches.

[rautamiekka]

18 minutes later it worked fine:

RipMe output: https://gist.github.com/rautamiekka/81cf27bb659d8f13979ff10b9add3b98

.\rips\deviantart_malte279_gallery_all\log.txt: https://gist.github.com/rautamiekka/2479864b742d0ece3c5c18f3e81fc8fe

.\ripme.log:

2019-06-06 00:14:45,190 DEBUG ripper.DownloadThreadPool .initialize() Initializing deviantart thread pool with 1 threads
2019-06-06 00:14:45,191 DEBUG ripper.AbstractRipper .getRipper() Found album ripper: com.rarchives.ripme.ripper.rippers.DeviantartRipper
2019-06-06 00:14:45,924 DEBUG ripper.DownloadThreadPool .initialize() Initializing deviantart thread pool with 1 threads
2019-06-06 00:14:45,924 DEBUG ripper.AbstractRipper .getRipper() Found album ripper: com.rarchives.ripme.ripper.rippers.DeviantartRipper
2019-06-06 00:14:45,925 INFO  ripper.AbstractRipper .getGID() Album Name: malte279_gallery_all
2019-06-06 00:14:45,925 DEBUG ripper.AbstractRipper .setWorkingDir() Using album title 'deviantart_malte279_gallery_all'
2019-06-06 00:14:45,925 DEBUG ripper.AbstractRipper .setWorkingDir() Set working directory to: D:\_DOWNLOADS_\RipMe\rips\deviantart_malte279_gallery_all
2019-06-06 00:53:17,442 INFO  ripper.DownloadFileThread .run() [+] Saved https://api-da.wixmp.com/_api/download/file?downloadToken=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ1cm46YXBwOjdlMGQxODg5ODIyNjQzNzNhNWYwZDQxNWVhMGQyNmUwIiwiaXNzIjoidXJuOmFwcDo3ZTBkMTg4OTgyMjY0MzczYTVmMGQ0MTVlYTBkMjZlMCIsImV4cCI6MTU1OTc3MjE5MiwiaWF0IjoxNTU5NzcxNTgyLCJqdGkiOiI1Y2Y4MzljODMxMGRmIiwib2JqIjpudWxsLCJhdWQiOlsidXJuOnNlcnZpY2U6ZmlsZS5kb3dubG9hZCJdLCJwYXlsb2FkIjp7InBhdGgiOiJcL2ZcLzc2Njk0OTk2LTk2OWMtNGZmNy05ZDZmLWZkM2NlMTMzODNkY1wvZGE0MnRrMC1jNjkwOGFmNS01NGU4LTRhOGEtYjIwZS1iZTdlZTQ0MjU5YTIuanBnIiwiYXR0YWNobWVudCI6eyJmaWxlbmFtZSI6InNvYXBzdG9uZV9wcmluY2Vzc19sdW5hX2J5X21hbHRlMjc5X2RhNDJ0azAuanBnIn19fQ.7izvee7ok1eOFAte_rwATeF7a2LPM0XzC8X0RrWy-tY as .\rips\deviantart_malte279_gallery_all\soapstone_princess_luna.jpg

[Berni8k]

Ripping deviant art using different tool a few months ago i came across a defense mechanism that sounds like this.

Large amounts of activity seamed to trigger it, once triggered the web page would load normally, yet the CDN server that hosts the actual image file would not respond at all. Images hosted on other CDN servers seamed to still load. The cooldown period for it seamed to be over a day, but just changing my IP address got it working again. So my solution was to slow down the ripper tool and hop to a different IP if tripped.

[metaprime]

[Mega-Thread] DeviantArt ripper is broken; yes we know -- de-duping all other DeviantArt issues to this one. #2063