New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RSS feed doesn't return any results? #921
Comments
Please attach debug infos as requested in the issue template: https://github.com/theotherp/nzbhydra2/blob/master/.github/ISSUE_TEMPLATE.md |
Aah, I checked the logs with
I tried going to So I guess nzbhydra2 can't do what I'm trying to do? |
http://:5076/torznab/api?apikey=&t=search&q=linux+iso In the config screen you can click the "API?" button for that info. |
Thank you!! In FreshRSS, it doesn't show any info except the name and you can download the magnet/torrent. I can't even see which indexer the link came from (although I do see that that info is there in the raw feed Is there some other app or app category that I should/could be using to read the nzbhydra2 feeds? Sorry, the learning curve with docker/indexers/torznab/rss has been steep over the last few days... Also, where's the best place I can ask questions? I have another question but not really appropriate as a bug report. |
Automation tools like sonarr or radarr would be your best bet. Or NZB360 if you're on android. See https://trash-guides.info/ |
I got FreshRSS to show more info by using an XPathBridge in RSS-Bridge with these settings:
Thanks again. I wasn't sure about sonarr or radarr because they're supposedly for movies/TV shows - do they work for random files like linux isos as well? |
Using lscr.io/linuxserver/nzbhydra2:latest docker image.
I'm trying to add a feed from nzbhydra2 to FreshRSS so I can know when the latest linux isos are released.
But the rss feed never returns any results?
The response is always:
Even though when I manually search, I get a lot of results.
In case it makes a difference, I'm only using torrent indexers.
What am I doing wrong?
The text was updated successfully, but these errors were encountered: