this post was submitted on 04 Sep 2024
24 points (96.2% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

55064 readers
150 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 2 years ago
MODERATORS
 

Hi guys! It's been a long while, and I still struggle with Deluge catching brand new releases of movies that just about everyone's downloading.

A bit of background, I have 1Gbps connection, and Deluge in headless mode (that's why I chose Deluge, for headless you get either Deluge or Transmission...AFAIK those are the only two supporting it).

So, whenever my -arr servers catch the latest release of the very latest movie or TV show, Deluge catches it, and faceplants it with a download error immediately. I can either "force check" or "resume". Either way (doesn't matter which), it will error again in a second or two. This struggle continues for a while of resume/error/resume, until it finally starts to download a larger chunk...for it to error again a minute or two later, after downloading several hundred MB. And then another section of constant errors. Finally, it will get stuck at the end at 99%, where it really needs a "force check" to find whatever data was corrupted, redownload that, and finish.

Any idea why this happens? Any way to fix/avoid it? I'm not sure deluge is connecting to fake seeders giving it corrupted data and it fails to catch/fix it. Any help would be very welcome. Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] myersguy@lemmy.simpl.website 9 points 3 months ago* (last edited 3 months ago)

I know it's of very little help, but I have not seen this issue, and I've been using Deluge for years (not automated via the arr suite, however)

It would do you well to find out what error it is throwing (check logs). Would be much easier to diagnose if you knew the actual issue.