Sonarr version (exact version): 2.0.0.4230
Mono version (if Sonarr is not running on Windows): 4.2.3
OS: unRAID 6.1.9
((Debug logs)): http://pastebin.com/K80LMjFG
(Make sure debug logging is enabled in settings and post the full log to hastebin/pastebin/dropbox/google drive or something similar, do not post them directly here)
Description of issue: any nzb grabbed from althub.co.za via api, either rss sync or manual search, produces an error. Althub is adamant it’s not an error on their end.
Looks like we’re not cleansing the API key from the nzb URL properly when we log it (since that URL worked for me), be worth changing your API to be safe.
Since I could download it, I can see the contents and it looks fine. The error looks to be on the NZBget side, ((trace logs)) in Sonarr might show the response Sonarr got from NZBget, but NZBget’s logs might indicate the issue as well. You could also try uploading the NZB to nzbget to rule out a bad NZB.
Which version of NZBget are you using?
I’m using NZBGet v17.0
Pertinent section of the log is as follows:
ERROR Wed Aug 24 2016 20:39:57 Could not add collection Macross Delta - 21 (1280x720 HEVC2 AAC).nzb to queue
ERROR Wed Aug 24 2016 20:39:57 Error parsing nzb-file Macross Delta - 21 (1280x720 HEVC2 AAC).nzb
ERROR Wed Aug 24 2016 20:39:57 Error parsing nzb-file: Premature end of data in tag html line 1
ERROR Wed Aug 24 2016 20:39:57 Error parsing nzb-file: Opening and ending tag mismatch: body line 3 and html
ERROR Wed Aug 24 2016 20:39:57 Error parsing nzb-file: Opening and ending tag mismatch: hr line 5 and body
Regardless of what nzb I add I get this same error. This is only happening with althub, not other indexers, and only when adding the nzb from sonarr whether via NZB360 on Android or the sonarr web UI. Also regardless if its added by search or rss sync. If I use NZB360 to search althub and add the nzb to nzbget directly, it downloads fine.
They’re definitely serving up HTML content when Sonarr requests it, though it works fine when grabbed in a browser directly, perhaps something with the user agent Sonarr uses causes it. About the only thing I can think of (without having access ourselves) would be to use a proxy (such as fiddler) to watch the traffic and capture the response they send back, maybe its something as simple as they’re redirecting to the login page because authentication is missing from the request.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.