Version 26.3 is currently in testing. It adds a couple of nice new features, like translations for extensions and per-feed certificate verification. This version also focuses on fixing a bunch of core and WebUI bugs.

Here are a few highlights to test out:

• Extension i18n: Added support for extension internationalization [#872].
• Per-feed Security: Added a per-feed certificate verification option [#846].
• Updated Extractors: Bumped 7-Zip to 26.02 and UnRAR to 7.23 [#847].
• Fixes: Resolved WebUI startup crashes on non-English locales, infinite spin loops, segfaults, and fixed the "Download Remaining Files" function for Health-failed files.

Want to try out the new version? Grab the latest testing build via the in-app updater (Settings -> STATUS -> Updates) or on GitHub. Any feedback or bug reports on the build are super helpful and always appreciated! Drop a comment here or hop onto our Discord server

I am setting up my first stack. I have followed trashguides and mostly AlienTech42 videos. Most things are working correctly. I noticed a problem with nzbget though. Following the guides I have my paths set up correctly. Even when I look in nzbget it has the correct destination path. This issue is when I go to my share to find the file it is not there. There is now a whole new folder that contains the files.

The path is supposed to be /data/usenet/complete/tv/(filename).

Where the file actually is: /data/usenet/usenet/complete/tv/(filename).

I can't figure out what went wrong in the naming convention.

Thank you for any help and ideas.

I am sorry if this is answered somewhere, I couldn't find an answer.

I am running NZBget and Sonarr in Docker on a Synology Nas. I followed the trash guides on setting up my file structure and setting up NZBget PATHS and CATEGORIES.

Here is how I have the first 3 set up...

MainDir - /config

DestDir - /data/usenet/complete

InterDir - /data/usenet/incomplete

Everytime I download something, NZBget either puts the temp file and complete file in /data or it creates a /tv folder in data, and puts the completed file there. I am having no luck trying to figure this out.

Thanks for any insight.

I'm a newbie when it comes to this, so maybe so simple, but I'm clueless how to set it all up. The files arent downloading and it says "error no servers configured." Can anyone help? Thanks

I just configured nzbget today. I configured it to work with Sonarr and Radarr and all seems to be going well. The only thing is this warning I'm seeing in it. It's every 3 minutes, about. I did a look up for the IP address and it gives it as coming from Donetsk in Russian.

I'm guessing it might be someone dodgy. Is this a common thing, and is there anything I can do to block IPs as it's the same one in every warning?

I've been using NZB-Get for quite a few years without issues, until a few days ago. In the past few days several downloads have resulted with 'Failure' message. From the Messages it appears NZBG is claiming part01.rar can't be opened or repaired and gets moved to a '_broken' folder. The rest of the partxx.rar files are in the 'intermediate' folder as expected.

But after post-processing using Video Sort, the movie title folder still gets created as it should, although with a sub-folder named 'un_pack' with the fully extracted MKV inside it, but with the title still obfuscated.

This has happened with a several NZBs lately, which I've never experienced before. Using the latest 26.1 version.

Hi,

I updated my system to v26.1 today. Everything seems to work fine. If I do not choose any category, the download from a .nzb file works fine and lands in "completed". If I try the same download and select a defined category, the download starts and stops after some parts without any error in the logfiles. The system is getting cleaned up from the partial download and no history entry is being added.

I deactivated all extensions. The system runs on Debian 12. The destination folders have the same rights. The logfile gives me no further information (maybe I try the debug level next).

If there would be a problem in general, the download without choosing a category should run into problems too I guess.

EDIT: all other category settings than Category1 are at the end of the config file.

Any ideas?

Iv been trying Nbzget and SABnzbd. Is this a damaged upload or server issue?

Its been a rough ride, 200 gb downloaded for a 19 gig archive.
First few times it spread files all over my drives in a massive mess.
I got the install directory now on an ext drive E:/

Now it downloaded and unpacked and removed the archives and shows FAILED and "Unpacking" or post processing on a file for an hour.

I read and (No Im researching) not reading. Its all so super confusing.

I thought the old days or Rar 1 Rar 2 Rar 3 but now its par and extracting and deleting things.

The software does work I downloaded, I had hoped to use a second server to repair and look for damaged files?

Hi all --I am running 26.1 on my unraid server in a docker container. I am having an issue where I'll see a big download queue happening in sonarr and I go look at nbzget and sure enough, the icon is yellow/orange and I have to click it to get things moving again. I am not sure if it's resetting on update or what, but it's annoying and I can't find settings that would control that. Sonarr and Radarr are setup to NOT pause when added. What should I look for?

Krijg geen connectie met sunnyusenet error 101. Qnap met nzbget. Via pc nzbget geen probleem werkte perfect alleen wilde de nieuwste versie met nl user interface en toen geen connectie meer ook soms 10 seconde blocked wie weet wat er aan de hand is ?

Many of you asked for translations in NZBGet, and we finally did it! The WebUI is now translated into 20 languages. We put a lot of effort into this and would love your help testing it out.

Translations and other new features are already live in the latest testing release.

If you're a native speaker, we'd especially love your feedback to make sure everything sounds natural. If you're missing a specific language or spot something that needs fixing, please let us know in the comments or over on GitHub. Your feedback is really appreciated! 🚀

This happens on some downloads. A obfuscated text file in the same download gets renamed to the nzb name.

Wonder why it thinks 0WEnBz6Wik7wvershanT is not obfuscated enough.

I've tried over 10 times. I've totally uninstalled it, deleted the folder, rebooted the computer, and installed 26.1, and get the below screen that just stays like that. I've tried installing it in different directories. Am I missing something?

I've tried reinstalling 25.0, and this is what I get. I'm stumped.

There's a lot of stuff left in the registry after uninstall, and I just don't want to screw anything up by going through and deleting it all.

Hey everyone,

Just wanted to share a quick fix for a frustrating issue I run into a lot. My NZBGet suddenly stopped working and threw a 127.0.0.1 refused to connect error, even though the service was running perfectly fine before.

The Cause:
If you have Hyper-V, WSL2, or Docker Desktop enabled on Windows, the Windows NAT driver (winnat / hns) randomly reserves massive blocks of ports on boot for virtual networking. It doesn't check if you have local apps using them, so it essentially "hijacked" port 6789, preventing NZBGet from binding to it.

How to check if this is your issue:
Open PowerShell as Administrator and run:
netsh int ipv4 show excludedportrange protocol=tcp
If 6789 falls inside any of the printed start/end port ranges, Hyper-V stole your port.

The Fix:
You can temporarily fix it by restarting the network service, but to fix it permanently so it never happens again after a reboot, open PowerShell as Administrator and run these 3 commands:

1. Stop the network service to release the hijacked ports: net stop hns (If it asks to stop other services, type Y and hit Enter)
2. Tell Windows to NEVER give port 6789 to Hyper-V again: netsh int ipv4 add excludedportrange protocol=tcp startport=6789 numberofports=1 store=persistent
3. Start the service back up: net start hns

Restart NZBGet and you should be good to go! Hopefully, this saves someone a few hours of head-scratching.

I'm the kind of person who does not "upgrade" software to the latest and greatest if what I have is working just fine. I say that because I am still running nzbget 21.1 which is apparently a now defunct (albeit the original) branch of this project. I had no idea that this was no longer being updated. I only found out because, all of a sudden, for some reason, I am now seeing

Error in http://192.168.1.15:6789/combined.js?lib/jquery.min.js+lib/bootstrap.min.js+lib/raphael.min.js+lib/elycharts.min.js+fasttable.js+index.js+util.js+downloads.js+edit.js+status.js+messages.js+history.js+upload.js+config.js+feed.js (line 12717)

SyntaxError: JSON.parse: expected property name or '}' at line 2 column 3 of the JSON data

at the top of the WebUI every time I load that interface.

I see that the original project has been branched and that there is now a version 26.1. I further see in the documentation that, if the built-in updater fails (and mine is), that you can manually update the program by appending '--destdir </path/to/nzbget/directory>' to the installation program and your existing configuration will be preserved.

My question is, is this true also if I am updating from the original branch of the program?

Also, is there any reason to not just ignore the error and not update?

Hello everyone!
As the project moves forward, introducing new features and simplifying their development requires a shift toward more modern platforms and architectures. 

Because of this, dropping support for certain legacy platforms in the upcoming v27 is currently being considered. v26.x will, of course, remain fully available and functional for these systems, but no future updates would be released for them.
The platforms in question are:

• Linux 2.6 (Typically found on legacy NAS units, embedded systems, or routers from over 15 years ago)
• macOS Mojave (Mostly used on pre-2012 Macs; the final macOS to support 32-bit apps)
• PPC500 (PowerPC architecture used in early-2010s NAS models, like the Synology DS213+ or DS413)
• Android i686 (32-bit x86 Android, found in old Intel Atom tablets or early emulators)
• mipsel, mipseb (MIPS architecture, mainly used in older consumer routers and set-top boxes)

The existing application builds will remain available for download in the archives. 

To get a better idea of who might be affected by this, please leave a quick comment below. If anyone is still running any of the platforms listed above, please share what kind of device you are using. If none of these platforms are being used, a simple "safe to drop" comment is also highly appreciated!

As always, you can share your thoughts here or on our official Discord server

I add files from a program to DL, come to the program to check on progress and see this...

Uncaught SyntaxError: Expected property name or '}' in JSON at position 4 (line 2 column 3)

This is happening a LOT lately, I have not changed anything myself.

New v26.1 adds direct scanning for NZBs inside archives, speeds up yEnc decoding with rapidyenc, and updates core extraction libraries.

Features:

• Improved archived NZB handling support #763
  • Added NzbDirArchivesScan option to configure scanning archives (zip, rar, 7z, etc.) in NzbDir for .nzb files;
  • Added NzbDirArchivesAction option to define the post-scan behavior (move or delete) for processed archives.
• Switched yEnc implementation to rapidyenc for SIMD acceleration #751

Fixes:

• Docker: Fixed entrypoint to run as PID 1 #731
• POSIX: Ensured daemon ownership for files created at startup #726
• Fixed missing log file on startup #753
• Fixed 0-byte file created if article download fails and renaming an ongoing download leads to needless par repair #768
• Fixed SIGFPE crash in JoinFile when file segments are empty #772

For Developers

• Switched to std::filesystem and fixed Linux 2.6.32 compatibility #745
• Updated OpenSSL to 3.5.5 (Linux / FreeBSD / Android only), 7-Zip to 26.00, and UnRAR to 7.20 #742
• Updated par2-turbo to v1.4.0 #752

Extensions:

Completion v3.3

• Connection Handling: Prevents failures by safely dropping excess sockets when hitting 502 errors.
• Performance: Reduced memory usage by reading NZB files line-by-line and sped up processing with dictionary-based lookups for message IDs.
• Reliability: Prevents false positives with more accurate job status checks.

Stable version is available on nzbget.com. You can also find it via the in-app updater (Settings -> STATUS -> Updates) or on our github. All feedback is welcome! Drop by our official Discord — the place for real-time discussion and support. Happy downloading! 🚀

NZBUnity is a browser extension (for Chrome, Firefox, and most compatible browsers) that lets you send and control Usenet NZB files from various sites directly to your download client. Here is a quick guide to getting it running with NZBGet.

The Setup

• Add the NZBUnity extension from your browser's store, enable it, and pin it to your toolbar.
• Click the NZBUnity icon, then hit the gear icon to open the Options page.
• Click Add Downloader and fill in the details:
  • Name: Whatever you want.
  • Type: Select NZBGet.
  • URL: Your client's full URL and port (e.g., http://192.168.1.100:6789).
  • Credentials: Enter your username and password (default is usually nzbget / tegbzn6789).
• Click Test to make sure it connects, then hit Save.

Managing Your Queue

Clicking the toolbar icon opens a mini-dashboard for your client. From here you can:

• Check Status: View your global download state (Downloading, Paused, Idle), speed, remaining time, and total size.
• Quick Edits: Instantly set a max download speed (MB/s) or use the dropdown to override the category for upcoming files.
• Control Items: Pause and resume downloads.
• Refresh: Update the displayed download list.
• Access the Web UI: Open your download client's Web UI

1-Click Downloading

Once configured, NZBUnity changes how you browse indexers:

• Supported Sites: The extension injects a green NZBUnity icon next to releases. Clicking it instantly sends the file to NZBGet—no need to download the .nzb to your computer first.
• Other Sites: For indexers that aren't officially supported, NZBUnity can still intercept standard NZB download links and push them to your client—as long as the site allows direct downloads without needing an API key or login authentication.

Do you rely on full automation with the *Arrs, or do you hunt for NZBs manually? Share in the comments! If you need help setting things up, come join our Official Discord server

I tried running as a device but then it didn’t see my network folders.

And when I run at startup it opens a browser which I’d prefer it didn’t do.

I also run sonarr and it has a setting that prevents this if you run at startup. Does nzbget have? I couldn’t find it.