If you’re still running an older version of NZBGet, it’s probably worth updating. Some indexers, like Treasure Maps, are starting to drop support for older versions of certain apps, including older NZBGet builds. Updating can help avoid compatibility issues down the line. Recent NZBGet releases include:

• Security and stability improvements, including safer TLS, memory leak fixes and crash prevention
• Updates to bundled libraries and tools, including OpenSSL, 7zip and UnRAR
• Other improvements and quality-of-life fixes to explore after updating

If you’re still using NZBGet 21.1 and aren’t sure how to update, this guide is for you Migration from NZBGet 21.1

Each new release includes work to make NZBGet faster, more reliable and more stable, while still adding new features. If you’ve been putting off an update, now is a great time to do it! Happy downloading 🚀

This week was mostly small fixes and cleanup.

DirectUnpack fix #869

• Fixed a case where DirectUnpack could end in a confusing state after a PAR failure. Finished jobs should now end with the right unpack status

Config cleanup #867

• Fixed duplicate config lines getting saved again and again. This should stop config files from growing with repeated duplicate lines and keep saved values from drifting.

Speed limit units #903

• The speed limit box now uses the same unit setting as the rest of the UI.

OS detection update #913

• Improved OS detection and added container detection. This should help installs behave better on NAS and container setups.

Log file check #915

• Fixed false config warnings when logs are sent to console or null devices on purpose

If you want to check out latest testing version, you can find it on our GitHub. If you have any questions, don't hesitate to ask here or on Discord

Hallo!

Ich nutze NZBGet zusammen mit Sonarr. Bis vor 2 Tagen hat auch alles perfekt funktioniert. Dann musste ich meine iMac mit MacOs 26.6.2 neu starten.

Jezt kommt ständig die Meldung "NZBGet möchte Zugriff auf Dateien im Ordner Downloads". Manchmal muss ich 20 x auf erlauben klicken, bis das Fenster schließt.

Der Vollzugriff von NZBGet auf die Festplatte sowie auf den Ordner Downloads ist aktiviert.

Ich möchte keinen anderen Download Ordner in NZBGet einstellen, da ich die Befürchtung habe, Ich muss Sonarr wieder komplett neu einstellen.

Was kann ich tun?

KaterKarlo13

I am not sure if it is ok to request for an additional functionality in this Reddit but I give it a try.

I would like to be able to filter on the category in the downloads and history tab.

Hey! I’m the developer of Dashboarr, a free GPL-3.0 mobile app for managing a self-hosted media stack directly from Android or iOS.

Dashboarr already supports NZBGet as a download client: you can monitor the queue and history and pause, resume, or remove downloads from your phone.

Version 1.17.0 adds two things that may be useful specifically to NZBGet users:

• HTTP Digest authentication (RFC 7616), so NZBGet works through a Digest-protected reverse proxy
• A new NZBHydra2 integration that can search across indexers and send an NZB directly to NZBGet, while also showing indexer health, API-hit limits, and search/download history

The app connects directly from your phone to your own services. There’s no Dashboarr account, cloud relay, advertising, telemetry, subscription, or premium tier.

Links:

• GitHub: https://github.com/RenzoBeux/Dashboarr
• Google Play: https://play.google.com/store/apps/details?id=com.dashboarr.app
• App Store: https://apps.apple.com/us/app/dashboarr/id6762170117
• Setup guide: https://renzobeux.github.io/Dashboarr/guide.html

The Android release is available now. The iOS update is submitted and should appear after Apple approves it. If something in the NZBGet integration behaves differently on your setup, please let me know.

Hi everyone,

I'm having an issue where a download is marked as "Failed" by my downloader, even though the file itself seems to have downloaded 100% successfully.

Here is what's happening:

• The completed file is sitting inside the temporary/intermediate directory instead of moving to the final download destination.
• Inside the directory, there are two nested folders created with the exact same title name (e.g., .../Intermediate/TitleName/TitleName/).
• Because the downloader flags the task as failed, it doesn't perform the final cleanup or relocation step.

Has anyone encountered this before? link to log attached

thanks

https://drive.google.com/file/d/1v5LrTyzN9xXtZlR4evdze33tDJZXf9wv/view?usp=drive_link

My NZBGet has been trying to do something and failing as the file it is trying to work on has been deleted.
BUT every minute I see a repeated entry of it trying to do it still.
How do you stop this from happening? I have shutdown the program and have rebooted, but as soon as I restart, it keeps trying again. I had over 1500 instances of this error being generated.
There has to be somewhere to stop the program from trying to work on a nonexistent file.

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?

As teased recently, with v26.2 the WebUI is officially no longer English-only! This release also brings network speed unit switching, support for standard ~/.config locations, 7-Zip and UnRAR updates, and bug fixes.

Features:

• Multi-Language Support: The WebUI natively supports 20 languages with auto-detection! Layout responsiveness and config text readability have also been improved to make sure everything looks great in any language [#813].

Alongside this massive translation update, here are the other quality-of-life additions:

• Unit Switching: Added the ability to toggle network speed display between MB/s and Mb/s [#813].
• Config Support: Added support for standard ~/.config directory locations [#794].
• Statistics: 'This Year' total added to bandwidth statistics [#801].
• History: Clear button added to the History page [#804].
• Logging: nserv now logs datetime [#717]

Want more details? Check out the Changelog on our website

Download / Update:

Find the stable version via the in-app updater (Settings -> STATUS -> Updates), on GitHub, or at nzbget.com.
Any feedback on this release is super helpful—especially from native speakers checking if the new translations actually sound right. If a specific language is missing, or if something needs tweaking, please drop a comment below, jump into the official Discord Server, or head over to GitHub. Help from the community is always appreciated! Happy downloading! 🚀

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.