strike

Yeah sonarr/radarr should be moving the files provided you have set up your volume mappings correct and deluge/sab is moving the completed files to the correct folder. if you have both sonarr and radarr you probably have at least 2 labels set up in deluge? Post your docker run command for radarr,sonarr,deluge and sab and the download and label settings in deluge, same for sab. For all of the apps to work together they all should share the same volume mappings and settings. If not, you get issues like the one you're having.

Then radarr is probably not using ssl either. Just check the radarr log if it's connecting to deluge over https or http. If it really connecting over https, then yeah it's really weird that it's working when deluge has ssl unchecked. If it's connecting over http its either a bug in radarr or maybe you remembered wrong and it does not have use ssl enabled.

Are you sure you've set up ssl in deluge? If not, that's the reason it's not working when you have enabled use ssl in sonarr.

Disable "use ssl" and it should work

According to you log it complains about a unknown label. Maybe you have set the wrong label in sonarr? Have you set up deluge to move the completed downloads to the correct folder? I assume you have at least 2 labels in deluge? What are your labels called? Post your deluge settings and the docker run command for both deluge and sonarr

I use emby, not plex, but the principle is the same: https://forums.unraid.net/topic/44679-support-binhex-emby/page/7/?tab=comments#comment-779966 Right now you have set the /trancode directory in plex, but that dir isn't mapped to anything outside the container. I don't know why you have set the /tmp as a variable in the container template, it should be a path. See my example in the link.

Glad you got it sorted

Yup, it should work now. So fingers crossed 2 volume mapping to the same share might have confused both sonarr and sab. I've never seen that before so would have been interesting to see complete logs to see what was actually going on.

Technically no, as long as you have a incomplete folder it should be fine to put the completed in the parent folder.

Well, technically you did have your downloads share mapped in 2 places. And technically they were mapped to the same share so if it's /data or /downloads shouldn't matter the files end up in the same place anyway. And now you have removed /Downloads so now the sab shouldn't know about that mapping. But are you saying the files are still in /Downloads if you open up the terminal window in the container and check there? If so just move them to /data. At least there isn't any errors in you log which is a good sign. And yeah try with a new download.

Do you have files in the complete folder ready to be moved? If it's not moving anything now check the sonarr logs, it will tell you what's wrong. Not the container logs, but system->logs in sonarr.

both /data and /Downloads point to your download share that's why you were able to find the downloads in the correct place. Edit: I see you sab container setting also have your downloads share mapped 2 times, please remove /downloads there too.

You have also mapped your download share 2 times in sonarr, please remove the /download mapping in the sonarr container settings

No, you are wrong, That's why sonarr is unable to find the downloads. Yes sab might have the /downloads folder, but that doesn't mean it's correct, Please read the 2 last pages again.

But I thought you changed the settings in sab after the comment from @binhex? But you haven't, please read his post again. You settings is wrong, remember the /downloads location doesn't map to anything on the host side.

The container does not know anything about your shares unless you map them to a location in the container. So if you want access to anything in you shares you first need to map it to a directory in the container. Say you want access to you tv folder, on the host side you set your tv folder path, and on the container side you need to "mount" that folder to a directory we can call /media as an example. So the container does not know anything at all about your files on your server unless you map them to a directory in the container. I know it's all confusing at the start, but we've all been there So your tv folder share would then be /media in the container

Can you post new screenshots of the settings in sonarr and sab too (not the container settings), now that you have changed to the correct location. I want specifically to see anything that refers to a path you have set which should match your volume mappings. And anything that mention moving/copying files. I don't use sab or sonarr myself, but I use radarr which is very much like sonarr. But sab is the downloader right? So it should move the files to the complete folder when it's complete. And sonarr then should have a setting where it can find the complete downloads. Been ages since I set up my radarr container though, so I may need to check it to confirm.

Ok, yes the docker.img file will stay the size you set on disk. Normally 10-20 GB is more than enough. BUT if you don't set your mappings correctly with the app everything you download will end up in the docker.img file. The file it self will not grow over what you have set so if it fills up because of incorrect mappings all your containers will stop working.

I don't use sonarr, but post a screenshot of your sonarr settings. Specifically the part where you set up the moving/copying to the tv folder

I was referring to the incomplete files and what will happen if you don't have your volume mappings set up correctly with the settings in the app. Your docker image file is probably around 10-20 GB if you have not set it anything larger. And if you don't set your mappings correctly it will fill up inside the image file and the container will stop working.

Yes, move them to the correct location. Anything you download to that directory in the screenshot will end up in the docker image file, and you will run out of space. Also please remove that last screenshot, don't show what you're downloading unless it's completely legal.

Yes, you need to manually add it, like this: https://forums.unraid.net/topic/44679-support-binhex-emby/?do=findComment&comment=779966

From your log: This means it's unable to authenticate with the username/password you have set. Reasons for this can be: 1. User/pw is wrong or contains special characters which can be problematic 2. Your subscription isn't active. 3. You're over the device limit. Normally you can use 1-x devices on 1 subscription and anything over that fails to authenticate. Check what the limit is for you provider

Then we need to look at some logs, follow these steps: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

https://github.com/binhex/documentation/blob/master/docker/guides/vpn.md