mirror of
https://github.com/Sonarr/Sonarr.git
synced 2024-11-25 04:02:48 +01:00
Updated Completed Download Handling (markdown)
parent
3ecf8999bf
commit
aa477f52b7
@ -59,39 +59,17 @@ Steps:
|
||||
|
||||
1. Enable Completed Download Handling by toggling the switch on the Sonarr Settings -> Download Client page.
|
||||
|
||||
###### Unsupported: Download Client on Different Computer
|
||||
###### All: Download Client on Different Computer
|
||||
|
||||
_As mentioned earlier, Completed Download Handling gets the file path to the download directly from the Download Client. Such a path is inaccessible from different computers and would prevent Completed Download Handling from importing the download._
|
||||
|
||||
The best solution to this problem is to run Sonarr and your Download Client on the same computer.
|
||||
In Settings->Download Client->Remote Path Mapping is an option to configure Sonarr to translate the remote path to something locally accessible.
|
||||
|
||||
_There are some advanced options to work around this limitation, but those will not be discussed here_
|
||||
For example:
|
||||
If I configured a remote Sabznzbd instance named 'MySab' in Sonarr. And that Sabnzbd instance uses `/sda3/download/sabnzbd/completed` as root folder for completed downloads. And that path is available as `\\10.2.3.4\sabnzbd\completed` on my Windows machine.
|
||||
Then you would add a Remote Path Mapping for Host=MySab, RemotePath=`/sda3/download/sabnzbd`, LocalPath=`\\10.2.3.4\sabnzbd`.
|
||||
|
||||
##### Keeping Completed Download Handling disabled
|
||||
|
||||
If you absolutely want to keep using the Drone Factory:
|
||||
|
||||
1. Enable Completed Download Handling and Save.
|
||||
2. Disable Completed Download Handling and Save.
|
||||
|
||||
This will permanently remove the warning.
|
||||
|
||||
##### Advanced Configuration/Migration Options
|
||||
|
||||
The above scenarios were written to avoid complex choices. If you're a Power User you might want to have a couple of different options:
|
||||
|
||||
* Change the Drone Factory folder to a different path. (this is actually what I did)
|
||||
You still have to remove the Drone Factory Post-Processing script, if you previously used it.
|
||||
|
||||
* Change the output path of your existing category.
|
||||
You still have to remove the Drone Factory Post-Processing script, if you previously used it.
|
||||
|
||||
* Simply disable the Drone Factory entirely.
|
||||
You still have to remove the Drone Factory Post-Processing script, if you previously used it.
|
||||
|
||||
Not creating a new category may cause a couple of old imported downloads to show up as queued, removing them from the Download Client history resolves that.
|
||||
|
||||
_As you can see, these are quite a number of choices and potential issues we tried to avoid by providing a couple of basic steps._
|
||||
However, the best solution to this problem is to run Sonarr and your Download Client on the same computer.
|
||||
|
||||
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user