Comment on [Help] Radarr/Sonarr Remote Path Mapping Good day selfhost gang!

non_burglar@lemmy.world ⁨1⁩ ⁨day⁩ ago

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 Native clients or if using a remote server.

Since radarr >4.x, there hasn’t been a need for remote path 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:

    volumes:  
      - /home/marighost/docker/seedbox/gluetunconfig:/gluetun  
      - /home/marighost/docker/seedbox/qbittorrentconfig:/config  
      - /srv/data/torrents:/data/torrents```

So when radarr tells
```Host: qbittorrent  
Remote Path: /srv/data/torrents/  
Local Path: /data/  ```

qbittorrent, which lives inside its docker world, has no idea what /srv means.

original
Sort:hotnewtop