I have 2 providers, a main unlimited one, and a block one. So I think the priority of the unlimited one is 0, correct? What is the priority of the block one?

Thnx

i keep getting flagged when downloading audiobooks. especially older ones. not sure if im missing something or if there is a way to whitelist this? it really seems to flag older files in the mp3 format

example error...
In "Robin_Hobb_-_Farseer_Trilogy_2_-_Royal_Assassin__2010__MP3" unwanted extension in RAR file. Unwanted file is Robin.Hobb.-.Farseer.Trilogy.2.-.Royal.Assassin/Audiobooks For Free.URL

Hi, I get the error in Sabnzbd whenever I try to open a nzb download link with sabnzbd. Does anyone know how to fix this?

I get broken files with SABnzbd and can't repair with MultiPar. When i download with Easynews there are no broken files anymore.

Is this a configuration problem or what am i missing?

https://sabnzbd.org/downloads

This is the first release candidate of version 5.1. Like many other projects out there, we were able to use the shiny new AI tools to add quite a lot of long-requested features!

New features in 5.1.0

• Refreshed the interface.
• When Retrying a job, only the actually missing articles are tried again. This only works for jobs downloaded in 5.1.0 (or newer).
• RSS items are now stored in the database instead of on disk.
• New RSS Age rule to filter jobs based on their age.
• Downloaded RSS items are cleared from the RSS database after 3 days.
• Added support for filename and path pattern matching to the Cleanup List.
• Unwanted extensions will also be removed after unpacking.
• Allow job setting changes directly from Extra queue columns.
• Added support for unpacking .tar files during post-processing.
• Improved anonymization of the logs when using Show Logging.
• Added SAB_FILES environment variable to Post-processing scripts, listing all files that resulted from the job.
• New Servers will default to 16 connections instead of 8.
• Use media duration as part of Ignore Samples detection.
• Improved support for screen readers.
• Parsing of header-encrypted RARs will use significantly fewer resources.
• Removed redundant INSTALL.txt file.
• Dropped support for Python 3.9.
• Windows and macOS: Updated Python to 3.14.6, Unrar to 7.23 and 7zip to 26.02.

Bug fixes in 5.1.0

• Prevent incorrect warnings about non-writeable directories.
• Files unrelated to job could get removed by the Cleanup List logic.
• Prevent path traversal in orphaned job APIs.
• Disk Full errors from unrar were not handled gracefully during unpacking.
• Memory leak could occur during article decoding.
• Windows: Uninstall would not remove Settings or Windows Service.
• Windows: Warn for OS-limit if more than 1024 connections are configured.
• macOS: AppleDouble files could result in failures in Moving stage.
• macOS: Restarting the application resulted in Terminal window.

Upgrade notices

• You can directly upgrade from version 3.0.0 and newer.
• Upgrading from older versions will require performing a Queue repair.

Known problems and solutions

• Read ISSUES.txt or https://sabnzbd.org/wiki/introduction/known-issues

Code Signing Policy

Windows code signing is provided by SignPath.io using a SignPath Foundation certificate.

About

SABnzbd is an open-source cross-platform binary newsreader. It simplifies the process of downloading from Usenet dramatically, thanks to its web-based user interface and advanced built-in post-processing options that automatically verify, repair, extract and clean up posts downloaded from Usenet.

(c) Copyright 2007-2026 by The SABnzbd-Team (sabnzbd.org)

I upgraded to 1gb fiber today from 500mbps and now when I do a download, I literally cannot browse. It downloads around 112-125 and I just can't browse. This never happened when my speed (actual internet speed) was lower and my downloads were slower.

Am I braindead and missing something here? Some help would be greatly appreciated.

https://sabnzbd.org/downloads

This is the third beta release of version 5.1. We will probably add (a few) new features in upcoming testing releases, but we already wanted to share the current improvements with you!

New features in 5.1.0

• Refreshed the interface.
• When Retrying a job, only the actually missing articles are tried again. This only works for jobs downloaded in 5.1.0 (or newer).
• RSS-items are now stored in the database instead of on disk.
• Downloaded RSS-items are cleared from RSS-database after 3 days.
• Add support for filename and path pattern matching to the Cleanup List.
• Allow job setting changes directly from Extra queue columns.
• Added support for unpacking .tar files during post-processing.
• Improved anonymization of the logs when using Show Logging.
• New Servers will default to 16 connections instead of 8.
• Use media duration as part of Ignore Samples detection.
• Parsing of header-encrypted RAR's will use significantly less resources.
• Removed redundant INSTALL.txt file.
• Dropped support for Python 3.9.
• Windows and macOS: Updated Python to 3.14.6, Unrar to 7.23 and 7zip to 26.02.

Bug fixes in 5.1.0

• Prevent incorrect warnings about non-writeable directories.
• Files unrelated to job could get removed by the Cleanup List logic.
• Prevent path traversal in orphaned job API's.
• Disk Full errors from unrar were not handled gracefully during unpacking.
• Memory leak could occur during article decoding.
• Windows: Uninstall would not remove Settings or Windows Service.
• Windows: Warn for OS-limit if more than 1024 connections are configured.
• macOS: AppleDouble files could result in failures in Moving stage.
• macOS: Restarting the application resulted in Terminal window.

Upgrade notices

• You can directly upgrade from version 3.0.0 and newer.
• Upgrading from older versions will require performing a Queue repair.
• Downgrading from version 4.2.0 or newer to 3.7.2 or older will require performing a Queue repair due to changes in the internal data format.

Known problems and solutions

• Read ISSUES.txt or https://sabnzbd.org/wiki/introduction/known-issues

Code Signing Policy

Windows code signing is provided by SignPath.io using a SignPath Foundation certificate.

About

SABnzbd is an open-source cross-platform binary newsreader. It simplifies the process of downloading from Usenet dramatically, thanks to its web-based user interface and advanced built-in post-processing options that automatically verify, repair, extract and clean up posts downloaded from Usenet.

(c) Copyright 2007-2026 by The SABnzbd-Team (sabnzbd.org)

Hey everyone. Not sure when this started happening but my speeds have slowed to about 70 MB/s when I used to get ~110 MB/s (Gigabit connection). This is on a synology DS920+, SABnzbd running in Docker. Doing the status test in SAB shows adequate folder speeds and the correct internet bandwidth, but then it maxes at about 70 MB/s during an actual download, including the test download in SAB. I've attached the speed diagnostics in the comments.

I know speeds were fine 2 months ago, so sometime since then the speeds have slowed. CPU utilization on the server is ~30% and RAM is ~50% during downloads. Tried different ethernet cable and same thing. Doing an iperf test to my server from my laptop shows the correct bandwidth (~900 mbps).

The speeds were originally slower (~45 MB/s), but they improved once I changed the articles per request from 1 to 10. Connections are set at 20.

Tried different usenet server and same issue. Same for SSL vs no SSL. Hard drives are WD80EFAX Red Plus NAS drives, no SSD in system.

Any ideas? Could a recent update have caused this?

Ok full disclosure. I signed up to Easynews about 2 years ago and for the most part I just download through their web interface and sometimes through SabNZB but I was reading and someone mentioned another provider called Frugal which has good retention. I was frustrated that stuff that's 2.5 years was not working. I went to setup Frugal after signing up and discovered I have SabNZb setup to use Usenetserver which I forgot to cancel.

If you see, I have them all activated and I'm getting over 90MB/sec which I never did before. On Usenetserver I'd get at best 40MB/sec so my question is, since I have them all selected, is pulling the files as a bonded connection or is Easynews really that fast? I don't see in this screenshot where it says which is default so I'm assuming they are all working in tandem.

I'm looking to setup a download serverwhere multiple people can "drop" .nzb files for the client to grab.

I was thinking about doing this with a Google drive folder or similar.

Is this possible and if so how is best to implement it?

Well that's kind of self explanatory but let's suppose you grab something that is 10GB but only have 11GB, doesn't Snzb require at least buffer to extract before deleting the archive to free up the space? How does that work?

I've been running SAB along with a variety of *arrs for a good long time and it's pretty much been a reliable appliance for me. Recently though I've been seeing it hang while calling a postprocessing script and when I investigated, I found that the source RAR file was encrypted and hadn't had files pulled out for the post processor. This almost never had happened to me in the past although SAB did occasionally detect and delete downloads that were encrypted - not so these. When SAB hits these the entire queue backs up and nothing processes while this is hung.

I had thought something had changed in the ecosystem but some of the files I'm downloading are years old, so this made no sense to me. Digging around searching I've seen comments that "all RAR are encrypted" and that the "NZB file will contain the password". Is this true? Since the NZB file get deleted when the download starts, I've not investigated any of them. I use multiple indexers so if this is the case perhaps one of them has made a change and that could explain why this isn't consistent. Has anyone else seen this? I can usually cancel the download and get it to work on another file but occasionally it takes multiple attempts.

I don't think this is a bug but suspect a provider problem or something I've somehow broken on my side. I'm on 5.0.4 currently, in a container on unRAID, and would love to get my reliability back. Troubleshooting tips much appreciated! I'd like to figure this out without having to download the same NZB file from each of my indexers if possible. I use multiple indexers and multiple UseNet providers...

https://sabnzbd.org/downloads

This is the second beta release of version 5.1. We will probably add (a few) new features in upcoming testing releases, but we already wanted to share the current improvements with you!

New features in 5.1.0

• Refreshed the interface.
• When Retrying a job, only the actually missing articles are tried again. This only works for jobs downloaded in 5.1.0 (or newer).
• RSS-items are now stored in the database instead of on disk.
• Downloaded RSS-items are cleared from RSS-database after 3 days.
• Add support for filename and path pattern matching to the Cleanup List.
• Allow job setting changes directly from Extra queue columns.
• Added support for unpacking .tar files during post-processing.
• Improved anonymization of the logs when using Show Logging.
• New Servers will default to 16 connections instead of 8.
• Parsing of header-encrypted RAR's will use significantly less resources.
• Removed redundant INSTALL.txt file.
• Dropped support for Python 3.9.

Bug fixes in 5.1.0

• Prevent incorrect warnings about non-writeable directories.
• Files unrelated to job could get removed by the Cleanup List logic.
• Windows: Uninstall would not remove Settings or Windows Service.
• Windows: Warn for OS-limit if more than 1024 connections are configured.
• macOS: AppleDouble files could result in failures in Moving stage.
• macOS: Restarting the application resulted in Terminal window.

Upgrade notices

• You can directly upgrade from version 3.0.0 and newer.
• Upgrading from older versions will require performing a Queue repair.
• Downgrading from version 4.2.0 or newer to 3.7.2 or older will require performing a Queue repair due to changes in the internal data format.

Known problems and solutions

• Read ISSUES.txt or https://sabnzbd.org/wiki/introduction/known-issues

Code Signing Policy

Windows code signing is provided by SignPath.io using a SignPath Foundation certificate.

About

SABnzbd is an open-source cross-platform binary newsreader. It simplifies the process of downloading from Usenet dramatically, thanks to its web-based user interface and advanced built-in post-processing options that automatically verify, repair, extract and clean up posts downloaded from Usenet.

(c) Copyright 2007-2026 by The SABnzbd-Team (sabnzbd.org)

I am attempting to DL some shows. When DL it goes great for about have of the file at runs at 500 MB. Then it comes up saying articles are missing and boom it slows to a crawl and takes forever to DL.

I'm using nzbgeek and drunkenslug for my indexers.

Backbone is newsgroupdirect, newshosting, supernewsgroup, and viper newsgroup.

Running version 5.1 beta of SAB. This issue was present on 5.0.4 as well. Used an older version and was having issues with that one as well.

Troubleshooting attempted:

1. restarted computer running programs

2. Verified network drivers are up to date.

3. Tried setting the Maximum line speed to different speeds but no luck

4. verified Fast_fail is enabled

5.Abort jobs that cannot be completed is checked.

I'm currently at a loss on what to do from here.

So I used to run sabnzbd on my Synology NAS. Last year I moved it (uninstalled NAS version installed a Windows version) onto an M150 NUC. No problems with either. I nuked the Synology install. Long story short I want it back on the Synology NAS so I reinstalled it (fresh brand new install).

Now I keep getting "API key missing, please enter the API key from Config->General into your 3rd party program ::ffff:172.30.0.1 [GuzzleHttp/7]

I cannot for the life of me figure out where the heck this is coming from. I uninstalled every SABConnect+++ extension I had on every device in the house. I'm assuming 172.30.0.1 is a docker container IP address as looking at the containers they have a similar IP range. I literally have NO docker containers using this IP address there are some that are 172.30.0.2 and other 0.x numbers but no 172.30.0.1. So WTF is trying to ping the new install? I'm open to suggestions for what else. I run some of the "arrs" but they're at a 192.168.x.x IP address and correctly configured and play nicely dropping NZBs into sabnzbd.

Help. Thanks!

I am running ZFS on a Crucial BX500, and my speed always goes to 0 every minute. I tried downloading on NVME, my speed never dropped at all. It was also on Btrfs, so it's not an issue with the fs. Should I sell this SSD and get another one? If yes, can I use a SATA drive, or should I just buy an m.2 drive and an m.2 PCIe card?

This in todays log; repeats about six times:

Traceback (most recent call last):
  File "cherrypy_cprequest.py", line 659, in respond
  File "cherrypy_cprequest.py", line 711, in _do_respond
  File "cherrypy_cpreqbody.py", line 985, in process
  File "cherrypy_cpreqbody.py", line 564, in process
  File "cherrypy_cpreqbody.py", line 225, in process_multipart_form_data
  File "cherrypy_cpreqbody.py", line 215, in process_multipart
  File "cherrypy_cpreqbody.py", line 624, in from_fp
  File "cherrypy_cpreqbody.py", line 640, in read_headers
ValueError: MIME requires CRLF terminators: b'------WebKitFormBoundaryx484147748721--'

Hey guys i wanted to make a Manga folder but i dont know how and if it works i want that if i download a manga lets say jjk i want it to get stored on a different folder than my series and movies does anyone know how to do that

https://sabnzbd.org/downloads

This is the first beta release of version 5.1. We will probably add new features in upcoming testing releases, but we already wanted to share the current improvements with you!

New features in 5.1.0

• Refreshed the interface.
• RSS-items are now stored in the database instead of on disk.
• Downloaded RSS-items are cleared from RSS-database after 3 days.
• Add support for filename and path pattern matching to the Cleanup List.
• Allow job setting changes directly from Extra queue columns.
• Added support for unpacking .tar files during post-processing.
• Improved anonymization of the logs when using Show Logging.
• Dropped support for Python 3.9.

Bug fixes in 5.1.0

• Prevent incorrect warnings about non-writeable directories.
• Windows: Uninstall would not remove Settings or Windows Service.
• Windows: Warn for OS-limit if more than 1024 connections are configured.
• macOS: AppleDouble files could result in failures in Moving stage.
• macOS: Restarting the application resulted in Terminal window.

Upgrade notices

• You can directly upgrade from version 3.0.0 and newer.
• Upgrading from older versions will require performing a Queue repair.
• Downgrading from version 4.2.0 or newer to 3.7.2 or older will require performing a Queue repair due to changes in the internal data format.

Known problems and solutions

• Read ISSUES.txt or https://sabnzbd.org/wiki/introduction/known-issues

Code Signing Policy

Windows code signing is provided by SignPath.io using a SignPath Foundation certificate.

About

SABnzbd is an open-source cross-platform binary newsreader. It simplifies the process of downloading from Usenet dramatically, thanks to its web-based user interface and advanced built-in post-processing options that automatically verify, repair, extract and clean up posts downloaded from Usenet.

(c) Copyright 2007-2026 by The SABnzbd-Team (sabnzbd.org)

Has this happened to anyone before? Until a couple of days ago, I had a good setup e.g everything was working fine. I noticed my last few files had downloaded fine, been removed from the history list of SabNZB but the downloaded files were nowhere to be seen. I checked my Incomplete downloads folder and have seen that any file I download seems to just be dropped there. When I look at the folder, it’s full of RAR and Par files. Looks like the system I’m using (Sonar, RADAR and SabNZB) isn’t working as it should. Radar and Sonar show the file status as “Downloading” . This has happened to me for the last 10 files I’ve tried to download - all seem to be healthy and good download sources.

Hi All,

I tried posting this in the unRAID sub but it was removed for not being relevant. I assumed it was an unRAID issue but maybe it's a docker or specific container issue.

Although I've had my unRAID server running for a few years now I'd consider myself a beginner (I'm not familiar at all with linux or much command line prompts). I have the *arrs setup wtih SABNZBD as my downloader and Homebridge and Homeassistant for home automation. It had been running exactly as I expected for a while but within the past year or so I've been experiencing a lot of issues with nearly all of the containers randomly unable to connect to the internet.

I say random because I haven't been able to trace what is causing the issue but typically if one container is impacted then the other containers are as well. But also sometimes they're not.

The issue seemed to start after I upgraded to unRAID 7 but I also rebuilt my server at the same time so I can't specifically point to either causing the problem.

The biggest issue I have is that when SABNZBD is downloading a file, the download speed completely stall for a period of time and then start to pick back up. This can happen multiple times during a download and continue for hours. I'll also receive errors in SABNZBD that it has failed to connect to my providers. I have multiple providers with different backbones that can all report the error at the same time (image below).

I'm also having similar issues in other containers. I've also noticed that Sonarr and Radarr will be unable to search for files - either manually or automatically. There have been times when I'll manually search for a few episodes of an show in Sonarr without issue and then 10 seconds later Sonarr fails to return any results.

When I'm streaming a show or movie via emby to one of my AppleTVs, it's not uncommond for the stream to complete stop and return to the previous menu on my AppleTV. Sometimes I can resume the file and other times it will not start up at all. I've also experienced this with VLC on the same AppleTV.

All other network devices work fine. I've tested downloading the same NZB file on a Windows PC while my unRAID download has stalled and it will finish just fine (without any slow downs).

I'm assuming this is specifically a network issue on my unRAID server. As I mentioned earlier, I'm a bit of beginner with all of this. I've ensured IPv4 only is enabled, have 1.1.1.1 and 8.8.8.8 as my DNS servers. The server is hardwired to an Omada switch (other devices are running just fine on the switch). Any help would be greatly appreciated.

https://sabnzbd.org/downloads

In this fifth major release of SABnzbd, we included:

• Smarter (and potentially faster) downloads with NNTP Pipelining and Direct Write.
• Reliability gains from a reworked cache and safer processing.
• A significant number of bug fixes and platform updates.

Features and bug fixes in 5.0.4

• RSS feed modifications no longe require clicking Apply Filters.
• Fixed RSS priority handling.
• Server Test could block the queue.
• Use reduced progress bar width in Compact layout.
• Replaced unreliable directory access check.
• Prevent crash in idle-jobs check.
• Jobs with invalid date would show as Fetching.
• Windows and macOS: Updated Python to 3.14.5 and Unrar to 7.22.

Features and bug fixes in 5.0.1, 5.0.2 and 5.0.3

• Fetching NZB's failed on new installations.
• Queue entries from older versions now load correctly after upgrading.
• nzo_id now uses GUIDs to prevent duplicates.
• Updating to 5.0 now succeeds even when duplicate nzo_id values exist.
• URL fetching no longer crashes when duplicate jobs are present.
• Default RSS priority is now applied correctly.
• Duplicate filenames no longer cause queue stalls.
• IPv6 binding now works correctly for the Web interface.
• The On queue finish action now executes reliably.
• Saving the post-processing queue no longer throws errors.
• Directory creation now handles existing directories gracefully.
• Windows and macOS: Updated Unrar to 7.21 and 7zip to 26.01.

New features in 5.0.0

• Added support for NNTP Pipelining which eliminates idle waiting between requests, significantly improving speeds on high-latency connections. Read more here: https://sabnzbd.org/wiki/advanced/nntp-pipelining New servers will have Articles per request set to 2 by default. Existing servers need to be manually changed to use NNTP Pipelining.
• Implemented Direct Write to optimize assembly of downloaded files. Read more here: https://sabnzbd.org/wiki/advanced/direct-write
• Post-processing scripts will always be executed, even for failed jobs. Make sure to check the status of the job in your scripts!
• Removed Special setting empty_postproc as it is no longer needed.
• Complete redesign of article cache.
• Improved disk speed measurement in Status window.
• Reduced delays between jobs during post-processing.
• Improved handling of disks getting full.
• Diskspace check will now include Category-specific folders.
• If a download only contains .nzb files, the new downloads will include the name of the original download.
• No longer show tracebacks in the browser, only in the logs.
• Dropped support for Python 3.8.
• Windows: Added Windows ARM (portable) release.
• Windows and macOS: Added HTML version of the Release Notes.
• Windows and macOS: Updated Python to 3.14.4, Unrar to 7.20, par2cmdline-turbo to 1.4 and 7zip to 26.00.

Bug fixes in 5.0.0

• Check before download could get stuck or fail to reject.
• Several stability changes for the core download process.
• If only par2 files were missing, jobs could get incorrectly aborted.
• No error was shown in case NZB upload failed.
• Correct mobile layout if Full Width is enabled.
• Handle passwords that exceed Unrar's password limit.
• Aborted Direct Unpack could result in no files being unpacked.
• Encrypted RAR detection could sometimes fail.
• Unwanted extension check was unreliable on passworded downloads.
• No longer exclusively lock all directory operations.
• Improved handling of non-NFC unicode filenames.
• Sorting of files inside jobs was inconsistent.
• Linux: No longer break test-data in the release package.
• Windows: Tray icon disappears after Explorer restart.
• macOS: Slow to start on some network setups.

Changes to default settings for new installations in 5.0.0

• Default Minimum Free Space for Temporary Download Folder set to 500M.
• Enabled verify_xff_header setting by default.

Upgrade notices

• You can directly upgrade from version 3.0.0 and newer.
• Upgrading from older versions will require performing a Queue repair.
• Downgrading from version 4.2.0 or newer to 3.7.2 or older will require performing a Queue repair due to changes in the internal data format.

Known problems and solutions

• Read ISSUES.txt or https://sabnzbd.org/wiki/introduction/known-issues

Code Signing Policy

Windows code signing is provided by SignPath.io using a SignPath Foundation certificate.

About

SABnzbd is an open-source cross-platform binary newsreader. It simplifies the process of downloading from Usenet dramatically, thanks to its web-based user interface and advanced built-in post-processing options that automatically verify, repair, extract and clean up posts downloaded from Usenet.

(c) Copyright 2007-2026 by The SABnzbd-Team (sabnzbd.org)

have 1 gig ethernet no vpn running on zimaos docker setup. newshosting with 100 connections

i usually avg 110 MB/s, this has been going on for a few days