What is Reddit's opinion of
NZBHydra2?
From 3.5 billion Reddit comments
➔ NZBHydra2 website
By popularity on Reddit, this Service is:
52 reviews of this app found across Reddit:
Usenet.
For $40/year (plus $10/year for a good indexer, or NZBHydra to use free indexers) you get lightning fast speed and don't (usually) have to worry about incomplete downloads. SABnzbd can be used with Sonarr & Radarr for full automation of fetching as well.
I've nearly stopped torrenting entirely, I only do it for really obscure and old shit now.
If choosing between Dog and nzbsu I would choose nzbsu any day. The stats from my Hydra install show it's much better, and Dog's recent frequent "4 years for just $50 sales!" has me worried that they are going out of business. Do you think otherwise?
Also, OP should install NZB Hydra if he hasn't already.
Another solution is to add each indexer from Jacket to nzbHydra 2 and then usethe torznab link from nzbHydra 2 in Radarr/Sonarr/Lidarr. This will save you from having to add each indexer to Radarr/Sonarr/Lidarr individually and overcome the different category and number of response limitations seen while using the torznab all address from Jackett.
DO NOT expose any of these services directly to the internet (i'm assuming you're running these at home and were thinking of using "port forward" on your router to point to them running on your server.
be smart, set up a reverse proxy to act as a webserver-in-the-middle between the services and your router.
set a SSL certificate and use https encryption. you can get a free certificate from letsencrypt.org.
you didn't mention if you're running these on linux or another operating system. if you're on linux, you might look into Docker and running these in containers, they are (IMHO) easier to manage and update this way, and slightly more secure. you can find out a lot more information and a good setup over at media-docker.com.
rather than point all your applications directly at your indexers, consider using nzbhydra2 as the middle-man. it also has a handy interface for you to do your own searches directly. this also can run in a docker container.
You're talking about that random site using the nzbhydra name. Not sure if many people use or recommend that site here but perhaps try that site's support contact page
https://nzbhydra.com/app/#/support
NOTE: For others reading this the site that OP is referring to has no relation to the well known NZBHydra meta search software
https://github.com/theotherp/nzbhydra2
/r/NZBHydra
You may want to check out Hydra2 and use it to aggregate your indexers. It allows you to give indexers priorities. It also does a good job of interfacing with a local install of Spotweb so you don't always have to use an external indexer.
https://github.com/theotherp/nzbhydra2
Most fo the Spotweb users are from the Netherlands so a lot of the comments are in Dutch. Most of the time nzbget handles the passwords on encrypted downloads, but sometimes you may have to look in the comments for the password. Password in Dutch is wachtwoord or sometimes ww.
It's more or less 1) install OpenJDK 2) download the hydra zip 3) unzip it 3) run the binary. See https://github.com/theotherp/nzbhydra2/wiki/Windows-service-and-Linux-start-scripts for running it as a service.
Similar to block accounts that fill in the gaps when articles are missing from the primary provider, you can also leverage low-cost index subscriptions with API limits so that only get searched or used when the primary indexer doesn't return satisfactory results. This can be setup with tools like nzbhydra & Prowlarr.
I don't think this feature will come to LunaSea, but instead I think users should install NZBHydra2. It adds a lot of complexity (since different indexers can return different data), and instead NZBHydra2 handles all of that for me, and includes more features like stats and such. NZBHydra2 is already supported within LunaSea and can be added as a regular indexer.
For Usenet I'd highly recommend using NZBHydra2 and premiumizer. Configure all your indexers in Hydra, set it to save NZBs to a blackhole folder, then configure Premiumizer to watch that blackhole.
Then you'll be able to search all your indexers (eg I use Geek, DrunkenSlug, NZBPlanet, and SimplyNZBs) with one interface, and it'll show a button to send the NZB to Premiumize.
In fact I'd recommend doing this for torrents too, although you'll need to install Jackett as well. That way you can search usenet and torrents from Hydra!
You can pair this with apps like Lidarr and Sonarr if you like!
Make sure to chmod +x it and if it doesn't run, try the python script (make sure you have python installed).
Once I installed the jdk, the script ran for me (but I can't remember if I had to use rhe python script of not)
I use NZBHydra2 as a indexer proxy and it has a setting to remove trailing text from the name of the NZB you're using. This fixes most of those offending NZBs for me.
Just do not use the /all thing. Add each indexer you setup in Jackett as an individual one in Radarr/Sonarr and pay close attention to the categories, you can view them by editing the indexer in Jackett and set them in that indexers settings in Sonarr/Radarr.
Since doing that for so many indexers is annoying, you might consider looking at nzbhydra2 to aggregate them all into one feed going into Radarr/Sonarr. It doing torrent aggregation is pretty new, so I haven't fully switched over to this personally (running both in parallel right now for torrents), but it is worth considering.
Follow the Readme. Don't clone the source code, download the latest Linux release, extract it somewhere and run the binary.
https://github.com/theotherp/nzbhydra2/releases/download/v1.4.13/nzbhydra2-1.4.13-linux.zip
Hey, please post your debug infos ZIP here: https://github.com/theotherp/nzbhydra2/issues/149
I haven't had any memory issues with xmx=256 on my machine with 10 indexers and a history that spans two years . But I also know that compared to some people I'm hardly a power user.
Anyway, as others said 512MB as XMX value should suffice for all but the most extreme users.
The developer states on github that he doesn't have anything to do with the site.
Also, he/she recently released version two which has noticable performance increase, but also has more overhead. Currently in beta but works very well for me.
Works fine for me. Please make sure to use the settings as provided in https://github.com/theotherp/nzbhydra2/wiki/Exposing-Hydra-to-the-internet-and-using-reverse-proxies
It should looke like this:
location /hydra {
proxy_pass http://127.0.0.1:5076/hydra;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_set_header Scheme $scheme;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $host;
proxy_redirect off; }
That also means setting the URL base /hydra in NZBHydra (you can change it in the file settings.yml while hydra is shut down).
It actually was just updated to patch the problem, so that's good. Just make sure you update.
I originally found it by searching for log4j in their github.
Since it was very early in the exploit becoming public knowledge, I didn't delve in to which versions they used, what was exposed, etc. etc. I just turned it off at the time to be extra safe.
Here is a simple .service file for that
[Unit] Description=NZBHydra2 Daemon Documentation=https://github.com/theotherp/nzbhydra2 After=network.target
[Service] User=XXX Group=XXX Type=simple # Set to the folder where you extracted the ZIP
WorkingDirectory=/opt/Nzbhydra2
# NZBHydra stores its data in a "data" subfolder of its installation path # To change that set the --datafolder parameter: # --datafolder /path-to/datafolder
ExecStart=/opt/Nzbhydra2/nzbhydra2 --nobrowser
Restart=always
copy it as nzbhydra2.serverice to /etc/systemd/system then systemctl enable nzbhydra2.service
Make sure you're up to date with nzbhydra. From their release notes:
v3.11.2 (2021-01-31)
Fix Fix a websocket issue when using a reverse proxy. Should've tested that better... If you're running NZBHydra behind a reverse proxy please see https://github.com/theotherp/nzbhydra2/issues/683#issuecomment-770444576.
If you've configured black hole folders in the downloading config you can send results from the download history there. See https://github.com/theotherp/nzbhydra2/issues/685
See https://github.com/theotherp/nzbhydra2/issues/647
I'll refer to issues in the changelog when they're triggered by a github issue.
Disclaimer: Results may be skewed as my accounts with some providers have API limits that I do hit on a regular basis. This was over the last 2 months with mostly TV Shows and Movies being searched for.
See also... https://github.com/theotherp/nzbhydra2/wiki/Indexer-results-uniqueness-score
>I use hydra but unless it has changed (or I've misunderstood) the stats aren't super useful. If it searches multiple indexers and each returns a result hydra will just pick a random "winner".
Winners might be random but the indexer score rates uniqueness of results. You might have a high overlap between 2 indexers (across torrents or nzbs) and they will get a lower score compared to times when only one of them gets a hit. Their documentation details how the scoring works.
I use a combination of the score and unique downloads to help understand which ones I use the most and should hold on to dearly ;)
Hope this helps the OP!
I'd recommend using NZBHydra2, premiumizer, Jackett (for torrent searches), and some Usenet indexers to get the full value out of a Premiumize subscription. Usenet is much better than torrents for some things, such as music.
Are you running this in Docker? Did you just update your nzbhydra2? Seems to be a somewhat rare issue that pops up. I had the same problem earlier in the week when I jumped from 3.8.0 to 3.8.1.
In my case, I'm running it in Docker, on top of FreeNAS 11.2 (RancherOS). The solution I found somewhere on github (Link here) suggested to keep your config files, and delete the "config/database" .db files, then restart. That won't kill your config/indexers, but WILL delete your history, naturally.
Since that would be destructive and I would lose the history, I tried the "simpler" method - I restarted the VM that runs docker. Not "docker-compose down" but restarted the actual VM.
All services popped back up without issue, including hydra2. Hopefully it's as simple as that for you!
For those looking for a more detailed explanation of what SNI is and why this is happening, I put some blurb here - repasted below.
>It lets the client say what hostname it's attempting to connect to when negotiating a TLS session with the server. Before SNI you needed a unique world routable IP address for each domain name you wanted to provide an HTTPS connection for on your server.
> This was fine when NZBGeek were exposing their own API directly, they just set it to use the default certificate for api.nzbgeek.info and it worked if the client used SNI or not.
> Now however they have moved the API behind Cloudflare, cloudflare uses a single set of IPs to represent literally hundreds of thousands of domain names, SNI simply must be provided or Cloudflare hasn't got a clue what certificate to use in the TLS negotiation.
> Essentially SNI does for the TLS part of HTTPS what HTTP/1.1 did for plain old HTTP, lets you have multiple domain names hosted on one IP address.
> Unfortunately it looks like at some point in the past NZBGeek didn't work if you had SNI enabled, perhaps their server didn't have the extension configured or something, and on 2nd September 2017 NZBhydra2 added an explicit disabling of SNI for nzbgeek in this commit - that now actively breaks NZBGeek for NZBHydra2.
Turn up logging to trace and come back with some trace logs !download (see auto mod reply) may help
/all being you are configuring jackett at the all endpoint, meaning you are adding jackett once as a whole and not creating a jackett entry for each indexer.
Hydra2 details here; you’ll still need jackett
https://github.com/theotherp/nzbhydra2
Basically you connect jackett to hydra2 (it will pull from config) and then have hydra2 configure sonarr/radarr (it will push the config) all done magically via the API
Please read https://github.com/theotherp/nzbhydra2/wiki/Tutorial-(Indexers,-newznab,-API,-*arr,-etc.)
Long story short: Hydra needs to be added twice, once as a usenet indexer and once as a torrent tracker. Click the "API?" button in the config to see the correct URLs.
I would recommend using NZBHydra2 to have a history of your previous searches, since this would also not be tied to the device alone. I have created a feedback board posting for you on the feature request though: https://feedback.lunasea.app/74
https://github.com/theotherp/nzbhydra2/issues/515
Supplying the apostrophe caused issues. You can enable it in the settings.
Edit: Actually I thought /u/TheOtherP added a setting for it, but I might he mistaken.
I had the same problem until I updated Hydra on my Pi4 to version 2.25.0 today. I did not use the automatic update because it apparently cannot overwrite some files (see https://github.com/theotherp/nzbhydra2/issues/566). So I downloaded the ZIP file and unpacked it in the Hydra folder. To verify that it's working I did a manual update query in Hydra (empty search field and max age set to 1) and added one of the entries that were found to Sonarr. In the next RSS sync it was picked up and downloaded. Unfortunately, I cannot really say why it was not working before. I did not find any issue in the Hydra Github that could explain that update queries were no longer working. I also did not see anything in the logs that would explain that behaviour.
Will fix this in the next version although I don't know why this would appear now as that part of the code hasn't been changed in ages...
For now just download the latest release from https://github.com/theotherp/nzbhydra2/releases/tag/v2.23.0 and replace the file in the lib folder from there.
I also recommend you (OP) read https://github.com/theotherp/nzbhydra2/wiki/Tutorial-(Indexers,-newznab,-API,-*arr,-etc.)
The search made by hydra when being queried by Radarr is such that it doesn't return the release you want. You need to find out how the searches differ. It's most likely due to different categories being used or ID based queries vs. plain text.
I wrote a tutorial that explains the pros and cons and some concepts you should be aware of to properly use hydra: https://github.com/theotherp/nzbhydra2/wiki/Tutorial-(Indexers,-newznab,-API,-*arr,-etc.)
Because sonarr doesn't know what indexer is behind hydra and handles hydra like any regular indexer.
I suggest you read this: https://github.com/theotherp/nzbhydra2/wiki/Tutorial-(Indexers,-newznab,-API,-*arr,-etc.)
I have tried 2.10.2 and 2.10.1 and both are still giving me: "Migration from NZBHydra v1 was removed in version 2.10.3. Please manually download and run the latest version which supports migration, migrate that and then update."
I'll keep trying a few older versions, but maybe I'll just skip the migration altogether if this is sketchy.
Just an FYI: I also noticed I have to make the nzbhydra2 binary executable first via chmod +x -- that has been true on the latest, 2.10.2 and 2.10.1.
Yeah, that database is probably too large.
I suggest you try migrating to v2 because I don't support python based v1 anymore. Install https://github.com/theotherp/nzbhydra2/releases/tag/v2.10.2 and migrate your v1 instance from there (in this case you should use the option where you provide the db and config files directly).
As the db seems to be so big you need to increase the XMX value in the config and restart before you try the migration. See if that helps.
From the Hydra page https://github.com/theotherp/nzbhydra2/wiki/Memory-requirements
>If you run a machine with very little memory I recommend sticking with Hydra 1 which only takes about 60MB of memory compared to the about 200-300MB which Hydra 2 uses.
​
So ... use hydra1
I think that's old.. if you look at the hibernate config it appears as if it is h2 as /u/TheOtherP mentioned. Thank you though!
You need to manually update your instance by downloading the latest release and extract it into your hydra folder.
In the future please check https://github.com/theotherp/nzbhydra2/issues to see if your issue is already known.
Looks like you downloaded the sources instead of the release. Download the latest release and extract it anywhere. Put the wrapper in the same folder. Change into that folder and run the python file.
I suspect you are correct.
Also note that the vast majority of people in /r/Usenet refer to NZBHydra the application not that falsely named indexer site you are referring to. See /r/NZBHydra and https://github.com/theotherp/nzbhydra2
They changed the layout of their page and I need to update the code that parses their results. That takes time which I currently do not have. I'm tracking the progress for that here: https://github.com/theotherp/nzbhydra2/issues/286
Download the latest Linux release from github. Extract it anywhere. Run the executable.
Sorry, on mobile and don't can't be hassled to write more elaborate instructions. https://github.com/theotherp/nzbhydra2/releases/download/v2.2.0/nzbhydra2-2.2.0-linux.zip is the link to the file if you use that in the tutorial you linked you should be good to go.
I ended up just running
​
wget https://github.com/theotherp/nzbhydra2/releases/download/v2.2.0/nzbhydra2-2.2.0-linux.zip
​
to grab the zip, not sure why the latest URL is not working for me.
https://github.com/theotherp/nzbhydra2/blob/master/readme.md#how-to-run
From the readme: "You need Java Runtime Environment or OpenJDK (both >=8u101 or 9 or 10, not 11!)."
The newest version is nzbhydra2 and it is java, I don't see why it wouldn't work on MacOS. The old nzbhydra is python, which... also should work.
What makes you think it doesn't?
Edit: This issue implies it should work.
See this: https://github.com/theotherp/nzbhydra2/issues/96
Some setting in the DB would continuously write to the disk. I increased the delay for that but apparently it means that crashes during a write will corrupt the database. I haven't had time to do more research on the matter.
As /u/fryfrog wrote this is, unfortunately, a known problem although it only seems to affect a minority of users. I've never been able to reproduce it. I just had an idea which is described here: https://github.com/theotherp/nzbhydra2/issues/96#issuecomment-389294005 You could give that a try.
This is a known issue that the developer is having trouble tracking down. If you're up for it, there are some data gathering steps in the issue you can follow to help him figure it out.
Personally, I've setup my systemd unit file to limit nzbhydra2's CPU usage in the mean time.
sudo systemctl edit nzbhydra2 to create an override, with the following inside. If you have more than one CPU, the % can go up to that. So 4 CPUS, you could do 400% to max them all, 8 would be 800%. So my 50% is 50% of one cpu, not all 32 of mine.
[Service] CPUAccounting=true CPUQuota=50%
late. I use and love it. As others have said it makes it easier to search manually. But I manly use it so I only have to modify indexers in one app.
Also: Check out version 2 on github. The creator recently rewrote the app and search is much faster now.