Sab quits randomly all the time, usually doesn't restart.

--

2026-06-02 17:08:57,692 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2026-06-02 17:08:57,692 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2026-06-02 17:08:57,692 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23442820355744 for <Subprocess at 23442821643440 with name start-script in state RUNNING> (stdout)>

2026-06-02 17:08:57,692 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23442820258128 for <Subprocess at 23442821643440 with name start-script in state RUNNING> (stderr)>

2026-06-02 17:08:57,692 INFO exited: start-script (exit status 0; expected)

2026-06-02 17:08:57,692 DEBG received SIGCHLD indicating a child quit

2026-06-02 17:08:57,695 DEBG 'watchdog-script' stdout output:

[info] SABnzbd not running

2026-06-02 17:08:57,695 DEBG 'watchdog-script' stdout output:

[info] Attempting to start SABnzbd...

2026-06-02 17:08:58,265 DEBG 'watchdog-script' stdout output:

[info] SABnzbd process started

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

2026-06-02 17:08:58,267 DEBG 'watchdog-script' stdout output:

[info] SABnzbd process is listening on port 8080

Press ANY KEY to close this window

My installation of binhex - SABnzbdVPN has been working and solid for at least a year now. But now I cannot connect to the docker container unless I disable the VPN within the container settings. I have tried to change the endpoint of the wireguard vpn to no avail either. Any suggestions? I do have this section of the log that appears to have something to do with this potentially?

2026-06-08 15:44:58,361 DEBG 'start-script' stdout output:

[info] WireGuard 'peer' not found, attempting to cycle WireGuard interface...

2026-06-08 15:44:58,362 DEBG 'start-script' stdout output:

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

[debug] Running WireGuard kernel implementation...

2026-06-08 15:44:58,369 DEBG 'start-script' stderr output:

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

2026-06-08 15:44:58,373 DEBG 'start-script' stderr output:

wg-quick: `wg0' is not a WireGuard interface

2026-06-08 15:44:58,373 DEBG 'start-script' stdout output:

[warn] Failed to bring 'down' WireGuard kernel implementation

2026-06-08 15:44:58,374 DEBG 'start-script' stdout output:

[info] Configuring WireGuard...

2026-06-08 15:44:58,516 DEBG 'start-script' stdout output:

[info] Successfully downloaded PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'

2026-06-08 15:44:58,519 DEBG 'start-script' stdout output:

[info] Successfully generated PIA token for wireguard

[debug] PIA generated 'token' for wireguard is 'aEW9UxXS4TTYzGDTHITc2i66SM19Y406nmDoQbBzvSTvv7_4zPYwmmQ+Y8BryeoQsAqVlzTawjoCT09gYUGCAHtl2YStMrcYZORuxAH5gjcTs8zhOq3Jz9NaJ+g='

2026-06-08 15:44:58,519 DEBG 'start-script' stdout output:

[info] Trying to connect to the PIA WireGuard API on 'ca-ontario.privacy.network'...

Any thoughts?

binhex-sabnzbdvpn log.txt

I had the very same problem for a very long time, but the latest version fixed it for me. However I can only connect using OpenVPN and it takes some time to establish a connection, I am using AirVPN.

If I try and use Wireguard I can't establish a connection at all, despite trying a number different VPN server configs

I suggest trying OpenVPN

Thank you. I changed the wireguard endpoint again from ca-ontario to ca-toronto and now it works. So frustrating. I made this change a couple of times with no success, but now....

question from april 13th again:

"problem here....no big issue....but everytime I restart the docker container or the whole unraid server, the actual download restarts from the beginning. I was downloading a big file of 80 gb, and I was at already 75 gb when I had to restart my system, sabnzb started again from 0. I checked the wizard folder and all 75 gb that are already downloaded can be found here. dont sabnzb check the wizard folder if you already downloaded some parts of the current job? why does it start from 0 everytime?

If I dont restart the docker or unraid, everything runs fine...but sometimes you have to restart ;)

thanks"

any hints how to continue the job instead of starting from scratch?