So I’ve got jellyfin all set up, but I’m having some issues with files downloading from qbittorrent and Knowing exactly how and when they get moved over, either the sonar or jellyfin repository, whichever is the final destination. This is important because my torrenting drive is separate from my media drive. I have noticed some shows and files staying on my torrenting drive while others go over to the media drive. And I’m and to figure out where the issue might be that’s causing this, I think I need a refresher on exactly how and when these files are supposed to be moved over. Since I can’t find any sort of documentation inside the apps.

Can anybody explain this to me like super simply? I just took an edible and it’s starting to kick in, but I still want to figure this out. Thanks y’all!

  • Evkob (they/them)@lemmy.ca
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    9 months ago

    I just took an edible and it’s starting to kick in, but I still want to figure this out.

    Getting stoned and getting the magic rocks in my homelab to do my bidding is one of my favourite ways to use up my time on this Earth.

  • CapitalNumbers@lemm.ee
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    I’ve literally just set this all up and it’s working now after some tinkering, so here’s what I found out. Assuming you have correctly configured the sonarr/qbitorrent api keys and credentials:

    When you make a TV show request in Sonarr, it will automatically add the torrent to your download client (e.g qbitorrent)

    qbitorrent will then download the file to wherever you specify (e.g. /torrents/completed)

    periodically, Sonarr will scan that /torrents/completed folder, and if it finds the tagged TV show, it will either copy or hard link that video file to your specified media folder (e.g. /media/tv-shows)

    JellyFin will do the same, periodically scanning your media folders to see if there are any updates

    EDIT: also if you are using docker containers, make sure that Sonars native /downloads folder is pointed at the same external folder your qBitTorrent is downloading files in

    • pezhore@infosec.pub
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      Also of note - if you’re using docker (and Linux), make sure the user is/group id match across everything to eliminate any permissions issues.

    • doodledup@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      1
      ·
      9 months ago

      I’m also trying to figure out a setup using Docker. What’s the recommended way of connecting the container to a VPN? Ideally I want to bind the qbittorrent container to a VPN while the rest of the machine is not connected to the VPN.

  • Evotech@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    9 months ago

    Sonarr gets torrents and sends to qbittorrent, qbittorrent downloads the torrent and puts the downloaded file somewhere, sonarr then picks up that file and moves it to its final destination where jellyfin expects it

    It’s important to have seperate directories for unfinished torrent downloads and complete ones, and only have sonarr pick up from the completed one

    • ipkpjersi@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      It’s important to have seperate directories for unfinished torrent downloads and complete ones, and only have sonarr pick up from the completed one

      Back when I used Torrents instead of Usenet for sonarr, I had only the one folder, since Plex would generally pick up the library changes automatically anyway. I’d assume that Jellyfin is similar, although I don’t use it enough to know for sure. These days I use only Usenet for sonarr/radarr since I’m paying for Usenet and it’s excellent for automation/new content, and SABnzbd provides both incomplete and complete folders by default anyway.