thewolf56

Members
  • Posts

    2
  • Joined

Community Answers

  1. thewolf56's post in Sonarr and SABnszbd import (mapping) issue was marked as the answer   
    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.