mirror/Sonarr
1
0
Fork 0
mirror of https://github.com/Sonarr/Sonarr synced 2024-12-22 07:43:01 +00:00
Code Issues Releases Wiki Activity

Updated Searches Indexers and Trackers (markdown)

Donald Webster 2020-04-06 21:01:09 -07:00
parent 5b68756113
commit ffa057fed0
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Searches-Indexers-and-Trackers.md

@ -4,7 +4,7 @@
The first step is to turn logging up to Trace, see [[Logging and Log Files]] for details. You'll then reproduce the issue and use the trace level logs from that time frame to examine the issue. If someone is helping you, put context from before/after in a [pastebin](https://paste.ubuntu.com) to show them. It doesn't need to be the whole file and it shouldn't *just* be the error. You should also reproduce the issue while tasks that spam the log file aren't running. The first step is to turn logging up to Trace, see [[Logging and Log Files]] for details. You'll then reproduce the issue and use the trace level logs from that time frame to examine the issue. If someone is helping you, put context from before/after in a [pastebin](https://paste.ubuntu.com) to show them. It doesn't need to be the whole file and it shouldn't *just* be the error. You should also reproduce the issue while tasks that spam the log file aren't running.
### Testing an Indexer or Tracker ### Testing an Indexer or Tracker
When you test an indexer or tracker, in debug or trace logs you can find the URL used. An example of a successful test is below, you can see it query the indexer via a specific URL w/ specific parameters and then the response. You test this url in your browser like `https://api.nzbgeek.info/api?t=tvsearch&cat=5000,5070&extended=1&apikey=(removed)&offset=0&limit=100` replacing the `apikey=(removed)` with the correct apikey like `apikey=123`. You can experiment w/ the parameters if you're getting an error from the indexer or see if you have connectivity issues if it doesn't even work. After you've tested in your own browser, you should test from the system Sonarr is running on *if* you haven't already. When you test an indexer or tracker, in debug or trace logs you can find the URL used. An example of a successful test is below, you can see it query the indexer via a specific URL w/ specific parameters and then the response. You test this url in your browser like `https://api.nzbgeek.info/api?t=tvsearch&cat=5030,5040,5045,5080,5070&extended=1&apikey=(removed)&offset=0&limit=100` replacing the `apikey=(removed)` with the correct apikey like `apikey=123`. You can experiment w/ the parameters if you're getting an error from the indexer or see if you have connectivity issues if it doesn't even work. After you've tested in your own browser, you should test from the system Sonarr is running on *if* you haven't already.
``` ```
19-11-12 13:27:28.8|Debug|Newznab|Downloading Feed https://api.nzbgeek.info/api?t=tvsearch&cat=5030,5040,5045,5080,5070&extended=1&apikey=(removed)&offset=0&limit=100 19-11-12 13:27:28.8|Debug|Newznab|Downloading Feed https://api.nzbgeek.info/api?t=tvsearch&cat=5030,5040,5045,5080,5070&extended=1&apikey=(removed)&offset=0&limit=100