this post was submitted on 27 Nov 2023
2 points (100.0% liked)

Self-Hosted Main

504 readers
1 users here now

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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
 

So, i've been struggling with this for few days, i have Ubuntu server with docker & portainer installed and radarr, qBittorrent are installed in portainer

This is my radarr docker compose within portainer
https://imgur.com/hBh2XU9

And this is qBittorrent docker compose within portainer
https://imgur.com/a/QfAKtss

these are the only docker-compose files that worked with me

inside radarr i created remote path mapping
https://imgur.com/Fz8dlh6

qBittorrent is downloading the files I choose from radarr without any problem
https://imgur.com/Ou31i4S

However there are two problems:

1: radarr it's stuck on this error
https://imgur.com/eDzsTPP
and in events it's telling me this error
Import failed, path does not exist or is not accessible by Radarr: /download/Bao (2018) [BluRay] [1080p] [YTS.AM]. Ensure the path exists and the user running Radarr has the correct permissions to access this file/folder

2: in the original path /mnt/data-500-g/downloads which is mounted on both apps in /download
there are no files downloaded?! i mean it's empty, shouldn't it at least have the downloaded files from qBittorrent?

the whole path /mnt/data-500g have permissions of 777 so i don't think it's permission issue
so what it could be 🤦‍♂️🤦‍♂️🤦‍♂️🤦‍♂️🤦‍♂️

you are viewing a single comment's thread
view the rest of the comments
[–] zachfive87@alien.top 1 points 11 months ago

I think its because you've used the same download location for both radarr and qbit. Looking at the trash guide here,docker guide, if you look at the compose example you'll notice that the download client, sabnzb in the example, has a separate download folder than radarrs. Fixing this should mean that you can also remove the remote path mapping, which in its current state has the same location for remote and local path, which conflicts with the practice described in this guide. But I think you shouldn't need remote path mapping if you follow the docker guides folder layout.