I was told this community might be able to help me…I’ve spent my entire day setting up sonarr/radarr on my Synology DS423+ NAS within docker. I got most of it figured out on my own but I’m stumped on how sonarr/radarr takes the files from my torrent client downloads folder and moves them to my media folder for plex/jellyfin to view.
This should just be part of configuring Sonarr/Radarr settings correctly. Do you have a red message in the settings that says a download client is missing, or have you filled out the download clients settings section with your torrent client info? If yes, have you checked the “auto import from client” box? and, have you set your root library folder in the media management section?
This. I remember being amazed that it just handled it.
The only catch I remember running into is that Sonarr must be aware of all storage locations. That is, if I didn’t see the path in Sonarr’s system info, the auto copy and rename didn’t work right.
Yes, I have a message in radarr that states “You are using docker; download client qbittorrent places downloads in /downloads but this directory does not appear to exist inside the container. Review your remote path mappings and container volume settings.” I’m confused because I mapped /data to /data in my docker settings so it should be able to see the downloads folder, no?
I do also have the auto import from client box checked and I do have my /data/media/movies folder selected under the media management section.
That’s helpful; this sounds like a docker issue or qBit issue then. The default qBit location for torrents is /downloads, but you’d need to make sure to point it towards the container volume mapping you’re setting up in docker.
my relevant qBittorrent compose volume mapping is as follows:
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: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
This should just be part of configuring Sonarr/Radarr settings correctly. Do you have a red message in the settings that says a download client is missing, or have you filled out the download clients settings section with your torrent client info? If yes, have you checked the “auto import from client” box? and, have you set your root library folder in the media management section?
This. I remember being amazed that it just handled it.
The only catch I remember running into is that Sonarr must be aware of all storage locations. That is, if I didn’t see the path in Sonarr’s system info, the auto copy and rename didn’t work right.
Yes, I have a message in radarr that states “You are using docker; download client qbittorrent places downloads in /downloads but this directory does not appear to exist inside the container. Review your remote path mappings and container volume settings.” I’m confused because I mapped /data to /data in my docker settings so it should be able to see the downloads folder, no?
I do also have the auto import from client box checked and I do have my /data/media/movies folder selected under the media management section.
That’s helpful; this sounds like a docker issue or qBit issue then. The default qBit location for torrents is /downloads, but you’d need to make sure to point it towards the container volume mapping you’re setting up in docker.
my relevant qBittorrent compose volume mapping is as follows:
Personally, I don’t separate my torrent downloads by type; I use incoming & completed folders. Here’s how I set up my qBittorrent config: