#Sonarr and sabnzbd download#

I f I try to change that internal directory, I can't climb up out of the config folder to get to it. If I set a downloads folder outside of the config file, and mount sabnznd to that, it still wants to set downloads in that internal directory. The only way I've been able to get it to work is to set the config directory the same for both apps. Thanks for the tips.When tinkering with it this morning, I left the external access alone and can confirm that the API key worked just fine for me without changing any of those settings.Īt this point, I'm sure it's either something I'm doing wrong or something that I've mangled in the Ubuntu install, because it's apparently working for everyone else. home/kd/storage/media/downloads:/Downloads It might be as simple as capitalizing that D in downloads. So my current thought is that I need to run another download, take not of the folders Sabnzbd is using to store the incomplete & complete download, in relation to the /config directory, and make sure that the storage volume I created to share between the two containers, is not only accurate on the left side of the :, it's also accurate on the right side. I assumed that linuxserver's compose file would already account for the actual paths that the app wants, but maybe it's being generic on the right side of the : as well as the left. Should be more like this: /home/kd/storage/media/downloads:/Downloads So maybe this (with the lowercase d in downloads) /home/kd/storage/media/downloads:/downloads

#Sonarr and sabnzbd download#

Kept me up later than I wanted to last night just thinking about those sloppy files hanging out together.īut looking at this with fresh eyes this morning.I'm thinking that the issue I'm having is perhaps not editing the container directory side of the download volumes. Here's the current file:Īnd it is a horrifying mess to look at in the directory, but it WORKS. So to test this theory, since I'd already installed it over and over again, I rewrote the docker-compose.yml file one more time to use the same config directory for both Sonarr and Sabnzbd. Sabnzbd is still keeping them in the default downloads folder inside its config folder, that Sonarr doesn't have access to. For some reason, even though I'm mounting a common folder for the downloads, and telling the containers to use that for the downloads, like this: /home/kd/storage/media/downloads:/downloads That made me look at the physical paths where the containers expect the downloads to be. Both containers are being created with PUID & PGID 1000, so I was fairly sure it wasn't a permissions issue. Our work with filter – U.S.Maybe.I uninstalled and reinstalled Sonarr and Sabnzbd probably 10 times yesterday fighting this 'DownloadedEpisodesImportService|Import failed, path does not exist or is not accessible by Sonarr:'īasically, everything would work up until the point where Sabnzbd needs to handed the downloaded file back to Sonarr.TRAILER MOUNTED SUCTION MACHINE – U.S.Enterprises has successfully emerged as a. 906, A 404, Karmaa Residency, Wasan Nagar remarks : -,To report network abuse, please contact mnt-irt,For troubleshooting, please contact tech-c and admin-c,Report invalid contact via.906, A 404, Karmaa Residency, Wasan Nagar, Nashik Maharashtra 422001 role : Parallel Web Cloud Services administrator.Registrar Abuse Contact Phone: Not Available.Usenterprises.in lookup results from server: