What are /r/nzbhydra's favorite Products & Services?

From 3.5 billion Reddit comments

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.

nzbhydra2-2.23.0-linux.zip

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)

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).

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

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.

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!

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.

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.

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.

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!

https://github.com/theotherp/nzbhydra2/blob/master/core/src/main/resources/config/application.properties

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.

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!)."

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%

192.* should be allowed but it's possible that it gets confused by the .09 IP address. I have no idea why that would happen.

See https://sabnzbd.org/wiki/extra/access-denied.html

If you leave that option empty you will be asked for the category whenever you send a download to sabnzbd in hydra.

Otherwise hydra will not set a category when sending a result to sabnzbd so sab will have to decide which category to use. See https://sabnzbd.org/wiki/configuration/2.3/categories for that. That's more a question related to sab than to hydra.