Hello.

I have a strange setup compared to most. My Plex server was built on Win10 and all of my media is in Win10. I bought a mini PC a while ago to run unRAID to start with HomeAssistant as a VM to move dockers and other items away from the instability of Win10 VMs, but being a miniPC, there is no internal room for expansion (1 nvme slot used for cache and 1 sata slot for SSD array).

 

I recently setup SABnzbd on my win10 with Sonarr as a docker in unRAID. After learning how to create remote shares and remote mapping, the solution worked perfectly (even with Overseer) and imported directly to the correct folders on my Win10 machine.  Once I introduced a VPN on my Win10, it broke the connection to access SABnzbd, so I decided to install SABnzbd in unRAID behind a VPN docker container.

 

I changed the Sonarr settings to introduce the new download client, and followed the mapping of this FAQ here (unRAID Docker FAQ), but I am still getting the error "Import failed, path does not exist or is not accessible by Sonarr: /data/usenet/TV/file_folder_name/. Ensure the path exists and the user running Sonarr has the correct permissions to access this file/folder."

 

My mapping is:

 

App Name     Container Volume       Host Path

SABnzbd      /downloads             /mnt/user/data/usenet/

             /incomplete-downloads  /mnt/user/data/usenet/incomplete/

sonarr       /downloads             /mnt/user/data/usenet/

             /tv                    /mnt/remotes/PLEXSERVE_TV_Shows/TV Shows/

My SABnzbd folder settings are:

 

And I can see the file folders in /mnt/user/data/usenet/TV, but Sonarr cannot import them after starting the download.

 

I used a backup configuration of SABnzbd from my Win10 on the docker container in unRAID, and there were no issues with the downloads once I updated the folder settings above with SABnzbd.

 

Any help would be appreciated

I was able to figure out my issue.

 

I looked further into the mapping and this was pretty much what was wrong. When I had changed the mapping in SANbzd, I didn't change the name of the path for unRAID. I left the name "/downloads" but the container path was actually "/data/usenet" (from following Trash Guides).  So, the "/downloads" path mapping didn't exist, but that folder was selectable.  Strange that the file would download and still be accessible through SMB to where I actually wanted it to download.

 

Now I can fix my other docker containers. I could not see the error until I actually clicked to edit the mapping that I made this error.