Open drelephant opened 5 months ago
Prowlarr has same function as NZBHydra, i don't see any reason to add one to other. What you want to do is really pointless.
I want to have a single RSS feed for each search, with each one searching all my indexers.
You can't do that with prowlarr. Prowlarr does not "want to promote this kind of use".
I'm curious what you believe the difference is between Jackett and Prowlarr in this context? To my mind, they both do almost exactly the same thing. So why would you ever add a Jackett indexer to nzbhydra2? Why not just use Jackett by itself?
Sorry for the late response.
They don't seem to support a torznab/newznab compatible API. I'm honestly not sure if implementing their proprietary API is worth it, especially as I can't say how stable it is. I'll keep this ticket open, though - who knows.
Using lscr.io/linuxserver/nzbhydra2:latest docker image.
I might be doing something stupid, but I can't successfully add a Prowlarr indexer to nzbhydra2.
Jackett feeds work fine, but I prefer the Prowlarr UI.
From Jackett I can just "copy torznab feed" then add the api key and it works fine. Or even better use the excellent "read from Jackett config" to get them all at once.
But for Prowlarr, I go to Prowlarr and copy the indexer url, eg
http://<serverip>:9696/2/api?apikey=<apikey>&extended=1&t=search
.Then go to nzbhydra2, "Add new indexer-Torrents-Choose from presets-Jackett/Cardigann", then click on "Submit".
But it always fails with "Connection check failed".
The logs have an error about unmarshalling exception:
I have tried a few other things, but haven't been successful.
Is there a way that I can add a Prowlarr indexer to nzbhydra2, or even better request them all at once as I can for Jackett?