15 hours ago, binhex said:

Set the network interface back to 'bridge', this is the default working network configuration.

It was set to bridge but I tried setting it to br0 and back to bridge and that seemed to resolve the docker networking issue. Oddly, now I have a different issue, the main web interface doesn’t load in the web browser and I can’t connect to it via any apps.

I’ll keep messing around with it to see if I can figure out what changed.

Edit: It was the container port. Changed it from 8064 to 8080. Don’t know why it was 8064 or when it changed to 8080. But comparing the log with the settings lead to the solution.

supervisord 2.log

Edited May 15May 15 by WuZiMu

Hi everyone,

I have a warning that pops up when I start up my SABNZBD
- /data/completed is not writable at all. This blocks downloads.

When try to add a NZB
- Failed making (/data/incomplete/filename)
Traceback (most recent call last):
  File "/usr/lib/sabnzbd/sabnzbd/filesystem.py", line 752, in create_all_dirs
    os.mkdir(path_part_combined)
    ~~~~~~~~^^^^^^^^^^^^^^^^^^^^
OSError: [Errno 28] No space left on device: '/data/incomplete/filename'

I have

• checked my permissions in the docker, 99, 100.

• ran the docker safe permissions tool

• docker set to privileged

• have sufficient space on my location 500gb

What can I do to fix this?

Thanks in advance!

NT

Edited June 2Jun 2 by NTster

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....