Hi selfhosted, I made a short tutorial for anyone who might want to dive into arr selfhosted software but dont know where to start. I did it on my RPI but docker config will work in any docker friendly environment so adjust it to your scenerio. I will gladly discuss that topic so fell free to talk.

  • nobug-404@geddit.social
    link
    fedilink
    English
    arrow-up
    12
    ·
    1 year ago

    You could make a container for the VPN and have the torrents route through that. Instead of having the whole system go through the VPN. You can then also make the VPN a dependency of the torrent container to prevent it from leaking torrent traffic out of your standard internet connection.

    • finestnothing@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      Gluetun is the answer! Just setup the gluetun container, then for the other containers do network_mode: “container:gluetun”, and it’ll route all of it’s traffic through gluetun

    • omalaul@lemm.ee
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      How would one do that if they had basic Linux knowledge but have not really touched docker? Asking for a friend and for his educational purposes only :)

    • Wojciech Plackowski@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Sure, but im using this setup only for downloading so it doesnt really matter to me. Everything works fine so i stoped tinkering at some point and i just let it work.

      • rambos@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        OP be careful nobug warned you that your home IP can maybe leak if something happens like VPN disconnect or server crapping out. Btw if you are using torrents you are not only downloading, you are also uploading and sharing the content.

        I checked the guide, and its a shame you didnt make it before I was building my arr setup. Thx for sharing

      • some_guy@kbin.social
        link
        fedilink
        arrow-up
        1
        arrow-down
        8
        ·
        1 year ago

        if you’re going to share it as a noob-friendly package, maybe don’t be such a prick about making it noob-friendly

  • slug@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    nice little guide, i’m surprised your pi can run the media servers though without being really slow. i’d also suggest using an alternate webui for qbittorrent if you’re only interacting with it through the webui. i like https://github.com/WDaan/VueTorrent