Hi guys,
I’ve been using Sonarr for some time and it has been working great. Historically, I added all of my usenet indexers directly into Sonarr and I never missed a show.
In an attempt to make my setup more “secure” I installed NZBMegasearch on the cloud (OpenShift), and configured NZBM with all of my indexers. Sonarr now only connects to NZBM via SSL (which then connects to my indexers via SSL).
I noticed that Sonarr was starting to miss some shows (some shows would be fine). Shows would air, and then even when running a manual/automatic search, nothing would show up or download. If I were to add one indexer back to Sonarr (so it would contain NZBM and Dognzb), the shows that were missing would immediately download and everything would be back to normal.
I looked around the long and found the following error: http://pastebin.com/pMBJvNRp . Any assistance would be greatly appreciated - thank you!
Edit: I also tried the following fix, to no success: https://www.reddit.com/r/usenet/comments/26fsn3/nzbmegasearch_not_playing_nicely_with_sickbeard/
There are a couple fixes that need to be applied to megasearch for it to work with Sonarr, the megasearch GitHub repo has them in issues/pull requests.
Your issue could potentially be SSL related, but I haven’t see this error (and with mono not running in debug a lot of info is missing).
While megasearch can work with Sonarr it will never work properly for season searches (and by extension series searches), because it doesn’t support paging of results.
We recommend not using megasearch because of the fixes that need to be applied and that its not being maintained any longer.
Ok, thank you!
Do you by chance know of any other piece of software that can aggregate newsnab indexers like NZBMegasearch?
No AFAIK it was the only one that did it.
What security are you hoping to achieve with this setup?
If someone were looking into me they would see me connecting to known Usenet indexers. They wouldn’t necessarily see what I pulled from the site (or from Usenet), but by using NZBM on the cloud I’m one step removed. One more layer of obfuscation.
It really depends if NZBM also proxies the NZB fetch requests or it gives the link to the NZB from the indexer. In the former case you are obfuscated, in the latter you’re just as screwed.
Sonarr’s logs would shows you what is happening there in debug logs.