I’m spinning up a new seedbox and wanted to know what is everyone using nowadays? I was using deluge via the thick client and rutorrent previously. Are they still king? edit: I should have also mentioned that I plan on running this server headless so I will need to be able to access it via a thin client or a web browser

  • Hyacin (He/Him)
    link
    fedilink
    English
    42 hours ago

    transmission in docker container on NAS, with dedicated IP that gets forced through VPN on my router

  • Andromxda 🇺🇦🇵🇸🇹🇼
    link
    fedilink
    English
    98 hours ago

    qBittorrent is probably the most commonly used client. Transmission is another popular option, especially among macOS users, since it has a familiar design and feels more native.

    rTorrent is great if you want a CLI app, and ruTorrent offers a web frontend. Another option that you can run on a server is Deluge.

    You can control qBittorrent from Android using qBitController or from iOS using qBitControl (you can get it from AltStore after adding the Michael-128 repo). Transdroid supports other clients as well, and it’s my personal favorite. If you want to torrent on the Android device itself, check out LibreTorrent. For iOS, use iTorrent (also available on AltStore).

    If you already plan on self-hosting, or have root access on your seed box (or some other way of installing applications/deploying Docker containers), I also recommend setting up bitmagnet. It’s basically your own torrent indexer and search engine. It can also integrate with your *arr applications.

  • Brickfrog
    link
    fedilink
    English
    36 hours ago

    On a headless seedbox Deluge/ruTorrent/Transmission are still reliable, most of the paid seedbox services still default with those.

    qBittorrent is hugely popular on the desktop front and has been getting more popular as a headless client now that the web ui has improved, also look into qbittorrent-nox if you don’t have a gui to do initial setup with.

  • @TwiddleTwaddle@lemmy.blahaj.zone
    link
    fedilink
    English
    38 hours ago

    I used transmission for years, but the larger my library got the more issues I had. Currently using Qbit and loving the categories for easier management, especially with the *arr suite.

  • @howrar@lemmy.ca
    link
    fedilink
    English
    28 hours ago

    rTorrent with Flood front end.

    My only complaint so far is being unable to reach the rTorrent TUI when it’s running headless. It otherwise works great.

      • @SatyrSack@feddit.org
        link
        fedilink
        English
        22 hours ago

        Closed source, and their prominent “contains NO Spyware” disclaimer doesn’t quite instill confidence. I have also never even heard about it until now.

        • Brickfrog
          link
          fedilink
          English
          1
          edit-2
          1 hour ago

          I don’t use that client either - But to be fair the dev (Kevin Hearn) has a long history with P2P software e.g. depending how old you are you may have used his WinMX software back in the day. He isn’t known for sticking spyware/malware into his software so I sort of trust the software he puts out in that sense. He also maintains other non-torrent P2P file sharing software outside of Tixati.

          Of course it would be better if it was open source but he’s never been an open source coder AFAIK.

  • @myersguyA
    link
    English
    310 hours ago

    I’m a much bigger fan of the deluge thin client, personally.

    • EffortlessOpsOP
      link
      fedilink
      English
      19 hours ago

      This is what I used in the past but I had issues with the Deluge thin client when using a Deluge docker image. Did you experience the same thing as well?

      • @myersguyA
        link
        English
        17 hours ago

        Nope! My deluge server is hosted in a docker network with gluetun, and I access it from both thin clients and the web interface.

        • EffortlessOpsOP
          link
          fedilink
          English
          16 hours ago

          Mind me asking which docker image you are using? I was never able to get the thin client to work through docker