Suddenly getting indexer error after update to 2.0.0.1981

Help & Support
1

Could there possibly be an issue with 2.0.0.1981 develop, or is it the indexer?

Here’s the error:

NzbDrone.Common.Http.HttpException: HTTP request failed: [403] [GET] at [https://api.nzb.su/api?t=tvsearch&cat=5030,5040&extended=1&apikey=xxxxxxxxxxxxxxx]
  at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00000] in <filename unknown>:0 
  at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00000] in <filename unknown>:0 
  at NzbDrone.Core.Indexers.FetchFeedService.Fetch (IIndexer indexer, IEnumerable`1 urls) [0x00000] in <filename unknown>:0 
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>403 Forbidden</title>
</head><body>
<h1>Forbidden</h1>
<p>You don't have permission to access /api
on this server.</p>
</body></html>

I posted a question about this over at the indexer forums, but it seems like the timing of the update with the sudden logged issues point to a possible problem with this new version (especially due to this new feature: Will now provider a clearer error if the indexer returned unexpected html content).

Thanks!

2

Looks like an indexer problem, my indexers don’t show the same error.

3

One way to check would be to copy the URL at the top of the message, change the xxx part into your actual API key and visit the page in your browser. If that also gives a 403, it wouldn’t be Drone causing the issue.

4

NMe, just tried your suggestion, and it did not give a 403–I got all that XML goodness. So what do I do from here?

As I said before, I only got that with one particular indexer. Seems strange how it works fine in the browser when I use that link from the log (and my API key).

5

Its a change to the Accept header we send in the latest version and the fact that their API doesn’t like it.

I have asked them to correct this on their forums: http://howdoiuse.net/help-nzbsu/403-forbidden-unless-texthtml-is-accepted/

1 Like
6

Is there any way this can be fixed temporarily besides waiting for the site? I too only use this one indexer, so its temporarily made nzbdrone useless for me.

Would rolling back the version of nzbdrone work?

7

markus, they probably allow:

request.Headers.Accept = "text/xml, text/rss+xml, application/rss+xml";

Which is already in the code, just not used yet in the webrequest itself.
I can fix that and see it solves the problem for Jeax.

8

@Jeax, can you check if version 2.0.0.1992 solves your problem?

9

Though not directed to me, I can confirm .1992 solves the issue with that indexer. Thanks so much!

10

Great, tnx for the confirmation.

11

indeed, problem seems fixed in .1992. thank you

12

@Taloth odd, when I changed the headers in code it appeared to be sent properly, regardless, glad its working now.