Closed elmerfds closed 7 years ago
Yeah mylar doesn't distinguish between nzbhydra and newznabs - so it would assume anything on a local address wouldn't have to adhere to a rate limit.
I recently added in the opposite (domain with local bypass), so adding in the opposite (local ip without local bypass) shouldn't be too difficult. I'll try and get this out tonight / tomorrow depending on available free time.
Thanks
Good to go in latest development commit. You just need to update the name of the newznab entry within Mylar to let it know it's an nzbhydra instance that you want to enforce the limit for. You do this by just appending on the words [nzbhydra] to the end of the Newznab Name field for the entry that is for your nzbhydra like so :
@evilhero that didn't work :(
Updated to the latest commit on dev, Done the changes as you requested to the nzbhydra newznab entry, had a look at the logs, no pauses, also see the screenshot from NzbHydra.
Test done by adding a new comic with 16 issues, all 16 issues were searched in about 3 mins.
Start of log from Mylar when status of issues set to 'wanted', still no pauses before doing the search.
Sorry, I just saw that it wouldn't work - give me a few moments to fix it
Sure
It works! thanks for sorting this out so quickly.
I've been using Mylar with Nzbhydra for a long time and I just switched to using the localhost address of my NzbHydra setup instead of my web address and I've noticed that Mylar doesn't do any pauses like it would do when you use any other indexer (like pauses to stop hammering the server, I've seen requests in the space of a few seconds hitting nzbhydra back to back). If I switch to the web url of Nzbhydra (www.example.com/nzbhydra) then only it starts to treat NzbHydra as a normal indexer.
In the logs I've noticed the following "local domain bypass for NzbHydraLocal is active." Is there an option hidden somewhere to turn that bypass off?