r/SABnzbd

SAB refuses connections

New to SAB but i have been reading forums about this. I am running a docker container, no vpn. Arr services get refused during test and my indexer (nzbplanet) looks like it is also being refused.

Logs

What i have tried:

Confirmed API

External Internet Access is Full API

Port fowarding correct, standard 8080

Whitelist Hostname and SABnzbd

Local ranges (myself) , 172.17.0.0/24 , 172.16.0.0/12

Arrs use SSL

No password/username

This is pretty frustrating... if anyone can help id really appreciate it. It bet its some simple setting im missing.

Edit: SOLVED!!! The Arr's in this case required the Local IPv4 from the Status Page of SAB and SSL off. Once i did that the connection worked. Also using the container name works (in my case sabnzbd) in that field.

reddit.com
u/Technical-Signal-401 — 9 days ago
▲ 15 r/SABnzbd

Release Notes - SABnzbd 5.2.0 Beta 2

https://sabnzbd.org/downloads

This is the second test release of version 5.2.0. We are still working on several other features, but hope you will already enjoy the current improvements and give us feedback!

New features in 5.2.0

  • Downloaded data will be written directly to disk (if your hardware supports it), which greatly reduces memory and CPU usage on systems with SSD's. Additionally, several other performance improvements were made.
  • Search your Indexers and add downloads directly from within SABnzbd.
  • Post-Processing, Pre-Queue and Notification Scripts no longer receive command-line arguments. Use the SAB_* environment variables instead. This prevents an attacker easy access to remote code execution.
  • Download directories can no longer be inside the program directory. This is also to prevent an attacker easy access to remote code execution.
  • Changed the internal webserver from CherryPy to Starlette.
  • Overview of Active Sessions is available when username and password are enabled.
  • Only allow proxied requests from hosts configured in xff_trusted_hosts.
  • Removed the scriptlog link from the script_log history field.
  • Remove unused fields completeness, meta, series, id, and script_log from history-API response.
  • Cache Public IPv4 address for 10 minutes to prevent abuse.

Bug fixes in 5.2.0

  • Downloads with Repair priority would not always be at the top of the queue.
  • Failure to read one RSS URL would stop the whole readout instead of continuing to the next.
  • Prevent potential XSS in the History from malicious Script output (GHSA-rpwc-qfxm-7h2v) or malicious NNTP responses (GHSA-c5x2-896f-g5g8).
  • Correct articles_success to articles_failed in Server statistics API-call.
  • Stalled Unrar could freeze the post-processing queue.
  • File handles could remain open after download completed.
  • Downloads with missing articles and no PAR2 would not be marked as failed.
  • macOS: Tray icon would not show on macOS 27.

Upgrade notices

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

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)

reddit.com
u/Safihre — 9 days ago

Can't Connect Via Tailscale

I run a number of other services (both windows and in docker) and they are all accessible via Tailscale. Sab is the only one that is giving me External Internet Access Denied fault when trying to connect from another device via the tailscale IP for the host machine on port 8080.

  • SABnzbd (5.1.3) Host is set to 0.0.0.0

  • Under Special -> local_ranges ( ) -> I added the Tailscale IP for the host machine (100.91.XX.XX) no change.

  • When I try to connect to the tailscale IP 100.91.XX.XX:8080 from another device, SAB gives me the error saying..

  • "Refused connection from: 100.110.XXX.XX [Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.X.X Mobile Safari/537.36]

What am I missing?

//EDIT

So surprising, google's AI fixed it for me.

Clearly its my inexperience talking, but since my host machine's TailScale IP is 100.91.XX.XX, I figured the local_range in sab would have to be the same range.

According to AI's instructions, I needed to put in 100.64.0.0/10 in the local range and low and behold, it works! Why, no idea lol.

reddit.com
u/adblink — 12 days ago