| Post Reply | RetroFed Forums Forum Index » Selfhosted |
| Author | Message | ||
|---|---|---|---|
marighost
piefed.social
marighost@piefed.socialJoined: 2025-06-05 |
Edit: Solved! Thanks a ton non_burglar. Good day selfhost gang! I'm redoing my media stack and I've come across a conundrum that I can't solve on my own. I've got Docker containers on the same Debian machine for qbittorrent, sonarr, and radarr for automatic media downloading. The problem is, as you may have guessed from the title, I need to implement remote path mapping in sonarr/radarr because qbittorrent downloads to a different location than where my media files are hosted. My media is hosted on a network share, mounted at
All three applications work mostly as expected (radarr can grab a release from an indexer, throws it into qbittorrent to download), but it does not move media into the Obviously, I get the error in both sonarr and radarr that tells me: Here is how my remote path mapping looks in the settings of sonarr/radarr:
I was messing around with radarr initially, and also tried appending Thanks for reading, happy to dig into my configs or setup more if necessary. |
||
| 21 Original | |||
|
non_burglar
lemmy.world
non_burglar@lemmy.world Joined: 2023-06-16 |
1st thing to check is permissions, I have seen radarr/sonarr complain about the path "not existing", but actually the download client process had no write permission to the destination. From the radarr wiki:
Since radarr >4.x, there hasn't been a need for remote path between Linux machines, not sure about sonarr, but they are similar. Now for your case, your qbittorrent host does not know about /srv/ in its path, it only knows about /data and everything under it:
So when radarr tells
qbittorrent, which lives inside its docker world, has no idea what /srv means. |
||
| 5 | |||
marighost
piefed.social
marighost@piefed.socialJoined: 2025-06-05 |
1st thing to check is permissions, I have seen radarr/sonarr complain about the path "not existing", but actually the download client process had no write permission to the destination. From the radarr wiki: Generally, a remote path map is only required if your download client is on Linux when *Arr is on Windows or vice versa. A remote path map is also possibly needed if mixing Docker and Nativ...
Thanks for the reply. I believe I have permissions set correctly, as qbit was the first thing I set up and had to fiddle with permissions under the I understood "remote path mapping" to also include filesystems on other machines, even if it's a LAN connection. Maybe that's true? because I simple changed the Remote Path mapping in radarr from I knew it had to be simple. Thank you, and I hope you have a great week! |
||
| 2 | |||
|
non_burglar
lemmy.world
non_burglar@lemmy.world Joined: 2023-06-16 |
Thanks for the reply. I believe I have permissions set correctly, as qbit was the first thing I set up and had to fiddle with permissions under the /srv/data/torrents folder to test if downloads worked. I understood "remote path mapping" to also include filesystems on other machines, even if it's a LAN connection. Maybe that's true? because I simple changed the Remote Path mapping in radarr fro...
No worries, and I'm glad it helped! I'll add that I was also mystified by the remote path option for a long time, I think the wiki should show more clearly what this does and maybe an example. Also, I used to run into issues of running into permissions errors because the download client wrote the files with the wrong permissions. Many nzb and torrent clients have a POSIX masking option that allows you to set the permissions at the time of writing. |
||
| 2 | |||
|
plantsmakemehappy
lemmy.zip
plantsmakemehappy@lemmy.zip Joined: 2025-12-04 |
Thanks for the reply. I believe I have permissions set correctly, as qbit was the first thing I set up and had to fiddle with permissions under the /srv/data/torrents folder to test if downloads worked. I understood "remote path mapping" to also include filesystems on other machines, even if it's a LAN connection. Maybe that's true? because I simple changed the Remote Path mapping in radarr fro...
You said radarr, sonarr, and qbit are all on docker on the same host, right? The correct fix is to remove the remote path mapping and fix the volumes for the arrs to be Your path for |
||
| 1 | |||
| Post Reply |
Back to top |