
This becomes a problem in more unique use cases, like the download client running on a different system (maybe even OS!). The key to understanding path issues is knowing that Sonarr gets the path to the download from the download client, via its API. Incorrect path issues are possible too, though less common in normal setups. Sometimes, permissions in the library folder can be at fault too, so be sure to check both. Most import errors are permissions issues, remember that Sonarr needs to be able to read and write in the download folder. If they're not showing up in Activity, this is the issue you need to focus on first so go back and figure that out. Import issues should almost always manifest as an item in Activity with an orange icon you can hover to see the error. Does it get sent to the download client? Does it end up with the correct category? Does it show up in Activity? Does it end up in the trace level logs during the Check For Finished Download task which runs roughly every minute? Does it get correctly parsed during that task? Does the queued up download have a reasonable name? Since Sonarr searches by tvdbid, season and episode on most indexers/trackers, it can queue one up with a name that it can't recognize. Pick one of those episodes and attempt to download it. Now we'll try a download, pick a show and do a manual episode search. It might be obvious, like an authentication problem where you've gotten the username, password or apikey wrong. It could be a connection problem, which could indicate a wrong ip, hostname, port or even a firewall blocking access. You should find a URL you can put into your browser and see if it works. Start by testing the download client, if it doesn't work you'll be able to see details in the trace level logs. When you reach out for help, be sure to read Asking for Help so that you can provide us with the details we'll need.

Nobody wants to dig through the whole trace log (it is huge!), but just a line or two is unlikely to help. Remember to get them from the actual log file, put them in a pastebin and show us context around what we need to see. And if you can't, anyone you ask for help will need to see them for sure. Start by using the Logging and Log Files article to turn logging up to trace, it is likely you're going to need to look at them to figure out what is wrong. This means that while there are some common setups, there isn't one right setup and everyone's setup can be a little different. There is a large variety of supported download clients and an even bigger variety of setups. From a high level perspective, Sonarr needs to be able to communicate with your download client and have access to the files it downloads. Troubleshooting Downloads and Importingĭownloading and importing is where most people experience issues.

The new V3 Wiki can be found at the Servarr Wiki.
