From 7d997c37edb2eb316465c16ddaf240c1d8dd767b Mon Sep 17 00:00:00 2001 From: Brian Di Palma Date: Fri, 17 Jul 2020 02:13:57 +0100 Subject: [PATCH] Updated Searches Indexers and Trackers (markdown) --- Searches-Indexers-and-Trackers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Searches-Indexers-and-Trackers.md b/Searches-Indexers-and-Trackers.md index 12425fa..d13064a 100644 --- a/Searches-Indexers-and-Trackers.md +++ b/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. ### 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=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. +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 with 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 with 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