search

theotherp / nzbhydra2

Usenet meta search
Other
1.23k stars 75 forks source link

Upated to 1.1.0 and Sickrage doesn´t work anymore #66

Closed Hobbabobba closed 6 years ago

Hobbabobba commented 6 years ago

updated to v1.1.0 and have severe problems with Sickrage (Couchpotato works flawless):

nzbhydra-debuginfos-2018-01-16-08-57.zip

theotherp commented 6 years ago

Enable debug logging level for the log file and in the logging markers setting choose URL calculation. Do another search and send me the debug infos.

Am 16.01.2018 09:45 schrieb "Hobbabobba" notifications@github.com:

updated to v1.1.0 and have severe problems with Sickrage (Couchpotato works flawless):

  • in the search history i can see the search and some results from the indexers
  • Sickrage suddenly doesn´t get any result from nzbhydra
  • Sickrage just shows no results, but no error messages in the SR log

nzbhydra-debuginfos-2018-01-16-08-57.zip https://github.com/theotherp/nzbhydra2/files/1634212/nzbhydra-debuginfos-2018-01-16-08-57.zip

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/66, or mute the thread https://github.com/notifications/unsubscribe-auth/ANtAeXbeu2UQwDZUj8YD48eYBDJe-xCTks5tLGHBgaJpZM4Rfa-J .

Hobbabobba commented 6 years ago

nzbhydra-debuginfos-2018-01-16-11-43.zip

theotherp commented 6 years ago

I'm an idiot... The algorithm hiding the sensitive information in the log is also hiding all the information that I'd need to debug the issue... I'll try to find the problem tonight.

theotherp commented 6 years ago

Did you enter the same address in SR that you entered in CP?

Hobbabobba commented 6 years ago

all the settings are exactly the same. and i tried without reverse proxy settings, same problem

theotherp commented 6 years ago

You mean it doesn't even work when you enter hydra's local address into SB?

Am 16.01.2018 12:35 schrieb "Hobbabobba" notifications@github.com:

all the settings are exactly the same. and i tried without reverse proxy settings, same problem

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/66#issuecomment-357933846, or mute the thread https://github.com/notifications/unsubscribe-auth/ANtAeR9SgdL69pd6hqVcam60gmsUV4wPks5tLIlxgaJpZM4Rfa-J .

Hobbabobba commented 6 years ago

in hydra i deleted the settings for base-path and external URL. From SR and CP i used hydra through 192.168.0.5:5076 instead of https://www.mydomain.com/nzbhydra/ same effect: CP works, SR not.

theotherp commented 6 years ago

Jesus, I thought Hydra was complicaed to configure.

theotherp commented 6 years ago

Got it.

theotherp commented 6 years ago

Unfortunately knowing the problem is not the same as solving it. It might take a couple of days, sorry about that. It's caused by a quirk in SR. It tries to recognize if the provider is torznab or newznab by looking for a certain string in the XML output. My newznab output is fully valid but contains that string so SR tries to parse the XML expecting torznab.

Hobbabobba commented 6 years ago

just tried Sonarr. As you said, works perfect. I think i will just switch to Sonarr, gives you less of a headache ;)

theotherp commented 6 years ago

I think you won't regret it. I'll still try to solve this issue.

Am 17.01.2018 09:17 schrieb "Hobbabobba" notifications@github.com:

just tried Sonarr. As you said, works perfect. I think i will just switch to Sonarr, gives you less of a headache ;)

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/66#issuecomment-358229770, or mute the thread https://github.com/notifications/unsubscribe-auth/ANtAeeZZSq5O01m2LsH32oF01adIPXasks5tLayMgaJpZM4Rfa-J .