I enabled Tailscale yesterday and I am unable to access SAB.  Radarr and Sonarr work fine.  But when I connect to Sab, I get  "External internet access denied - https://sabnzbd.org/access-denied"

 

The logs show:

 

"2025-04-22 16:44:54,001::INFO::[notifier:157] Sending notification: Warning - Refused connection from: 100.X.X.X Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36] (type=warning, job_cat=None)"

 

100.x.x.x is the tailscale network.  My unraid server is on the 192.X network. Im assuming it has to do with that. 

 

I saw someone mentioned to look at at Q4 in the github, but Im not understanding it.  Do I need to go into edit in the SAB settings and add a variable?  I am not see en var or LAN Network.  

I am sorry if this has been figured out, but I can not for the life of me get this working.

 

I am using proton vpn wireguard and have made the appropriate adjustments (privileged, etc.)

 

SABnzbdvpn will download a burst at full speed, then quickly go down to 0kb/s before showing this error in the UI a bunch of times:

 

     "Failed to connect: [Errno 110] Connection timed out [email protected]:<redacted> (news.iad.newshosting.com)"

 

I have looked in the logs, and only see this over and over:

 

2025-04-23 10:14:54,017 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '192.178.50.68'

2025-04-23 10:14:54,017 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-04-23 10:14:54,034 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-04-23 10:14:54,042 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is x.x.x.x

 

I have tried pinging from the container and there is no issue hitting the URL.

 

Any help is greatly appreciated.

@TobiasGMI doubt that also. Thanks for namedropping Gluetun. I didn't know of that. Will try it out. I assume it sets up a proxy other containers can connect to?

@klausagnolettiYes, basically. You can set up your VPN in Gluetun and then route other containers through it.

If you're on Unraid 7 you just need to change the network type of the other containers to "Container". Then you can change their container network to Gluetun. On earlier versions of Unraid you would need to add the extra parameter "--net=container:GluetunVPN" to the containers you want to route through Gluetun.

We had a power outage today. The Sabnzbd docker is the only one that wouldn't start, showing error 403. I removed the docker and image, and am trying to reinstall from the Community App Store. But it shows this error:

Can anyone help with this?

6 minutes ago, Emphyrio said:

We had a power outage today. The Sabnzbd docker is the only one that wouldn't start, showing error 403. I removed the docker and image, and am trying to reinstall from the Community App Store. But it shows this error:

Can anyone help with this?

that is a connectivity related issue and/or issues with the registry (probably github), try it again in 1 hour, if still no joy then take a look at your router.

I am unable to get to the GUI via LAN when I enable the VPN feature. Using PIA as my provider.

this is the log for the container within Unraid after it starts:

text error warn system array login

-A OUTPUT -d 84.239.27.41/32 -o eth0 -j ACCEPT

-A OUTPUT -d 84.239.27.30/32 -o eth0 -j ACCEPT

-A OUTPUT -d 172.64.147.163/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.18.40.93/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.18.159.201/32 -o eth0 -j ACCEPT

-A OUTPUT -d 104.19.240.167/32 -o eth0 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT

-A OUTPUT -o eth0 -p udp -m udp --sport 8080 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --sport 8090 -j ACCEPT

-A OUTPUT -o eth0 -p udp -m udp --sport 8090 -j ACCEPT

-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT

-A OUTPUT -o lo -j ACCEPT

-A OUTPUT -o wg0 -j ACCEPT

2025-06-26 16:51:35,291 DEBG 'start-script' stdout output:

--------------------

2025-06-26 16:51:35,293 DEBG 'start-script' stdout output:

[info] Configuring WireGuard...

2025-06-26 16:51:35,471 DEBG 'start-script' stdout output:

[info] Token generated for PIA wireguard authentication

2025-06-26 16:51:35,474 DEBG 'start-script' stdout output:

[info] Trying to connect to the PIA WireGuard API on 'us-wisconsin-pf.privacy.network'...

2025-06-26 16:51:35,563 DEBG 'start-script' stdout output:

[info] Attempting to bring WireGuard interface 'up'...

2025-06-26 16:51:35,570 DEBG 'start-script' stderr output:

Warning: `/config/wireguard/wg0.conf' is world accessible

2025-06-26 16:51:35,574 DEBG 'start-script' stderr output:

[#] ip link add wg0 type wireguard

2025-06-26 16:51:35,576 DEBG 'start-script' stderr output:

[#] wg setconf wg0 /dev/fd/63

2025-06-26 16:51:35,577 DEBG 'start-script' stderr output:

[#] ip -4 address add 10.10.161.248 dev wg0

2025-06-26 16:51:35,582 DEBG 'start-script' stderr output:

[#] ip link set mtu 1420 up dev wg0

2025-06-26 16:51:35,587 DEBG 'start-script' stderr output:

[#] wg set wg0 fwmark 51820

2025-06-26 16:51:35,588 DEBG 'start-script' stderr output:

[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2025-06-26 16:51:35,588 DEBG 'start-script' stderr output:

[#] ip -4 rule add not fwmark 51820 table 51820

2025-06-26 16:51:35,589 DEBG 'start-script' stderr output:

[#] ip -4 rule add table main suppress_prefixlength 0

2025-06-26 16:51:35,591 DEBG 'start-script' stderr output:

[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2025-06-26 16:51:35,592 DEBG 'start-script' stderr output:

[#] iptables-restore -n

2025-06-26 16:51:35,593 DEBG 'start-script' stderr output:

[#] '/root/wireguardup.sh'

2025-06-26 16:52:21,671 DEBG 'start-script' stdout output:

[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2025-06-26 16:52:22,071 DEBG 'start-script' stdout output:

[info] Successfully retrieved external IP address 84.239.27.11

2025-06-26 16:52:22,071 DEBG 'start-script' stdout output:

[info] Port forwarding is not enabled

2025-06-26 16:52:22,072 DEBG 'start-script' stdout output:

[info] WireGuard interface 'up'

2025-06-26 16:52:22,686 DEBG 'watchdog-script' stdout output:

[info] SABnzbd not running

2025-06-26 16:52:22,686 DEBG 'watchdog-script' stdout output:

[info] Attempting to start SABnzbd...

2025-06-26 16:52:23,101 DEBG 'watchdog-script' stdout output:

[info] SABnzbd process started

[info] Waiting for SABnzbd process to start listening on port 8080...

2025-06-26 16:52:23,106 DEBG 'watchdog-script' stdout output:

[info] SABnzbd process is listening on port 8080

This is the sabnzb.log file output:

2025-06-26 16:52:23,052::INFO::[SABnzbd:1135] --------------------------------

2025-06-26 16:52:23,053::INFO::[SABnzbd:1136] SABnzbd.py-4.5.1

2025-06-26 16:52:23,053::INFO::[SABnzbd:1137] Full executable path = /usr/lib/sabnzbd/SABnzbd.py

2025-06-26 16:52:23,053::INFO::[SABnzbd:1138] Arguments = "/usr/lib/sabnzbd/SABnzbd.py" "--config-file" "/config" "--server" "0.0.0.0:8080" "--https" "8090" "--daemon"

2025-06-26 16:52:23,054::INFO::[SABnzbd:1147] Certifi version = 2025.01.31

2025-06-26 16:52:23,054::INFO::[SABnzbd:1148] Loaded additional certificates from /usr/lib/sabnzbd/venv/lib/python3.13/site-packages/certifi/cacert.pem

2025-06-26 16:52:23,054::INFO::[SABnzbd:1154] Using INI file /config/sabnzbd.ini

2025-06-26 16:52:23,056::INFO::[postproc:140] Loading postproc queue

2025-06-26 16:52:23,057::INFO::[scheduler:190] Scheduling RSS interval task every 60 min (delay=10)

2025-06-26 16:52:23,057::INFO::[scheduler:200] Scheduling version check in 10 minutes and daily at 5:47

2025-06-26 16:52:23,057::INFO::[scheduler:215] Setting schedule for midnight auto history-purge

2025-06-26 16:52:23,057::INFO::[scheduler:224] Setting schedule for midnight BPS reset

2025-06-26 16:52:23,057::INFO::[scheduler:233] Setting schedule for midnight server expiration check

2025-06-26 16:52:23,057::INFO::[scheduler:242] Setting schedule for server quota check

2025-06-26 16:52:23,058::INFO::[__init__:306] All processes started

2025-06-26 16:52:23,058::INFO::[SABnzbd:336] Template location for Glitter is /usr/lib/sabnzbd/interfaces/Glitter

2025-06-26 16:52:23,058::INFO::[SABnzbd:336] Template location for Config is /usr/lib/sabnzbd/interfaces/Config

2025-06-26 16:52:23,058::INFO::[misc:1303] [N/A] Running external command: ['/usr/sbin/unrar']

2025-06-26 16:52:23,061::INFO::[misc:1303] [N/A] Running external command: ['/usr/sbin/7z']

2025-06-26 16:52:23,062::INFO::[misc:1303] [N/A] Running external command: ['/usr/sbin/par2', '-V']

2025-06-26 16:52:23,063::INFO::[SABnzbd:421] SABCTools module (v8.2.5)... found!

2025-06-26 16:52:23,064::INFO::[SABnzbd:422] SABCTools module is using SIMD set: AVX2

2025-06-26 16:52:23,064::INFO::[SABnzbd:423] SABCTools module is linked to OpenSSL: True

2025-06-26 16:52:23,064::INFO::[SABnzbd:443] Cryptography module (v44.0.2)... found!

2025-06-26 16:52:23,064::INFO::[SABnzbd:446] par2 binary... found (/usr/sbin/par2)

2025-06-26 16:52:23,064::INFO::[SABnzbd:453] UNRAR binary... found (/usr/sbin/unrar)

2025-06-26 16:52:23,064::INFO::[SABnzbd:461] UNRAR binary version 7.11

2025-06-26 16:52:23,064::INFO::[SABnzbd:468] 7za binary... found (/usr/sbin/7z)

2025-06-26 16:52:23,064::INFO::[SABnzbd:470] 7za binary version 24.09

2025-06-26 16:52:23,064::INFO::[SABnzbd:476] nice binary... found (/usr/sbin/nice)

2025-06-26 16:52:23,064::INFO::[SABnzbd:480] ionice binary... found (/usr/sbin/ionice)

2025-06-26 16:52:23,066::INFO::[SABnzbd:1212] HTTPS keys are OK

2025-06-26 16:52:23,067::INFO::[SABnzbd:1348] Starting web-interface on 0.0.0.0:8090

2025-06-26 16:52:23,067::INFO::[_cplogging:213] [26/Jun/2025:16:52:23] ENGINE Bus STARTING

2025-06-26 16:52:23,168::INFO::[_cplogging:213] [26/Jun/2025:16:52:23] ENGINE Serving on http://0.0.0.0:8080

2025-06-26 16:52:23,276::INFO::[_cplogging:213] [26/Jun/2025:16:52:23] ENGINE Serving on https://0.0.0.0:8090

2025-06-26 16:52:23,276::INFO::[_cplogging:213] [26/Jun/2025:16:52:23] ENGINE Bus STARTED

2025-06-26 16:52:23,276::INFO::[SABnzbd:1387] Starting SABnzbd.py-4.5.1

2025-06-26 16:52:23,276::INFO::[_cplogging:213] [26/Jun/2025:16:52:23] ENGINE Client ('127.0.0.1', 48400) lost — peer dropped the TLS connection suddenly, during handshake: (8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1028)')

2025-06-26 16:52:23,277::INFO::[dirscanner:112] Dirscanner starting up

2025-06-26 16:52:23,277::INFO::[notifier:157] Sending notification: SABnzbd - SABnzbd 4.5.1 started (type=startup, job_cat=None)

2025-06-26 16:52:23,277::INFO::[__init__:460] Commit = 3b72a005fd024e0db6d3af5eff1ed2c9f4cbe573

2025-06-26 16:52:23,277::INFO::[__init__:461] Python-version = 3.13.2 (main, Feb 5 2025, 08:05:21) [GCC 14.2.1 20250128]

2025-06-26 16:52:23,277::INFO::[__init__:462] CPU architecture = x86_64

2025-06-26 16:52:23,277::INFO::[__init__:463] Platform = Docker Unraid

2025-06-26 16:52:23,277::INFO::[__init__:464] JSON-module = orjson 3.10.16

2025-06-26 16:52:23,277::INFO::[__init__:465] Preferred encoding = UTF-8

2025-06-26 16:52:23,278::INFO::[__init__:466] SSL version = OpenSSL 3.5.0 8 Apr 2025

2025-06-26 16:52:23,283::INFO::[zconfig:61] No bonjour/zeroconf support installed

2025-06-26 16:52:23,284::INFO::[ssdp:108] Serving SSDP on 10.10.161.248 as SABnzbd

Any idea why I can only get to the GUI when VPN is turned off?

10 hours ago, mgadbois said:

Any idea why I can only get to the GUI when VPN is turned off?

what is LAN_NETWORK defined as? and what is the ip of the machine running the web browser that you are attempting connection from?.

LAN is 10.5.24.0/24 Local PC (same subnet) running windows 11 with Chrome as browser. Running on a custom network (named proxynet)

Edited June 27, 20251 yr by mgadbois
added images

9 hours ago, mgadbois said:

Running on a custom network (named proxynet)

so what is the ip address of the machine?, is it within network 10.5.24.0?

It is on the same subnet. 10.5.254.148/24 is the PC IP. Server is 10.5.254.80/24

If I disable VPN in the settings i can get to the GUI just fine.

Edited June 28, 20251 yr by mgadbois

On 6/28/2025 at 4:24 PM, mgadbois said:

It is on the same subnet. 10.5.254.148/24 is the PC IP. Server is 10.5.254.80/24

If I disable VPN in the settings i can get to the GUI just fine.

same issue here, same subnet etc, interestingly can access guy from iPhone with vpn active but not from MacBook via safari or Firefox or chrome. Using Airvpn if that helps.

i just tried 2 different VPN options on my Android and no luck.

Very frustrating.....

On 4/23/2025 at 10:22 AM, fityp said:

I am sorry if this has been figured out, but I can not for the life of me get this working.

 

I am using proton vpn wireguard and have made the appropriate adjustments (privileged, etc.)

 

SABnzbdvpn will download a burst at full speed, then quickly go down to 0kb/s before showing this error in the UI a bunch of times:

 

     "Failed to connect: [Errno 110] Connection timed out [email protected]:<redacted> (news.iad.newshosting.com)"

 

I have looked in the logs, and only see this over and over:

 

2025-04-23 10:14:54,017 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '192.178.50.68'

2025-04-23 10:14:54,017 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-04-23 10:14:54,034 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-04-23 10:14:54,042 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is x.x.x.x

 

I have tried pinging from the container and there is no issue hitting the URL.

 

Any help is greatly appreciated.

@binhex Sorry to bug you, but could you take a look at this? My downloads are only in short bursts. I dont have any issues using newshosting over ProtonVPN anywhere else, so I feel like I have something mis-configured.

I cannot get this up and running using Wireguard VPN. Works fine on my unRAID server but on another linux server, it is failing every time with this error:

sabnzbdvpn | 2025-07-05 13:30:12,320 DEBG 'start-script' stdout output:

sabnzbdvpn | [info] Configuring WireGuard...

sabnzbdvpn |

sabnzbdvpn | 2025-07-05 13:30:12,348 DEBG 'start-script' stdout output:

sabnzbdvpn | [info] Attempting to bring WireGuard interface 'up'...

sabnzbdvpn |

sabnzbdvpn | 2025-07-05 13:30:12,370 DEBG 'start-script' stderr output:

sabnzbdvpn | Warning: `/config/wireguard/wg0.conf' is world accessible

sabnzbdvpn |

sabnzbdvpn | 2025-07-05 13:30:12,371 DEBG 'start-script' stderr output:

sabnzbdvpn | /usr/sbin/wg-quick: line 40: /config/wireguard/wg0.conf: Permission denied

sabnzbdvpn |

sabnzbdvpn | 2025-07-05 13:30:12,374 DEBG 'start-script' stdout output:

sabnzbdvpn | [warn] WireGuard interface failed to come 'up', exit code is '1'

I've checked every permission and even tried some very permissive ones, but it still fails.

I removed:

PostUp = '/root/wireguardup.sh'

PostDown = '/root/wireguarddown.sh'

lines from my wg0.conf file, but they just keep reappearing every time I start up the container, so I created dummy files at those locations.

Any other ideas?

Thanks

My Docker Compose is here:

services:

sabnzbdvpn:

image: binhex/arch-sabnzbdvpn:latest

container_name: sabnzbdvpn

sysctls:

net.ipv4.conf.all.src_valid_mark: 1

privileged: true

ports:

- 8080:8080

- 8090:8090

- 8118:8118

- 9118:9118

- 58946:58946

- 58946:58946/udp

volumes:

- /srv/docker/sabnzbdvpn/config:/config

- /srv/docker/sabnzbdvpn/downloads:/downloads

- /srv/docker/sabnzbdvpn/incomplete:/incomplete-downloads

- /etc/localtime:/etc/localtime:ro

environment:

- VPN_ENABLED=yes

- VPN_PROV=custom

- VPN_CLIENT=wireguard

- ENABLE_PRIVOXY=yes

- STRICT_PORT_FORWARD=no

- USERSPACE_WIREGUARD=no

# - ENABLE_SOCKS=<yes|no>

# - SOCKS_USER=<socks username>

# - SOCKS_PASS=<socks password>

- LAN_NETWORK=192.168.2.0/24

- NAME_SERVERS=1.1.1.1,1.0.0.1

- PUID=1000

- PGID=1000

# - VPN_INPUT_PORTS=<port number(s)>

# - VPN_OUTPUT_PORTS=<port number(s)>

- DEBUG=false

- UMASK=002

# - PUID=<uid for user>

# - PGID=<gid for user>

restart: unless-stopped

And my wireguard wg0.conf is here:

# TorGuard WireGuard Config

[Interface]

PostUp = '/root/wireguardup.sh'

PostDown = '/root/wireguarddown.sh'

PrivateKey =[redacted]

ListenPort = 59347

MTU = 1390

DNS = 1.1.1.1

Address = 192.168.2.0/24

[Peer]

PublicKey = [redacted]

AllowedIPs = 0.0.0.0/0

Endpoint = [redacted]

PersistentKeepalive = 25

On 4/22/2025 at 5:52 PM, Armed Ferret said:

I enabled Tailscale yesterday and I am unable to access SAB.  Radarr and Sonarr work fine.  But when I connect to Sab, I get  "External internet access denied - https://sabnzbd.org/access-denied"

 

The logs show:

 

"2025-04-22 16:44:54,001::INFO::[notifier:157] Sending notification: Warning - Refused connection from: 100.X.X.X Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36] (type=warning, job_cat=None)"

 

100.x.x.x is the tailscale network.  My unraid server is on the 192.X network. Im assuming it has to do with that. 

 

I saw someone mentioned to look at at Q4 in the github, but Im not understanding it.  Do I need to go into edit in the SAB settings and add a variable?  I am not see en var or LAN Network.  

I am having this exact problem and have been unable to find a solution. Any luck fixing this?

22 hours ago, camens said:

I am having this exact problem and have been unable to find a solution. Any luck fixing this?

Please see Q30 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Hi, the latest versions of Sonarr, Radarr, and Sabnzbdvpn are not starting under Docker and throw the following error:

/usr/sbin/init.sh: line 10: utils.sh: No such file or directory.

The last working (aka starting) versions for me are: Radarr 26.2.10099-1-01, Sonarr 4.0.15.2941-1-01, and Sab 4.5.2-1-01.

Any idea why this might be happening?

Thank you and for all of your efforts on these releases - they are great!

17 hours ago, caplan said:

Hi, the latest versions of Sonarr, Radarr, and Sabnzbdvpn are not starting under Docker and throw the following error:

/usr/sbin/init.sh: line 10: utils.sh: No such file or directory.

im going to need to see the full log, attach /config/supervisord.log - fwiw i run sonarr myself and am on latest with no issue.

5 hours ago, binhex said:

im going to need to see the full log, attach /config/supervisord.log - fwiw i run sonarr myself and am on latest with no issue.

Tl;dr: my fault, nothing to see here.

Since the newer build containers don't start, supervisord.log isn't created/appended to. I have noticed that the container command to start appears to have changed between the versions that spin up fine and the newer versions.

On the working versions, the container startup command appears to be: /usr/bin/dumb-init -- /bin/bash /usr/local/bin/init.sh

On the non-working, newer versions, it's:

/usr/bin/dumb-init -- /bin/bash init.sh

It dawned on me that is may be an issue with the path priority, and sure enough it was. I had a path statement in the compose files (which has been there for years) that overrode the built in one that you defined and since the new start doesn’t specifically include a full path for init.sh, it couldn’t find it (or the right version of it) and prevented the newer build containers from starting, I eliminated the path statement in my compose file and they are all back to full working order on the latest builds.

Thank you for your response as it led me to the issue.

5 hours ago, binhex said:

im going to need to see the full log, attach /config/supervisord.log - fwiw i run sonarr myself and am on latest with no issue.

Edited August 3, 2025Aug 3 by caplan
Additional findings included that solved the problem.

A quick gift - I have setup a GitHub re-occuring action to generate the list of PIA port forward enabled endpoints, the output is to a public Gist in markdown format, feel free to reference if you want to switch endpoint and you can't be arsed to go searching through your supervisord.log: https://gist.github.com/binhex/0d8bc1974bad90f8a61d2d4219ef862c

Note: The URL is NOT expected to change, if it does i will edit the post here.

I can establish a VPN connection using AirVPN, but Sabnzbvpn can't connect to any usenet servers? I have set NAMES SERVERS to 8.8.8.8 and 1.1.1.1 Sonaar & Radarr can't download search items either.

I am seeing this in the log file INFO::[_cplogging:213] [12/Oct/2025:11:57:36] ENGINE Client ('127.0.0.1', 34844) lost — peer dropped the TLS connection suddenly, during handshake: (8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1032)')

I've tried 4 different VPN servers with the same effect

Please see attached files, I have read the Q&A's but can't see any that can help me.

If I turn off the VPN connection, sabnzbvpn works OK

I'd be grateful for some assistance

sabnzbd.txt supervisord.txt

AirVPN_Netherlands_TCP-443-Entry3.ovpn

Edited October 12, 2025Oct 12 by clevoir

On 4/23/2025 at 11:22 AM, fityp said:

I am sorry if this has been figured out, but I can not for the life of me get this working.

 

I am using proton vpn wireguard and have made the appropriate adjustments (privileged, etc.)

 

SABnzbdvpn will download a burst at full speed, then quickly go down to 0kb/s before showing this error in the UI a bunch of times:

 

     "Failed to connect: [Errno 110] Connection timed out [email protected]:<redacted> (news.iad.newshosting.com)"

 

I have looked in the logs, and only see this over and over:

 

2025-04-23 10:14:54,017 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '192.178.50.68'

2025-04-23 10:14:54,017 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2025-04-23 10:14:54,034 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2025-04-23 10:14:54,042 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is x.x.x.x

 

I have tried pinging from the container and there is no issue hitting the URL.

 

Any help is greatly appreciated.

On 7/3/2025 at 10:30 AM, fityp said:

@binhex Sorry to bug you, but could you take a look at this? My downloads are only in short bursts. I dont have any issues using newshosting over ProtonVPN anywhere else, so I feel like I have something mis-configured.

I have the same symptoms as you, downloads are fine for an hour or sometimes a day and then they drop to KB/sec and the only way to recover is to restart the container, where it goes back up to 30MB/sec (3gb fibre connection, but 30MB is ok for me) I do not however get any errors or messages that you are seeing.

I have 3 usenet providers and they all do the same thing. However I use a different VPN provider, I Will try swapping to OpenVPN and see if that improves.
I have been fine for years, until the past month, I changed ports and tried hardcoding specific VPN IP's but no difference.

On 7/3/2025 at 10:30 AM, fityp said:

@binhex Sorry to bug you, but could you take a look at this? My downloads are only in short bursts. I dont have any issues using newshosting over ProtonVPN anywhere else, so I feel like I have something mis-configured.

I have been suffering with similar symptoms for a few weeks now, and have not been able to identify what is causing throughput to slow down, there are no errors or messages like you are seeing, I have tried tweaking my MTU settings as it seems I needed to lower the WG interface to 1290 to not fragment any packets, but still after a random amount of time from minutes to hours the throughput drops to under 1MB. Restart SABNZB fixes it for a amount of time again.

I see no big or rapidly increasing errors or re-transmits on the NIC, which are both Intel 1GB (team). So I am at a loss as to how to resolve it. I have been using this for years without problems, and my VPN provider forums have no reports of errors (I have tried hard coding several servers, across multiple countries to see if this was an ISP related thing, but no difference. even tried different ports and usenet providers.

I am on Unraid 7.14, which was a recent upgrade, so perhaps there is an issue with the NIC driver with Wireguard running in a container for my configuration.

I am going to try OpenVPN, and then try swapping the NIC, I have a 10Gb card that I can try and see if this makes any difference.

Asrock B550 5600G

Intel NIC - dual port

Edited October 26, 2025Oct 26 by hwextreme

Ok so I just realised my bonded NIC connection was using a Onboard Realtek and the intel, this has been running for 2 years like this, I have just unplugged the cable from the onboard nic and doubled my throughput. I had never seen more than 30MB/sec assumed that was just the most I could get from my VPN provider, I also only download at night so 30MB was not a problem.

I didnt notice as the bonded network took the MAC of the intel nic, I had to take a look on the console to connect the MAC to the NIC.

So please check if you have an intel or Realtek network adapter and double check your networking

Looks like that didnt fix the issue, back to 230KB/sec again this morning. restart of of the container and back to 50MB on the same file.. Weird.