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!

  • CapitalNumbers@lemm.eeEnglish
    9·
    3 days 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.pubEnglish
      4·
      3 days 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.worldEnglish
      2·
      3 days 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.

      • CapitalNumbers@lemm.eeEnglish
        3·
        3 days ago

        literally was going through the exact same thoughts as you a couple a weeks ago, tried so many different configurations but the one i found that worked was actually kinda simple

        basically they way i did was to run a gluetun docker container, and then in the environment variables pass in the the fact i wanted this to use the WireGuard VPN manager, and then i passed in my Proton VPN wireguard api key (you’ll need a subscription for this)

        then once that gluetun container is up and running, you literally just add “network_mode: service:gluetun” to any other containers that you want to use this VPN

        can you can even test its working by sending a curl command to an ip checking site from within those containers connected to gluetun

        and then also try shutting down that gluetun vpn, and see if you other services (e.g. qbitorrent, still work)