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!
Thanks…I don’t think think I have considered rTorrent before. But this one doesn’t have a remote GUI client the way deluge and transmission allow their UI to connect to a remote daemon, right?
Regarding all the troubleshooting steps, thanks a lot. I’m going to go about enabling logging by default on the service, which is disabled and definitely doesn’t help. I’m also considering to rebuild the whole thing, since it’s running off of an older Ubuntu 20.04 container. I might as well take the chance to do it on 24.04. We’ll see.
I don’t think think I have considered rTorrent before. But this one doesn’t have a remote GUI client the way deluge and transmission allow their UI to connect to a remote daemon, right?
Correct. You’re referring to the thin client, offhand I think it’s just Transmission and Deluge that have that. You don’t need a thin client for a headless torrent client setup, plenty of people do fine with a web ui. But I get it, if you prefer using a thin client then yeah Deluge or Transmission are your options for that.
re: Deluge once you have logging enabled it’ll be easier to troubleshoot things. Always seemed a bit odd that Deluge doesn’t at least enable error/warning logging by default but that’s a Deluge thing.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Thanks…I don’t think think I have considered rTorrent before. But this one doesn’t have a remote GUI client the way deluge and transmission allow their UI to connect to a remote daemon, right?
Regarding all the troubleshooting steps, thanks a lot. I’m going to go about enabling logging by default on the service, which is disabled and definitely doesn’t help. I’m also considering to rebuild the whole thing, since it’s running off of an older Ubuntu 20.04 container. I might as well take the chance to do it on 24.04. We’ll see.
Correct. You’re referring to the thin client, offhand I think it’s just Transmission and Deluge that have that. You don’t need a thin client for a headless torrent client setup, plenty of people do fine with a web ui. But I get it, if you prefer using a thin client then yeah Deluge or Transmission are your options for that.
re: Deluge once you have logging enabled it’ll be easier to troubleshoot things. Always seemed a bit odd that Deluge doesn’t at least enable error/warning logging by default but that’s a Deluge thing.