Support Forum

Seems maybe something changed in this check in Python. This code is ancient. Seems using os level checking is doing something different. I implemented a change in the check for this for a next patch. You can work around this by setting any folder for your Complete folder, then setting your desired d...

I will see if I can add this feature to 5.1.0.

The blocked extensions are different, they already abort the job during the download. So the whole download wouldn't never be finished. You only want to clean them up after the download?
Running a script takes milliseconds.

AI is hallucinating, it was never supported. But do you mean blacklist, which aborts download if a file is detected during download, or the Cleanup list? That one cleans up after download. Because if you just want to Cleanup after successful download, then AI can super easily make you a post process...

How do you add the files to SABnzbd? Double click? Or Watched Folder?

I think you or your browser has auto-filled the 119 port (which is normally used for usenet servers) in the settings for SABnzbd webhosting itself. You can run this in the Terminal: /Applications/SABnzbd.app/Contents/MacOS/SABnzbd --console --server 127.0.0.1:8080 After this SABnzbd will start on it...

You should be able to post now.

Open the Terminal app and copy paste the command.
Then hit enter.
It will probably display something of an error.

Can you try this and post the output?
Run SABnzbd on macOS via Terminal using /Applications/SABnzbd.app/Contents/MacOS/SABnzbd --console

It's toggled by the icon in the top right of the queue. It's either on or off, that's why it keeps showing. You must have clicked the icon at some point.

It's a bug indeed, it happens when not using English as language.
We will fix.

Yeah exactly, that's what that option is for.

Can you enable Debug logging in the Status window?
At least we will have logs if it happens again. You can sent them to me at safihre@sabnzbd.org if it happens again.

Seems you maybe also have something configured for Cleanup list? In Config Switches?

Yes. It's probably your database being corrupted.
Go to the location of your sabnzbd.ini, shutdown Sab, then delete history.db and restart Sab.
You'll loose your History, but it shouldn't be stuck anymore.

Only stability changes.

Did you ever reported this problem with b1? Because we are not aware of it...