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?
The *arrs automatically check for availability every 15 minutes or so. If the movie is monitored, it should have started a download already. Did you check if Prowlarr’s indexers also show up in Radarr’s indexer tab?
Did you try manually searching for the movie (interactive search)?
When starting an automatic search in Radarr (Search movie), in the bottom left of the sidebar should be a progress indicator. Does it say that releases were found or that a report was sent?
Ok, I’m learning and thank you! Let’s start with the first question…the Indexer sections of Radarr and Sonarr have nothing in them (this wasn’t mentioned in the tutorial I was following), how do I add Prowlarr to them?
You need to add your *arr apps to Prowlarr. Add them in the tab “Apps” and use “Full Sync” as the sync level. If everything works, Prowlarr should add all indexers to the apps after a short while.
That part is fixed at least. Long story short, I made a mistake with API keys. The indexers are showing up in Radarr and Sonarr now, thank you again for that.
It showed up in qBittorrent, so the connections are good. Unfortunately, the download speeds are about 400 B/s despite the indexers. Any tips there would be nice.
Do you mean that the automatically grabbed torrent is slow in qBittorrent? The apps themselves don’t have any idea what is a popular or unpopular torrent, so it may have just grabbed an almost dead one.
You may want to check out TRaSH Guides for some good Custom formats and guides for the *arr apps.
Based on your previous posts I assume that you use Windows as your server OS. I am sadly unable to help you with OS-level issues on Windows. I am also unfamiliar with the quirks of the Synology OS.
You can check if your *arr-apps run as the same user as the permissions on the share (on the *arr-server). The folder and contained files of the share on the Synology NAS should have read, write and execute (rwx) permissions for the user of the share.
Gotcha, thank you for your help. In case anyone else is curious…after some testing, I think the problem is Synology shutting down all connections when too many things (downloading + scanning/tagging + moving to Jellyfin) are happening at once
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
The *arrs automatically check for availability every 15 minutes or so. If the movie is monitored, it should have started a download already. Did you check if Prowlarr’s indexers also show up in Radarr’s indexer tab?
Did you try manually searching for the movie (interactive search)?
When starting an automatic search in Radarr (Search movie), in the bottom left of the sidebar should be a progress indicator. Does it say that releases were found or that a report was sent?
Ok, I’m learning and thank you! Let’s start with the first question…the Indexer sections of Radarr and Sonarr have nothing in them (this wasn’t mentioned in the tutorial I was following), how do I add Prowlarr to them?
You need to add your *arr apps to Prowlarr. Add them in the tab “Apps” and use “Full Sync” as the sync level. If everything works, Prowlarr should add all indexers to the apps after a short while.
That part is fixed at least. Long story short, I made a mistake with API keys. The indexers are showing up in Radarr and Sonarr now, thank you again for that.
It showed up in qBittorrent, so the connections are good. Unfortunately, the download speeds are about 400 B/s despite the indexers. Any tips there would be nice.
Do you mean that the automatically grabbed torrent is slow in qBittorrent? The apps themselves don’t have any idea what is a popular or unpopular torrent, so it may have just grabbed an almost dead one.
You may want to check out TRaSH Guides for some good Custom formats and guides for the *arr apps.
Radarr Custom Format Tutorial
Radarr high-quality release groups
Sonarr Custom Format Tutorial
Sonarr high-quality release groups
I recommend finding some good release groups and setting them to be always preferred over others.
They are able to pull seed/leech info, but I’ve found that info to be inaccurate.
deleted by creator
I made a few updates with new issues. I’d love some advice if you have any
Based on your previous posts I assume that you use Windows as your server OS. I am sadly unable to help you with OS-level issues on Windows. I am also unfamiliar with the quirks of the Synology OS.
You can check if your *arr-apps run as the same user as the permissions on the share (on the *arr-server). The folder and contained files of the share on the Synology NAS should have read, write and execute (rwx) permissions for the user of the share.
Gotcha, thank you for your help. In case anyone else is curious…after some testing, I think the problem is Synology shutting down all connections when too many things (downloading + scanning/tagging + moving to Jellyfin) are happening at once
I appreciate the help!