I don’t think this is a permission issue as I have NZBGet add a 0002 UMask to the files it touches and Deluge does the same. Is there anything different that I should be doing for the remote path mapping to get this to work? Category: sonarr (this must correspond to the category that is later configured in sonarr, dafault is sonarr-tv but this guide uses sonarr) Save pah: /data/torrents/tv Click Add Radarr Install container. If you are having issues use something like Firefox, or something else. As an FYI Microsoft Edge is just a Microsoft skin on Google Chrome. Also, look at the logs (right on the container, and click logs instead of restart), and check for errors. Everything else on the server (including sonarr) is working fine. Earlier this year, when loading the web GUI, I’m stuck at the bouncing balls screen. Now, when I try to access radarr through port 7878 I get the message that the site can't be reached and my server refused to connect. Sonarr version (exact version): Not sure, last updated in early 2017 (January) Mono version (if Sonarr is not running on Windows): 4.6.2.7-8 OS: Synology DSM 6.1.3-15152-4 ((Debug logs)): Description of issue: Installation has worked for years. I have set the remote and local paths with the additional “…/Downloaded/TV” because this is the final location that both NZBGet and Deluge moves the TV category downloads after post processing with extracting files, etc. The other option is to redeploy the docker containers. The site can't be reached (out of the blue) Describe the bug. Local Path: /unraid/Downloads/Downloaded/TV/ Host: 192.168.1.2 (unRAID’s ip address and the same address as is listed in the “hosts” section of the download client ip) This is the current setup I am trying that isn’t working yet, I still see the “No files found are eligible for import in /unraid/Downloads/Downloaded/TV/…” error message I have set both Sonarr and Radarr to have the “/download” path mapped to “/mnt/user/Downloads/” as well Once I did this, Sonarr/Radarr could now connect to both SabNZB & my indexers.I have a feeling that there may be a problem with the path mappings because Deluge, NZBGet and Sonarr are all in docker containers with slightly different paths.Īt the moment I have tried to setup remote path mapping in Sonarr to see if files can be seen in Sonarr for importĬurrently both NZBGet and Deluge download files to the following path “/mnt/user/Downloads/” set as “/data” To test it out, go to your favourite torrent indexer site and copy the magnet URL into a new torrent by clicking the + button in the top left. For this I had to go into the SabNZB download client settings within Radarr, and change the 'Host' from my local IP of the server, to the word 'localhost'. Sonarr lists Sab in 'download clients' and the client test is successful. However, these dockers could not connect to SabNZB anymore - only the indexers were testing OK, not the download clients. I can search manually in Sonarr, and it will send to Sab just fine, but its not downloading automatically. If one container has /data and the other has /download, it won't work, even if they both map to /mnt/user/downloads. This allowed me to see the Sonarr/Radarr webguis. Be sure both the downloading container and sonarr have identical mappings for both the host side AND the container side for the download folder. Make sure that your ports for Sonarr/Radarr/Lidarr are added into that field, separated by commas.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |