It was definetly DNS

  • lemming741@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    ·
    4 months ago

    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.

    • GiveOver@feddit.uk
      link
      fedilink
      arrow-up
      3
      ·
      4 months ago

      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

    • uis
      link
      fedilink
      arrow-up
      1
      ·
      4 months ago

      transmission

      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.

      • lemming741@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 months ago

        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.

        • sephallen@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          4 months ago

          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.