Mirrors/Sonarr
1
0
Fork 0
mirror of https://github.com/Sonarr/Sonarr.git synced 2024-11-22 02:32:51 +01:00
Code Issues Releases Wiki Activity

Updated Downloads and Importing (markdown)

Donald Webster 2019-12-14 20:35:52 -08:00
parent 7eef221842
commit be47c77c95
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
Downloads-and-Importing.md

@ -1,3 +1,4 @@
# Troubleshooting Downloads and Importing
Downloading and importing is where *most* people experience issues. From a high level perspective, Sonarr needs to be able to communicate with your download client and have access to the files it downloads. There is a large variety of supported download clients and an even *bigger* variety of setups. This means that while there are some *common* setups, there isn't one *right* setup and everyone's setup can be a little different. Downloading and importing is where *most* people experience issues. From a high level perspective, Sonarr needs to be able to communicate with your download client and have access to the files it downloads. There is a large variety of supported download clients and an even *bigger* variety of setups. This means that while there are some *common* setups, there isn't one *right* setup and everyone's setup can be a little different.
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. And if you can't, anyone you ask for help will need to see them for sure. Remember to get them from the actual log file, put them in a pastebin and show us context around what we need to see. Nobody wants to dig through the whole trace log (it is huge!), but just a line or two is unlikely to help. 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. And if you can't, anyone you ask for help will need to see them for sure. Remember to get them from the actual log file, put them in a pastebin and show us context around what we need to see. Nobody wants to dig through the whole trace log (it is huge!), but just a line or two is unlikely to help.