Support Forum

What are your local ranges set-to?

Run this on the server: ... adjusting the port number if-required.

This is a simple loopback query. It will show you the location SABnzbd is using for its config file.

Something you should report to the Radarr folks?

Sounds like an indexer. You’re not trying to add it as a Usenet server, are you?

sander wrote: ↑February 13th, 2024, 11:23 am So SABnzbd does not stop randomly, but as it is instructed by an authorized client.

Nice catch @sander.

Do I need to run it from source to leverage systemd so it's always running as a service? No, you can run any version this way. The service script is only to manage starting and stopping an application automatically during OS startup and shutdown. You don't need it however. Just run the SABnzbd exec...

Can you guide OP how to do that? Already covered in the wiki: https://sabnzbd.org/wiki/installation/install-off-modules Just need to use the SystemD service file: https://github.com/sabnzbd/sabnzbd/blob/master/linux/sabnzbd%40.service Mine looks like: # copy or _hard_link to # Debian: /lib/systemd/...

Although, running SABnzbd from source on Debian isn't a big deal. I've been running it that way for quite a while now.

Follow-up:

It seems there are a handful of apps available: https://www.westerndigital.com/en-au/su ... -cloud-nas

We were both right though.

Hi and welcome to the forum.

I don't think this NAS supports installation of user applications, it's an entry-level NAS only.

https://www.cnet.com/reviews/wd-my-cloud-2-tb-review/

edit: oops, too-late.

I even post those release notes on the QNAP forum. I should probably read them a little closer though.

Ah, I now realise this selection box was moved from the front SABnzbd page, into Config -> Switches -> Queue -> On queue finish script.

So, not a bug, just a change.

Might be this? https://github.com/sabnzbd/sabnzbd/comm ... b7f5a7f00a

It looks like 'interfaces/Glitter/templates/include_menu.tmpl' had some changes related to end-of-queue operations.

update:

• works in 4.2.0Alpha1
• works in 4.2.0Alpha2
• not working in 4.2.0Alpha3
• not working in 4.2.0Beta1

If filesystem.py hasn't changed, maybe it’s the interface?