It was definetly DNS
this post was submitted on 12 Jul 2024
872 points (97.9% liked)
me_irl
4678 readers
23 users here now
All posts need to have the same title: me_irl it is allowed to use an emoji instead of the underscore _
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Full arr stack makes life much easier. Only time I got that look was when it pulls a .rar that didn't automatically extract. Wrote a script that transmission runs on completion and they extract when finished now.
I've had a bunch of issues that totally belong on the right side of this graph. Broke the nginx proxy trying to add a rule for a game server and can't access the arrs anymore. Subscribed to a list that had too much crap on and it downloaded everything and filled up my drives. Buggered up permissions somehow so sonarr can download the files but I have to extract it manually with ssh
How do you extract them? I have some nzbs that stop halfway through extraction and I have no idea why
It was permissions for me, I think I bodged it with a chmod 777
Meh. Try other clients like rtorrent. As I remember transmission is not most healthy for swarm client. Or maybe it's my memory is shit.
Two of my private trackers have client and version requirements and transmission 3.0 was the only one on both if I use a VPN. It's the Debian of torrent clients.
I think Transmission is a very competent client. However, when I last used it a few years back, as soon as you reach 1800+ seeded torrents it really struggles. I switched to rTorrent but experienced similar issues at around 2500+ torrents. After hours of tinkering (which rTorrent / ruTorrent does have a lot to tinker!) and not getting anywhere, I made the switch to qBittorrent which is still happily chugging along seeding 4500+ torrents.