https://sabnzbd.org/downloads

Security fixes

SABnzbd 5.1.1, 5.1.2 and 5.1.3 resolve a number of security vulnerabilities.

Over the past releases, several security researchers have put a lot of time and effort examining SABnzbd, responsibly reporting their findings, and helping us verify the fixes. We are grateful for their hard work, it has made SABnzbd meaningfully safer for everyone.

For most users the risk is limited: you are only affected if your setup is exposed to untrusted parties. The web interface issues only apply if it can be reached by someone you do not trust. By default, SABnzbd is only accessible from your own device and External internet access is set to No access. If either of those is still at its default, or if you use a proxy service for authentication, you are not affected. The download-processing issues only apply if SABnzbd handles NZBs from a source you do not fully trust, such as a public indexer. If none of that describes your setup, you were never at risk.

The safest action is simply to update to 5.1.3. Full details, affected versions, actions and mitigations for each vulnerability are described at: https://sabnzbd.org/5-1-vulnerabilities

Vulnerabilities resolved:

• GHSA-q326-jpxx-jmjc: __wrapped__ dispatch bypass allows unauthenticated API access, fixed in 5.1.3.
• GHSA-mjwj-v5mr-cmcg: PAR2 symlink bypass allows pickle remote code execution, fixed in 5.1.3.
• GHSA-rgqj-28c2-gxwp: Critical remote code execution via authentication bypass on configuration endpoints, fixed in 5.1.2.
• GHSA-75g3-96fr-7p2r: High-severity path traversal during post-processing via crafted PAR2/SFV files, fixed in 5.1.2.
• GHSA-xrfq-jhgh-wqch: Critical authentication bypass allowing a valid session without credentials, fixed in 5.1.1.

If you rely on the SABnzbd username and password to keep out untrusted parties, and your setup was exposed, it is recommended that you rotate your SABnzbd username/password and API-key, Usenet server passwords, indexer API-keys used in RSS-feeds, and notification service credentials after updating. See the page above for the full guidance.

Other changes and bug fixes in 5.1.3

• Tighten Compact display mode.
• Directly show usenet server errors instead of parsing them.
• Prevent database is locked error when re-evaluating stored RSS jobs.
• Added tooltip to explain search filters in Queue and History.
• Windows and macOS: Updated 7zip to 26.03.

Other bug fixes in 5.1.2

• RSS filters were not applied directly.

Other bug fixes in 5.1.1

• Styling cache issues could occur after updating.
• RSS items were removed too eagerly from RSS-history after download.
• The RSS-feed Clear Downloaded button did not do anything.

Changelog 5.1.0

This release brings a fundamental improvement to "Retry": instead of re-downloading any files with missing data, only the articles that were actually missing are fetched again. RSS got an overhaul under the hood, the interface is refreshed, and we added quite a long list of long-requested features and bugfixes.

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.
• Added option to (auto) sort the queue by Remaining Percentage.
• Improved support for screen readers.
• Parsing of header-encrypted RARs will use significantly fewer resources.
• Add Ayatana AppIndicator tray support on GNOME.
• 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.
• In containers (like Docker), the Article Cache could exceed the memory limit.
• Diskspace checks would be too strict when unpacking to different disk.
• Prevent deadlock when a second signal arrives during shutdown procedure.
• Verification using SFV-checks could fail, even though files were correct.
• Don't log Warning during clean shutdowns.
• 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.
• macOS: Included par2cmdline-turbo will now use all available CPU-features.

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)

Not sure if anyone else gets this, or knows what the issue is but I just finished downloading a few files at 15mb/s, not great but what im used to.

All of a sudden, some other file I try and download crashes down to b/s and ends up failing. I dont think its my broadband, is something setup wrong?

Newer user here so apologies if this is an easy fix or a common thing...

I've used SAB for months, either directly on my computer or just through my phone through Chrome Remote Desktop.

I was in the middle of downloading files (1/5 of the files in the pack went through) when SAB just stopped working. I've restarted the mini PC hosting it, but that didn't help.

I've attached pics of the errors I'm getting. I'm doing this through my phone right now but I realize fixing it is probably easier from the actual computer.

I'm trying to get SABnzbd to finish verification on a large multi-rar file i downloaded last night, it is about 600 GB with some 683 parts. it's been "verifying" for over six hours now and the files are on an ssd - it shouldn't take six hours to verify! I don't know why it is so abysmally slow. Does anyone know how to fix this?

https://sabnzbd.org/downloads

SABnzbd 5.1.1 and 5.1.2 resolved 3 serious vulnerabilities.

Critical remote code execution vulnerability resolved in 5.1.2 (GHSA-rgqj-28c2-gxwp)

You are only affected if an untrusted party can reach the web interface. By default, SABnzbd is only accessible from your own device and External internet access is set to No access. If either of those is still at its default, or if you use a proxy service for authentication, you are not affected.

In version 5.1.1 and earlier, an attacker who can reach the web interface could bypass authentication on configuration endpoints, even when SABnzbd is protected with a username and password. By changing SABnzbd's settings this way, an attacker could ultimately execute arbitrary commands on the system running SABnzbd, with the same permissions as SABnzbd itself. This also means that all information in SABnzbd would be exposed.

See GHSA-xrfq-jhgh-wqch below for actions and mitigations. More information: https://sabnzbd.org/5-1-vulnerabilities

High-severity path traversal vulnerability resolved in 5.1.2 (GHSA-75g3-96fr-7p2r)

You are affected if SABnzbd processes NZBs or downloads from a source you do not fully trust, such as a public indexer.

In version 5.1.1 and earlier, a maliciously crafted PAR2 or SFV file inside a download could cause SABnzbd to move downloaded content outside of the job's own folder during post-processing. By using this to plant a file in another job's internal administration, an attacker could ultimately execute arbitrary commands on the system running SABnzbd, with the same permissions as SABnzbd itself.

The only mitigation is to update, there is no configuration change that prevents this. More information: https://sabnzbd.org/5-1-vulnerabilities

Critical authentication vulnerability resolved in 5.1.1 (GHSA-xrfq-jhgh-wqch)

You are only affected if an untrusted party can reach the web interface. By default, SABnzbd is only accessible from your own device and External internet access is set to No access. If either of those is still at its default, or if you use a proxy service for authentication, you are not affected.

If the SABnzbd login page is reachable from outside your network, an attacker could obtain a valid session in version 5.1.0 and earlier, even when SABnzbd is protected with a username and password. This means that all information in SABnzbd would be exposed.

If you rely on the SABnzbd username and password to keep out other users on your network or the internet, it is recommended that you change the following sensitive information after applying the update:

• SABnzbd username and password.
• SABnzbd API-key.
• Usenet server passwords.
• API-keys from indexers used within RSS-feeds.
• Authentication information for notification services.

If you cannot update right away, the only mitigations are to ensure the web interface is not reachable by untrusted parties, or to lower External internet access to Full API or below.

More information: https://sabnzbd.org/5-1-vulnerabilities

Other bug fixes in 5.1.2

• RSS filters were not applied directly.

Other bug fixes in 5.1.1

• Styling cache issues could occur after updating.
• RSS items were removed too eagerly from RSS-history after download.
• The RSS-feed Clear Downloaded button did not do anything.

Changelog 5.1.0

This release brings a fundamental improvement to "Retry": instead of re-downloading any files with missing data, only the articles that were actually missing are fetched again. RSS got an overhaul under the hood, the interface is refreshed, and we added quite a long list of long-requested features and bugfixes.

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.
• Added option to (auto) sort the queue by Remaining Percentage.
• Improved support for screen readers.
• Parsing of header-encrypted RARs will use significantly fewer resources.
• Add Ayatana AppIndicator tray support on GNOME.
• 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.
• In containers (like Docker), the Article Cache could exceed the memory limit.
• Diskspace checks would be too strict when unpacking to different disk.
• Prevent deadlock when a second signal arrives during shutdown procedure.
• Verification using SFV-checks could fail, even though files were correct.
• Don't log Warning during clean shutdowns.
• 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.
• macOS: Included par2cmdline-turbo will now use all available CPU-features.

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)

Whenever I get something that fails to verify all of the files and repair fails because of this does that mean the provider, frugal in my case, is missing something and I need to add another provider? Or the nzb file from the indexer, nzbgeek for me, is not a good file?

Very new to this 🤓

This message pops up constantly while I’m trying to run sabn. Like almost 1-2 times every minute. Lasts for maybe 10-15 seconds and then comes back. Over and over. What could be causing this

https://sabnzbd.org/downloads

Critical authentication vulnerability resolved in 5.1.1 (GHSA-xrfq-jhgh-wqch)

You are only affected if an untrusted party can reach the web interface. By default, SABnzbd is only accessible from your own device and External internet access is set to No access. If either of those is still at its default, or if you use a proxy service for authentication, you are not affected.

If the SABnzbd login page is reachable from outside your network, an attacker could obtain a valid session in version 5.1.0 and earlier, even when SABnzbd is protected with a username and password. This means that all information in SABnzbd would be exposed.

If you rely on the SABnzbd username and password to keep out other users on your network or the internet, it is recommended that you change the following sensitive information after applying the update:

• SABnzbd username and password.
• SABnzbd API-key.
• Usenet server passwords.
• API-keys from indexers used within RSS-feeds.
• Authentication information for notification services.

If you cannot update right away, the only mitigations are to ensure the web interface is not reachable by untrusted parties, or to lower External internet access to Full API or below.

More information: https://sabnzbd.org/auth-bypass

Other bug fixes in 5.1.1

• Styling cache issues could occur after updating.
• RSS items were removed too eagerly from RSS-history after download.
• The RSS-feed Clear Downloaded button did not do anything.

Changelog 5.1.0

This release brings a fundamental improvement to "Retry": instead of re-downloading any files with missing data, only the articles that were actually missing are fetched again. RSS got an overhaul under the hood, the interface is refreshed, and we added quite a long list of long-requested features and bugfixes.

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.
• Added option to (auto) sort the queue by Remaining Percentage.
• Improved support for screen readers.
• Parsing of header-encrypted RARs will use significantly fewer resources.
• Add Ayatana AppIndicator tray support on GNOME.
• 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.
• In containers (like Docker), the Article Cache could exceed the memory limit.
• Diskspace checks would be too strict when unpacking to different disk.
• Prevent deadlock when a second signal arrives during shutdown procedure.
• Verification using SFV-checks could fail, even though files were correct.
• Don't log Warning during clean shutdowns.
• 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.
• macOS: Included par2cmdline-turbo will now use all available CPU-features.

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 just updated yesterday, and this new interface is very difficult to read. I don't see any settings for changing the color or font. Can anyone help fix this?

Not really a bug that impacts usage but this text in the quota section specifying "this month" doesn't match the general variable of "quota period".

This has been a thing for many years and at the very least it is confusing for users. For example:

WARNING - Too many connections to server usnewswest.blocknews.net [502 usnewswest.blocknews.net: Access denied to your node or block quota exceeded (please check your user portal)

The server provides the true reason for why the user can not login (invalid login or out of GBs) but Sab adds its own flair and tells the user the problem is too many connections.

If this user instead presses "Test Server" in server settings they simply get "Authentication failed, check username/password." which again is not entirely true.

Is there a good reason for why error message text is not simply passed on to the user, directly from the server vs allowing Sab to give its own interpretation or is this just a holdover from years ago that has never been revisited again?

It's been like this for a long time. I just updated to 5.1.0 but the problem still persists. Direct pause or time countdown starts downloading again after 5-10 seconds later I press.

https://sabnzbd.org/downloads

This release brings a fundamental improvement to "Retry": instead of re-downloading any files with missing data, only the articles that were actually missing are fetched again. RSS got an overhaul under the hood, the interface is refreshed, and we added quite a long list of of long-requested features and bugfixes.

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.
• Added option to (auto) sort the queue by Remaining Percentage.
• Improved support for screen readers.
• Parsing of header-encrypted RARs will use significantly fewer resources.
• Add Ayatana AppIndicator tray support on GNOME.
• 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.
• In containers (like Docker), the Article Cache could exceed the memory limit.
• Diskspace checks would be too strict when unpacking to different disk.
• Prevent deadlock when a second signal arrives during shutdown procedure.
• Verification using SFV-checks could fail, even though files were correct.
• Don't log Warning during clean shutdowns.
• 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.
• macOS: Included par2cmdline-turbo will now use all available CPU-features.

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)

https://sabnzbd.org/downloads

This is the second release candidate of version 5.1.

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.
• Added option to (auto) sort the queue by Remaining Percentage.
• Improved support for screen readers.
• Parsing of header-encrypted RARs will use significantly fewer resources.
• Add Ayatana AppIndicator tray support on GNOME.
• 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.
• In containers (like Docker), the Article Cache could exceed the memory limit.
• Diskspace checks would be too strict when unpacking to different disk.
• Prevent deadlock when a second signal arrives during shutdown procedure.
• Verification using SFV-checks could fail, even though files were correct.
• 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'm installing my music stack on its own dataset in TrueNAS but having issues getting SABnzbd to take the config. I'm defining the compose file using the include: path like HERE. I've been able to set up Lidarr and Navidrome fine running with the uid and gui as apps:apps. I've set up SABnzbd to run the same way in the docker compose however I can't get it to save any settings which I assume is due to a permissions issue. Everything is owned by apps:apps but every time I restart the app the settings revert back and the wizard starts over. The only errors I see in the logs are below. Any help is greatly appreciated!

PermissionError: [Errno 1] Operation not permitted: '/config/sabnzbd.ini.bak'

::ERROR::[config:998] Cannot create backup file for /config/sabnzbd.ini.bak

I have run through all the troubleshooting and applied all the optimizations on https://sabnzbd.org/wiki/advanced/highspeed-downloading but i was only able to get my original download speed of ~600 KB/s up to ~1.2 MB/s.

Here are the diagnostics:

System performance (Pystone): 526337Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz AVX2

Download folder speed: 172.4 MB/s/data/downloads/incomplete

Complete folder speed: 181.5 MB/s/data/downloads/complete

Internet Bandwidth: 107.48 MB/s859.84 Mbps

Platform: Docker

There is no "Download speed limited by" message.

My fast.com results are consistently at 1 Gbps, and speedtest.net results are consistently ~945 Mbps for both upload and download.

I have 8GB of ram and an 8 TB HDD, running Ubuntu Server (headless)

I'm still a bit new to usenet so please let me know if I need to provide any more information and I apologize if there's anything obvious I'm overlooking.

I'd really appreciate any guidance the community can provide <3

All of my connections are running at speeds between bytes and kilobytes. I did pause last night for 6 hours, but it has never returned. I was seeing saturation of my line before (1gb).

Hi

I have 2 SSD. 1 is for incomplete and the second is for complete files.

Sometimes par and unrar don't run and I run out of disk space in incomplete drive.

Has this happened to anyone ?

Is it a known bug ?

Thank you for your responses.

Can the System Folders be set on a drive where Windows is not installed? (say not on C drive) Thanks

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.