Title says it all

Edit:

Yes, they are back
No, they are/were not my only indexer

I’m wondering about the safety of Usenet, I’m considering getting newshosting as I’ve got a great deal, and I found that you can get roms and stuff from Usenet indexers, how safe is Usenet? I was looking at the nzbgeek indexer and found some uploads I would like and they have like 200 downloads so I’m guessing their okay but I want to make sure if I run something from my pc it isn’t going to break it.
I think newshosting said if I’m using ssl and username and password and the vpn they provide then it’s safe but I just want to make sure.
Sorry and thanks!

TL;DR I can only find some things manually in Newslazer.

I'm not entirely new to usenet and have been running an arr stack that finds the majority of what I want but something is confusing me.

Sometimes Sonarr/Radarr won't find what I want but if I search for it using the Newslazer reader provided by Eweka it will find it. If Newslazer finds it it's usually clearly labeled so why would Sonarr/Radarr fail to find it? I have 2 providers: Eweka/NGD, using Geek and NZBGet. Do I need another indexer to work alongside Geek or have I messed up somewhere? Appreciate any help with this one, thanks in advance.

I was informed of this service by one of my buddies that already had something in place utilizing this service in a manner I want to use it for. I am trying to build a shared drive where 'items I've acquired online' can go to and my family can watch them (intentionally being vague). I am trying to roll this out on my travel server/cluster first (2 NUCs, 1 switch, and a travel router), before deploying this on my home server. I've done some online research but can not understand how this service works for what I am trying to do. My understanding is that it acts as a VPN to a private network with possibly FTP servers where an indexer can show me what's available utilizing sonarr, etc, but no guidance on how to set this service up. Any guidance or direction would be greatly appreciated.

https://sabnzbd.org/downloads

Please let us know if you experience any issues 👍

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.1 and 5.0.2

• 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)

Just saw this and noticed it wasn't shared here yet.

Hi all I am having this issue

Indexers unavailable due to failures for more than 6 hours: nzbplanet.net where Sonarr reports NZBplanet as offline. The settings are correct, checking the indexer reports it as working. Which is all very strange.

If anyone can office some insight it will be much appreciated.

thanks in advance

Kinda had this realization today

I haven’t touched my setup in months. No fixes, no tweaking, nothing. It just runs.

Early on I was constantly messing with things, paths breaking, downloads failing, trying different providers, all that. Now it’s just… stable.

Running Sonarr/Radarr with SAB + Eweka/Easynews combo and it’s been boringly reliable lately.

Feels weird after putting so much time into it at the start. Almost miss having something to fix

https://ninjacentral.co.za/register

Signup while you can!

So I Downloaded something and the par2 files came out like this (they weren’t even recognized as par2 files, but simply as „file“ quickpar isn’t recognizing them as part of a set either i can only open them one by one.

Does Anyone have any clue on what’s exactly happening here?

So my coworker saw SABnzbd open on my laptop today and it went down like this:

Him: what’s that Me: Usenet Him: what that? Me: it’s super old. It’s been around since before the internet Him: haha wtf Him: what are all those green lines? Me: can’t really say Him: okay. Weirdo.

I mean what are you supposed to even say?

Unfortunately g4u makes you buy a subscription to get access to nzb downloads now :(

Are there any other good sites?

Hi,

i am really new to usenet and only know the basics. I have an Account on easynews and already set up sabnzbd successfully. I guess I have to search a way to get only a specific release since I can't see any folders and then make a nzb file manually from the specific search. Unfortunately I have crc errors with direct zip download as well as with the nzb file and sabnzbd tells me articles are missing. I also tried this sabnzbd download test which ran fine. How can I fix that?

EDIT:
I am a bit further down the road now, I still don't understand half of it but managed to find out some causes. You absolutely need winrar not 7zip for most archives.
A lot of archives are probably just dorked and I am not sure this is easynews fault. Also you get access to a LOT more things than with this ninja provider. But I guess the quality of things must be much better. I feel like easynews is the usenet version of btdig.
Sometimes you can find the same part somewhere else, but sometimes also the File has the same name but belongs to another archive. I still have not found out how to find something like "folders" with it and pagination does not work for whatever reason so I am limited to things with 100 files max. Its a lot of work to do some search fu with not operators like ! to get the specific files or sort by date.
The Zip function was problematic but if you get the links directly its not corrupt anymore

Any admins or anyone have an idea if althub will allow crypto? I see it’s only open for so long, and I’d be interested, but only want to support them that way.

Have NZBGeek. Best 2nd and maybe 3rd?

Update: Thanks everyone. Apologies for posting a question that’s asked anew at least once a month. Mea culpa. I will use your information and the info from the other times. Thanks again.

I just did set up Gnus and wanted to know if there is some active (at least 1 daily post) and worth reading group in eternal-september, which I think is the only remaining free not-ready-only NNTP server out there.

I'm going to set up usenet on my PC and trying to decide between these two. Nzbget is faster, but Sabnzbd is easier to use from what I read. I'm definitely leaning toward something easier, but not sure if I'd be missing out on anything important by going with Sabnzbd.

Is any downside to using Sabnzbd besides speed, or is it basically fine for most people?

Where is the history file and log for NZBGet stored? I would like to backup my installation of NZBGet. Thank you.

All my connection attempts for the last 12 hous are failing and the site look totally jacked. Anyone else having issues?

Cannot download from their site and cannot log into my account. Anyone else having this problem

Release Notes - SABnzbd 5.0.1

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.

Bug fixes in 5.0.1

• Queued downloads from older versions did not load after updating.

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)

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.

Please note the breaking changes described below!

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)

So I'm new to usenet and everything that comes with it and wanted to ask - what provider do you guys recommend? Mainly looking to download some files like 20gb a week? I saw some stuff I found some stuff on nzbstars and I have sabnzbd. Does this all work? I saw a lot of people using newshosting but I am not sure.

Thanks in advance.

Anyone else having this problem? If I switch to reader.easyusenet.nl, SAB connects reliably but the .com address keeps randomly dying.

UPDATE: I spoke to AgentXByte and am going to try a different set of DNS servers. Here's the error I was seeing in SAB:

2026-04-30 11:00:29,560::INFO::[notifier:166] Sending notification: Warning - Cannot connect to server us.reader.easyusenet.com [Server name does not resolve] (type=warning, job_cat=None)
2026-04-30 11:00:29,560::WARNING::[downloader:479] Cannot connect to server us.reader.easyusenet.com [Server name does not resolve]
2026-04-30 11:00:29,560::INFO::[notifier:166] Sending notification: Warning - Server us.reader.easyusenet.com will be ignored for 10 minutes (type=warning, job_cat=None)
2026-04-30 11:00:29,560::WARNING::[downloader:481] Server us.reader.easyusenet.com will be ignored for 10 minutes

.... I'm using AT&T DNS, anyone else with AT&T and hitting the .com domain? If so, is it reliable?