How to auto download with *arr?
How to auto download with *arr?
Update: it was an issue with API keys due to a previous install.
Update 2: new problem, qBittorrent has an I/O issue, probably involving the final destination for the media: my Synology NAS. Any advice here is appreciated.
Update 3: I was having issues with mapping my Synology NAS as the root folders, so I restarted the *arrs and now they are unreachable. The solution was to reinstall them without uninstalling them because my computer is weird.
Once a year I try setting up Prowlarr, Sonarr, and Radarr and I felt confident so I reinstalled them. The *arrs are connected to qBittorrent (all tests succeeded) and Prowlarr (again, tests succeeded) and vice versa. I added every indexer that I could successfully connect to (which was most of them) and currently have all of the web UIs open <IP address>:<port> which work as expected. Everything seems to be communicating and functioning as intended so I tested Radarr. I found a popular movie and started monitoring it, this was about 30 minutes ago. It hasn't shown up in qBittorrent and I'm not sure what I'm missing; can someone help me troubleshoot? In other words, how do I know definitively that this movie I have selected will download and when will it download?
You're viewing part of a thread.
Are you running Jellyfin on the NAS as well as the arrr stack?
Also which Synology NAS do you have exactly and as someone else asked, what client / box are you using to access it with?
I've got a couple of Synology boxes and only run Radarr/Sonarr/Transmission on them and that's it - Jellyfin is on another SFF PC and I've also been thinking of taking Transmission out of the Syn boxes since it nails them on large & multiple downloads.
My VPN is a mullvad exit node via TailScale which isn't supported by Synology unfortunately. So Jellyfin on the NAS, and arr + qBittorrent on my windows computer. The problem was in having the mid-download folder on the NAS, causing so many small writes to the NAS that it would shut down the connection. I moved the download folder to a spare HDD on my PC and havent had issues with the setup since. From what I've gathered though, this is a really inefficient setup
Maybe try it the other way like I've done?
Put the arrr stack + qbit on your Syn drive, mount the shares via NFS, and then use Jellyfin on your Windows PC?
edit: or, like you're saying you're wanting qbit behind your Mullvad put that on your Windows PC and tell Sonarr/Radarr that's where the Download Client is
Is there a benefit to having the arrs on the NAS if it's still going to have to communicate and download through the other machine anyway?
That's what I've been curious about, but even still on a DSM 223 & 418 I've found them alright to an extent running Radarr/Sonarr/Transmission.
I did however run into problems trying to use them via Container Manager aka Docker on the DSM's.
Jellyfin thou is definitely best run on something that can transcode media and the DSM's are definitely not cut out for that, and if your Windows PC has an Intel processor will see you having less issues. Good luck you ;)
So I originally had the Jellyfin running on a Win10 with GPU transcoding, but now I'm running it on a DS923+ in a docker image, and it's had surprisingly far better performance. And thank you!
Just had a nosey, that DSM 923 (Vs 423) doesn't have a discreet GPU.
What rules are you putting on your downloads from the arrr's, and do you find some struggle to transcode w/ Jellyfin?
I've had to lower the rules since it got silly trying to transcode 80GB+ files over the puny specs of the DSMs > N100 SFF box I'm testing with, and use them solely for NAS / arrrrrs. I still need to invest a little more I think :/
I followed the trash guide for the 1080p profile for TV shows and 4k for movies, haven't had any transcode issues...yet. If I have any issues though, I'm fully prepared to buy more hardware for the DS923+