I’m new to Sonarr/NzbDrone and trying to set up Dognzb as an indexer. I am using the up-to-date dognzb api as far as I know: https://api.dognzb.cr and I’ve set my api key correctly.
Here is a relevant chunk of the sonarr logs with trace-level logging enabled:
15-4-3 16:53:27.7|Debug|Newznab|Downloading Feed https://api.dognzb.cr/api?t=tvsearch&cat=5030,5040&extended=1&apikey=<removed>&offset=0&limit=100
15-4-3 16:53:27.7|Trace|HttpClient|Req: [GET] https://api.dognzb.cr/api?t=tvsearch&cat=5030,5040&extended=1&apikey=<removed>&offset=0&limit=100
15-4-3 16:53:30.5|Trace|HttpClient|Res: [GET] https://api.dognzb.cr/api?t=tvsearch&cat=5030,5040&extended=1&apikey=<removed>&offset=0&limit=100 : 200.OK (2,859 ms)
15-4-3 16:53:30.5|Trace|NzbDroneErrorPipeline|Handling Exception
15-4-3 16:53:30.5|Warn|NzbDroneErrorPipeline|Invalid request Validation failed:
-- No results were returned from your indexer, please check your settings.
The response seems pretty straight forward - no results returned. If I perform the same request with curl I get a 200:
Even if the dognzb api is overloaded (like the root element problem I read about while searching here) it seems like a 200 would be considered successful and allow me to add this as an indexer. I don’t know if the results above are actually successful - if they are not I’m wondering what I am doing wrong in setting up the dognzb indexer. I have tried using 5000, just 5030 and just 5040, but they all have the same results as far as I can tell.
For what it’s worth my dognzb account is in good standing and I have noticed during the tests made by nzbdrone I can see my allowed requests counter decrease:
101 API request received today (2,399 left)
If there’s any more info that would help figure this out please let me know. Thank you.
I have the exact same problem.
Was working - then I reinstalled my OS…now Sonarr won’t let me add Dognzb indexer.
When I check on Dognzb: I see the API requests being decreased. Oznzb indexer is working OK though.
It would seem that the problem is not with Sonarr but with Dognzb. Check their forums on “API requests” they are deploying new API servers ATM and we just have to either wait it out or get a “Dogpass” to access the VIP API server.
Dognzb has been returning a blank RSS feed instead of one with valid results, which Sonarr treats as an error (but since it hits their server the API hit is counted). You can add it as disabled to get it added, but its not worth attempting using it actively until their issues are resolved.
@markus101 Thanks this is just what I was wanting - I can add it disabled which just lets me get it into Sonarr. I know dognzb has been doing things with their API recently and I’m content with waiting them out (and I realize it’s not a sonarr issue). Allowing me to add it and then enable it later is perfect. Thanks for the help.
OT: Sonarr is awesome by the way. I was turned off by using mono on OS X but I’m glad I finally got over that hump.
As I wrote in an other thread, I am not entirely convinced that the empty RSS response is an API problem.
I am not trying to say there is no problem with their API as you can see in search results, but I pulled the git, wrote my own indexer using the RSS link I provided last time and it’s working like a charm.
I agree on that when using the search functionality.
However RSS were working somewhat fine until last week (Tuesday or Wednesday) since then no hits at all.
Because you are open source, I was able to easily add a new indexer to use their alternate RSS feed (the one provided in the profile page). I had no problems getting the RSS feed since. I didn’t remove the other RSS feed to see if it’s a temporary problem, but it still fails to get RSS results.
Thats a completely separate endpoint on their main web server, not their API web server. I don’t think thats a standard endpoint for newznab either, just something they adde. We’re not going to support a one-off endpoint for a newznab indexer though, once they fix their API issues things will be back to normal, but thats in their hands.
Yeah, it’s not standard. I just thought they were moving on to their own RSS feed instead of the newznab one.
But if you are aware and don’t want to change anything in sonarr that’s fine by me.
Their rss feed isn’t capable of search, so there’s that.
That’s the point of the newznab api spec, provide a standardized api capable of seach too.
@markus101 You actually got confirmation from dog admins that there’s a problem with their api? It’s all a pretty hot item here, reddit etc. But haven’t really seen something official, that’s possibly only on their own forums, but I can’t check.
Yeah, their IRC channel gets a few flybys and they confirm issues there. They’re probably tired of answeerjng on reddit, usually a couple new posts a week on reddit about it.
@falsename Sorry for reviving this, could you share what you did? I suppose you might have a github repo somewhere? If it is as simple as adding 1-2 plaintext files somewhere, one could offer annoyed/upset people a temporary patch (unofficially). Say if people are upset on reddit / the forums.
It’d be less work for someone to find another indexer, versus having to find the binaries, download them and then deal with switching back when their API’s finally work again.
