SABnzbd Forums

Hello all, I recently updated my Sabnzbd to 2.3.4 after being on a much older version for like 8 years (my friend installed it a while back.) Since installing, my files just sit there. I believe it has something to do with the way I have it set up. After updating, I got a message saying that I needed to create a new category, so I added one called tv. Since then, maybe 30% of my files actually download.

I have checked my connection in Status and I have checked that my test server is connected.

I use Supernews with Sonarr for tv shows and some manual downloads through DogNZB and OMGWTFNZBs. I'd appreciate any assistance.

Playing with it now, it looks like I have better luck manually downloading files than I do downloading through Sonarr (though it works, sometimes.) In my Sonarr settings, I have the Category set as TV to match the category I made on Sabnzbd, but this didn't exist before in the old version of Sab I was using for years, so I believe this is where the hiccup is in my flow.

Sonarr won't let me put nothing or default for that category, which is what prompted me to add a tv category. Even though Sonarr says adding a category is optional, leaving it blank or entering "Default" causes the test to fail. Only entering "tv" makes the test succeed, but the file does not download.

Did you maybe set jobs to be added Paused in the Categories settings?
You can always try this: https://sabnzbd.org/wiki/faq#freshstart

safihre wrote: ↑August 26th, 2018, 1:54 pm Did you maybe set jobs to be added Paused in the Categories settings?
You can always try this: https://sabnzbd.org/wiki/faq#freshstart

Thanks for your reply. I don't think so. My Sabnzbd Categories tab looks like this:

Category: tv, Priority: Default, Processing: Default, Script: blank, Folder/Path: blank, Indexer Catoegories/Groups: blank

I would then suggest to try the fresh start, it should keep your history just reset your settings.

Alternatively you could also download the logs. First switch logging to Debug in the Status window and then after it happens again, click Show Logging.
(this assumes you use the Glitter interface)
Maybe there's something in there about stalling connections maybe?