theotherp / nzbhydra2

Usenet meta search
Other
1.26k stars 75 forks source link

Problem with Sonarr and Radarr since update to 1.1.0 #71

Closed MrChick closed 6 years ago

MrChick commented 6 years ago

I have some strange issues with sonarr and radarr since updating from 1.0.18 to 1.1.0 yesterday. I did some downloads through sonarr couple of minutes before the update which worked fine.

The logs (it's set to debug) show successful searches on my indexers, though (ignore the slow, redacted indexer - same issue with it being disabled):

2018-01-17 20:07:42.337  INFO --- [0.1-5076-exec-5] org.nzbhydra.api.ExternalApi             : [Search: 705538, IP: 88.130.6.17, User: MrChick] Received external API call: NewznabParameters{t=TVSEARCH, q=Better Things, cat=[5030, 5040], season=2, ep=10, offset=0, limit=100, raw=false, extended=true}
2018-01-17 20:07:42.338  INFO --- [0.1-5076-exec-5] org.nzbhydra.api.ExternalApi             : [Search: 914690, IP: 88.130.6.17, User: MrChick] Executing new search
2018-01-17 20:07:42.341  INFO --- [0.1-5076-exec-5] o.n.searching.IndexerForSearchSelector   : [Search: 914690, IP: 88.130.6.17, User: MrChick] Selected 4 out of 4 indexers: NZB Finder, NZBGeek, <redacted>, NZBCat
2018-01-17 20:07:42.343  INFO --- [ool-27-thread-2] org.nzbhydra.indexers.Newznab            : [Search: 914690, IP: 88.130.6.17, User: MrChick] NZBGeek: Calling https://api.nzbgeek.info/api?apikey=<APIKEY>
2018-01-17 20:07:42.343  INFO --- [ool-27-thread-1] org.nzbhydra.indexers.Newznab            : [Search: 914690, IP: 88.130.6.17, User: MrChick] NZBCat: Calling https://nzb.cat/api?apikey=<APIKEY>
2018-01-17 20:07:42.343  INFO --- [ool-27-thread-4] org.nzbhydra.indexers.Newznab            : [Search: 914690, IP: 88.130.6.17, User: MrChick] NZB Finder: Calling https://nzbfinder.ws/api?apikey=<APIKEY>
2018-01-17 20:07:42.343  INFO --- [ool-27-thread-3] org.nzbhydra.indexers.Newznab            : [Search: 914690, IP: 88.130.6.17, User: MrChick] <redacted>: Calling https://<redacted>/nzbhydra/api?apikey=<APIKEY>
2018-01-17 20:07:42.512  INFO --- [ool-27-thread-4] org.nzbhydra.indexers.Newznab            : [Search: 914690, IP: 88.130.6.17, User: MrChick] NZB Finder: Successfully executed search call in 162ms with 100 results
2018-01-17 20:07:42.861  INFO --- [ool-27-thread-1] org.nzbhydra.indexers.Newznab            : [Search: 914690, IP: 88.130.6.17, User: MrChick] NZBCat: Successfully executed search call in 517ms with 0 results
2018-01-17 20:07:43.851  INFO --- [ool-27-thread-3] org.nzbhydra.indexers.Newznab            : [Search: 914690, IP: 88.130.6.17, User: MrChick] <redacted>: Successfully executed search call in 1507ms with 11 results
2018-01-17 20:07:44.060  INFO --- [ool-27-thread-2] org.nzbhydra.indexers.Newznab            : [Search: 914690, IP: 88.130.6.17, User: MrChick] NZBGeek: Successfully executed search call in 1716ms with 6 results
2018-01-17 20:07:44.066  INFO --- [0.1-5076-exec-5] org.nzbhydra.searching.Searcher          : [Search: 914690, IP: 88.130.6.17, User: MrChick] Returning results 1-100 from 111 results in cache. A total of 208 results is available from indexers of which 0 were already rejected and 6 were removed as duplicates
2018-01-17 20:07:44.068  INFO --- [0.1-5076-exec-5] org.nzbhydra.api.ExternalApi             : [Search: 914690, IP: 88.130.6.17, User: MrChick] Search took 1729ms. Returning 100 results
2018-01-17 20:07:44.330  WARN --- [0.1-5076-exec-2] org.nzbhydra.web.UrlCalculator           : [Search: 267949, IP: 88.130.6.17, User: MrChick] Header x-forwarded-host does not contain port. Please change your reverse proxy configuration. See https://github.com/theotherp/nzbhydra2/wiki/Exposing-Hydra-to-the-internet-and-using-reverse-proxies for more information
2018-01-17 20:07:44.331  INFO --- [0.1-5076-exec-2] org.nzbhydra.api.ExternalApi             : [Search: 267949, IP: 88.130.6.17, User: MrChick] Received external API call: NewznabParameters{t=TVSEARCH, q=Better Things, cat=[5030, 5040], season=2, ep=10, offset=100, limit=100, raw=false, extended=true}
2018-01-17 20:07:44.331  INFO --- [0.1-5076-exec-2] org.nzbhydra.api.ExternalApi             : [Search: 731148, IP: 88.130.6.17, User: MrChick] Executing new search
2018-01-17 20:07:44.332  INFO --- [ool-32-thread-1] org.nzbhydra.indexers.Newznab            : [Search: 731148, IP: 88.130.6.17, User: MrChick] NZB Finder: Calling https://nzbfinder.ws/api?apikey=<APIKEY>
2018-01-17 20:07:44.497  INFO --- [ool-32-thread-1] org.nzbhydra.indexers.Newznab            : [Search: 731148, IP: 88.130.6.17, User: MrChick] NZB Finder: Successfully executed search call in 160ms with 91 results
2018-01-17 20:07:44.518  INFO --- [0.1-5076-exec-2] org.nzbhydra.searching.Searcher          : [Search: 731148, IP: 88.130.6.17, User: MrChick] Returning results 101-200 from 202 results in cache. A total of 208 results is available from indexers of which 0 were already rejected and 6 were removed as duplicates
2018-01-17 20:07:44.520  INFO --- [0.1-5076-exec-2] org.nzbhydra.api.ExternalApi             : [Search: 731148, IP: 88.130.6.17, User: MrChick] Search took 188ms. Returning 100 results
2018-01-17 20:07:46.330  WARN --- [0.1-5076-exec-3] org.nzbhydra.web.UrlCalculator           : [Search: 545067, IP: 88.130.6.17, User: MrChick] Header x-forwarded-host does not contain port. Please change your reverse proxy configuration. See https://github.com/theotherp/nzbhydra2/wiki/Exposing-Hydra-to-the-internet-and-using-reverse-proxies for more information
2018-01-17 20:07:46.333  INFO --- [0.1-5076-exec-3] org.nzbhydra.api.ExternalApi             : [Search: 545067, IP: 88.130.6.17, User: MrChick] Received external API call: NewznabParameters{t=TVSEARCH, q=Better Things, cat=[5030, 5040], season=2, ep=10, offset=200, limit=100, raw=false, extended=true}
2018-01-17 20:07:46.333  INFO --- [0.1-5076-exec-3] org.nzbhydra.api.ExternalApi             : [Search: 126472, IP: 88.130.6.17, User: MrChick] Executing new search
2018-01-17 20:07:46.334  INFO --- [0.1-5076-exec-3] org.nzbhydra.searching.Searcher          : [Search: 126472, IP: 88.130.6.17, User: MrChick] Returning results 201-202 from 202 results in cache. A total of 208 results is available from indexers of which 0 were already rejected and 0 were removed as duplicates
2018-01-17 20:07:46.334  INFO --- [0.1-5076-exec-3] org.nzbhydra.api.ExternalApi             : [Search: 126472, IP: 88.130.6.17, User: MrChick] Search took 1ms. Returning 2 results

At first I thought it might have something to do with the forwarded port headerstuff so I changed my vhost config according to the wiki. Still get the message, still the same problems as described below.

Hydras Webinterface

I can send results to sabNZBd without any problems (upload-method)

Radarr:

I do get a list of results, but I can't download anything because apparently the URI is empty. Nothing striking in its logs

Sonarr:

No matter what I search for, I always get no results shown even though the hydralog indicates there should be some. I also tried the trace logs, which seems to point at the actual problem:

18-1-17 20:36:23.8|Debug|NewznabRssParser|Failed to parse Url http:/getnzb/api/-734<redacted>600?apikey=(removed) ignoring.

Edit: I just updated to 1.1.1 after configuring the external url in the settings. Not sure which of those fixed my problem; but I don't get thsoe missing-port-messages anymore. The external URL field is shown to be empty though (even after a couple of tries), so not sure if it's actually saved or there's another bug

theotherp commented 6 years ago

It's indeed caused by 1.1.x

The external URL field should be empty because the new code should theoretically derive all the needed data from the request.

For some reason Hydra cannot calculate the correct URL to use for the NZB links in its results and uses an empty host. What URL did you enter in Sonarr for Hydra's host? Do you use 127.0.0.1 or a certain IP address or did you enter the URL of a reverse proxy or what?

MrChick commented 6 years ago

Sonarr/Hydra use the host of the reverse proxy, which worked perfectly until 1.1.0 and again since 1.1.1 as it seems

theotherp commented 6 years ago

Ah sorry, didn't read the update properly. So I consider this already fixed. Sorry about that. The whole issue with hosts and ports and schemes and what address to use etc is really complicated.