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?
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+