Anyone else using the betas w/Sonarr?

[Eurisko]

I just upgraded to Newsbin 6.70 beta 7. I haven't been able to do much backwards testing, due to timing. Also, I had too many variables to rule out what the cause was.

I built a new server for Plex, Newsbin & Sonarr. Stood it all up, everything seemed to work, except the communication between Sonarr & Newsbin. Sonarr would show, and log that it sent the info to Newsbin, but Newsbin did nothing. Nothing would show as if it got the message. I rolled back to Newsbin Beta 5, and it started working perfectly. I went back to beta 7, it broke again, so I went back to beta 5. (That was the last beta I happened to have a quick copy of.)

The reason I can't say for sure what the real cause was, is due to how many things changed at once. I moved everything to a much larger server. Sonarr decided to auto-update in the middle of this. It could be 2.0.0.3953 (came out March 12, 2016) of Sonarr broke beta 7, or beta 7 broke it. I'm not sure which. I was just curious if anyone else has a similar setup with Newsbin and is having this same issue.

Thanks!

[Quade]

1 - If you go into the Sonaar option for downloader what happens if you "Test" the connection?

2 - Do you see Newsbin listing on the port you set in the remote NZB Options?

3 - Are you just using the API key on both ends?

[18:33:45] DEBUG SbServer: Read Request GET /api?mode=history&start=0&limit=30&category=tv&apikey=57bb53f14f2869b0a3fdb2d850743d36&output=json HTTP/1.1
[18:33:45] DEBUG GET /api?mode=history&start=0&limit=30&category=tv&apikey=57bb53f14f2869b0a3fdb2d850743d36&output=json HTTP/1.1

Using 6.70B7, I see this in the logging tab when I have logging turned up to debug. You should see something like that. The fact an update breaks it makes me think there's some issue with your security software.

[Eurisko]

1 - If you go into the Sonaar option for downloader what happens if you "Test" the connection?

2 - Do you see Newsbin listing on the port you set in the remote NZB Options?

3 - Are you just using the API key on both ends?

[18:33:45] DEBUG SbServer: Read Request GET /api?mode=history&start=0&limit=30&category=tv&apikey=57bb53f14f2869b0a3fdb2d850743d36&output=json HTTP/1.1
[18:33:45] DEBUG GET /api?mode=history&start=0&limit=30&category=tv&apikey=57bb53f14f2869b0a3fdb2d850743d36&output=json HTTP/1.1

Using 6.70B7, I see this in the logging tab when I have logging turned up to debug. You should see something like that. The fact an update breaks it makes me think there's some issue with your security software.

1.) It succeeds on b5, b6 & b7
2.) Yes
3.) I have tried with/without.

It works perfectly on B5 & B6. When I go to B7, it stops. I cranked up logging, and the log messages look the same, it just doesn't start, or show up in the filelist at all in B7. I can repeat it by going back to B5 or 6, and it works. As soo as I install B7, it fails 100% of the time. I excluded the process from Defender. Even tried disabling it. (New system, haven't had a change to install my normal security suite yet).

Any suggestions?

[Quade]

Any suggestions?

I'd suggest sticking with B6 for now.

It you manually feed an NZB from Sonaar what do you see in the logging tab?

Edit: You know NZB Filters apply to Sonaar sourced NZB's too right? Just something worth checking.

[Eurisko]

I don't have anything fancy. No filters, just a pretty vanilla install of Newsbin. No watchlists, etc. It lives mainly for the occasional manual search, and to be Sonarr's automation piece.

Manually triggering a file from Sonarr yields the same thing, I see in the log entries where it comes across, but Newsbin doesn't appear to do anything with it.

[Quade]

Manually triggering a file from Sonarr yields the same thing, I see in the log entries where it comes across, but Newsbin doesn't appear to do anything with it.

Ok thanks. I'll check it out.

[cat_man]

I can confirm B7 breaks Sonarr integration. Works fine as a Blackhole but not with Sabnzbd interface. B5 and B6 both work with Sabnzbd integration.

[Quade]

Yeah I'm looking at it.