I've successfully ran NBP and Sonarr since April, but due to a issue with a Microsoft Update (anniversary?), I had to format and reinstall. I recall that it was pretty easy to set up the first time, but it's been two days of googling and futzing around, and no joy.

Very easy and straightforward, and very much not working. At this point, I feel like I could bring in a monkey to fling poo at the monitor and it would be equally as effective towards reaching my objective: I'm just completely lost. Please throw me a bone here. I'd like to get this set up by Monday, as I go in for surgery Tuesday, and I doubt this will get any easier for me after that.

Here is what I'm actually seeing, in case I'm clicking on something wrong.

I'm changing the port entries to match, of course, and I've tried several different ones. Upon following the directions in the post linked to above, I get the following error after testing: "Test was aborted due to an error: Unable to connect to SABnzbd, please check your settings" It doesn't seem to matter if I have SSL enabled or not in Sonarr. I use SSL in NBP in communicating with my Usenet servers.

If I get this fixed, I'm screenshotting it and hardcopying it, I swear.

1 - You need an API key at the very least. Sonarr won't work without one. Just make something up. It has to be the same on both ends.

2 - Is sonarr running on the same machine?

3 - Don't use SSL between Newsbin and Sonarr. If they're running on the same machine, the packets never leave your PC.

4 - You might use "127.0.0.1" instead of "Localhost" on both sides. Localhost is supposed to be a shortcut for that 127 address but I prefer 127...

5 - Make sure both ports are the same.

6 - Might disable you firewall and see if that allows the connection through.

Your specific error suggests a port problem or that you have SSL enabled. I'd use "Netstat -ant" before starting Newsbin and see if something is listening on 8000 already. If it is, use some other unused port. I'd set it in Newsbin, then restart Newsbin and type "Netstat -ant" from a command prompt. You should see something listening on the port you picked.

Well, I messed about and did what you said, and the test function worked. We'll see if i can get any files to DL, though. So far, I haven't been about to get anything to DL. I'll see what happens overnight.

They're just random filenames. There's no actual way to group them so, they go as individual files.

As long as the PAR files download they should work. There's someone on our IRC channel that uses that style NZB's and he says they work.

I see the PAR blocks counting up meaning Newsbin is recognizing the files. This isn't a problem as long as Newsbin can rename and unrar the files. The block counts should tell you. This issue isn't sonarr or Newsbin. It's an artifact of both how the files are posted and the search engine you're using to feed Sonarr.

You need to put your Newsbin key into your user profile for the pics to work.

Quade wrote:They're just random filenames. There's no actual way to group them so, they go as individual files.

As long as the PAR files download they should work. There's someone on our IRC channel that uses that style NZB's and he says they work.

I see the PAR blocks counting up meaning Newsbin is recognizing the files. This isn't a problem as long as Newsbin can rename and unrar the files. The block counts should tell you. This issue isn't sonarr or Newsbin. It's an artifact of both how the files are posted and the search engine you're using to feed Sonarr.

You need to put your Newsbin key into your user profile for the pics to work.

It's not working for me as each individual rar and par file downloads and sits there but it doesn't unrar.

It downloaded perfectly for me but then again I expected that. I think it's because I have multiple news servers. It didn't clean up after itself very well.

The next step is for me to damage the NZB a bit to simulate only having a single server missing parts of the file and see if there's a way to make it still work. The NZB's work as long as the first chunk isn't missing. If the first chunk is missing determining what PAR the files belong to becomes difficult because of the obscured filenames.

I don't know why it's only happening with NZB's from PFMonkey either when they insist there's nothing wrong at their end.

The reason they don't compact together is because the "Poster" field is randomized. I've been thinking about code changes for the sonarr interface in order to handle this. The NZB's are pretty shitty in that the filenames don't match the filenames of the actual files and the posters are randomized which breaks compaction but they should still work for you. They work for me.

I'd suggest watching the block counts and seeing if the block counts add up properly. If they block counts + repair counts exceed the needed blocks, if should repair and unrar.

The only thing I don't understand is why they download and unrar for me but not for you.