Support Forum

If your indexer supports bookmarks/carts, might be safer to configure SAB to access your bookmarks via an RSS feed. This means SAB will pull your NZBs instead of the indexer pushing them.

Did you add your Usenet providers as servers?

Have you tested them?

Version 4.4.0 has a fix for this. Suggest you upgrade your SABnzbd.

Anyway, currently here is what I have been doing. I goto my indexer and get an nzb file. I then move this file to the sabnzbd+ watcher. sabnzbd+ then puts everything in order and that results in a functional result. My problem is that, sometimes, the functional result is not functional. When that h...

The RSS thing is useful if you habitually spend time on your indexers, browsing for things you'd like to download. If the indexer offers a bookmarks/cart facility for your account on their site and have an API for this, the downloading process becomes more convenient. Enter the RSS details for your ...

safihre wrote: ↑November 26th, 2024, 6:38 am Sounds like a bug indeed. Can you great a Github ticket?

... and done. Issue #2979.

Hi guys, running SABnzbd 4.3.3 from source on Debian 12.8. Just noticed this one. Seems odd, please let me know if this is a bug or by-design. My RSS checking interval is 20 minutes. I jumped to the SABnzbd RSS feed page, saw there were 2 minutes to-go until the next scan time. But, I couldn't wait,...

Could be… you’d need to check the files with ‘mediainfo’, or whatever they use on macOS.

It may just be those media files can’t be played with your media player.

Hi. :) No special settings are required, I use NZBFinder, DogNZB and a bunch of other indexers without issue. It may be the original media wasn’t ripped correctly. Try a few other downloads and see if you can find a few that work. It’s also a good idea to have more than one Usenet server susbscripti...

No, don’t type the “select all” bit…

I’m not sure sherpa is the right solution for you. You really must have some familiarity with the shell to use the sherpa package manager. If you’re new to this, the learning curve is quite-steep. It’s not something you can pickup in 5 minutes.

Hey I just noticed, you appear to have the older SABnzbd QPKG installed too. You should really only have a single SABnzbd QPKG installed.

Please uninstall all SABnzbd QPKGs that appear in your App Center, then use sherpa to install the correct one.

No, but a good first effort.

You must enter exactly what is shown in my previous post in the code block. Don’t change anything.

Can you please examine the service log for the SABnzbd QPKG?

You can view this with: This log should show what happens when QTS attempts to start SABnzbd.

That old NAS and its low RAM will take a while to start your QPKGs. How long have you waited after the reboot began? Have you confirmed the out-of-memory killer hasn’t been active?

Hi Michael, and welcome to the forum.

SABnzbd will be automatically started after a reboot, unless you manually stopped it before the reboot via the QTS App Center (stopping a QPKG in the App Center also disables it, preventing startup on next reboot).