On 4/2/2022 at 12:14 PM, naxos said:

I just started having a DNS problem with this container and I've maxed out my limited Linux chops trying to figure it out.

 

Well, and it just started working today, both with Mullvad and Cloudflare DNS servers. I have no idea why. I guess I'll take it.

Anyone would have a list of server to use with Private Internet Access (Wireguard)...  I install the application, that is now working but super slow.  Would like to try a different endpoint.  I search google and contacted the support at PIA (which was not really helpfull).

 

Thank you for your help,

Martin

I am unable to write to /data/complete directory. No clue what changed but files download properly but the postprocessing script fails to write files to /data/complete due to a permissions issue.

I was able to fix this, some how permissions had changed on /data/complete to root. chown -R nobody:users /data/complete seems to have fixed this for me

On 5/4/2022 at 7:59 PM, bumpyclock said:

I was able to fix this, some how permissions had changed on /data/complete to root. chown -R nobody:users /data/complete seems to have fixed this for me

Any more thoughts on what may have caused this? I’m having the same issue. What’s to stop it happening again?

 

Looking at my system it chewed through 50GB of bandwidth over the last few hours trying to download and redownload files that were no longer importing. 

Edited May 19, 20224 yr by stridemat

12 hours ago, stridemat said:

Any more thoughts on what may have caused this? I’m having the same issue. What’s to stop it happening again?

 

have you upgraded to unraid 6.10.0 by any chance?, i see on reddit people complaining about random permissions changes to appdata so it maybe related to that.

7 hours ago, binhex said:

have you upgraded to unraid 6.10.0 by any chance?, i see on reddit people complaining about random permissions changes to appdata so it maybe related to that.

Yes it seems to be an issue arising in 6.10.0. Knew I should have held on. 
 

Updating permissions seemed to work. 

Edited May 20, 20224 yr by stridemat

Regarding the 'LAN_NETWORK' property, should this be the LAN range provided by my docker bridge (172.*) or the LAN range of the HOST (192.*)?

4 hours ago, User42 said:

Regarding the 'LAN_NETWORK' property, should this be the LAN range provided by my docker bridge (172.*) or the LAN range of the HOST (192.*)?

See Q4.

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Hi there guys.

I'm having an issue where I can't for the life of me change the WebUI port.

 

Things I've tried:
Changed the icon WebUI port in the template
Changed the host port for the WebUI in the template without changing the container port
Changed both the host and container ports for the WebUI in the template
Ensured the LAN_NETWORK variable is set correctly and tested 0.0.0.0 for good measure
Ensured the template .xml reflects the settings in the template
Changed the WebUI port in sabnzbd.ini though Sabnzbd reverts all changes back to default every time it starts
Ran container with 0/0 for PUID and PGID for root permissions
Ran container again with nobody permissions leaving the appdata folder root owned to force the container to read the .ini without changing it

Deleted the perms.txt file at various times throughout the process before restarting the container and while it was already stopped

I'm unable to access any WebUI on port 8080 so I can't get into it at all to make any changes there. I'm at a complete loss. No matter what I do, I can't connect or have the .ini changes stick

Edited May 26, 20224 yr by Avsynthe

Hello, looks like I got an auto update (using latest) last night which included Sab 3.6.0. Ever since, Sab won't start. I reverted back to binhex/arch-sabnzbdvpn:3.5.3-1-03 for now to get myself back up and running, but does anyone have any thoughts on why it won't start up?

 

I set the template to debug. Here's the log: https://pastebin.com/Vk9fsWpM

sabnzbd.error.log: https://pastebin.com/RdCEK85m

5 hours ago, fatgeek said:

Hello, looks like I got an auto update (using latest) last night which included Sab 3.6.0. Ever since, Sab won't start. I reverted back to binhex/arch-sabnzbdvpn:3.5.3-1-03 for now to get myself back up and running, but does anyone have any thoughts on why it won't start up?

 

I set the template to debug. Here's the log: https://pastebin.com/Vk9fsWpM

sabnzbd.error.log: https://pastebin.com/RdCEK85m

 

@fatgeek I also ran into this exact same issue. Reverting back to binhex/arch-sabnzbdvpn:3.5.3-1-03 also fixed it for me.

 

No clue what the issue might be, but I thought I'd let you know you're not the only one having these symptoms

On 6/8/2022 at 2:04 PM, fatgeek said:

Hello, looks like I got an auto update (using latest) last night which included Sab 3.6.0. Ever since, Sab won't start. I reverted back to binhex/arch-sabnzbdvpn:3.5.3-1-03 for now to get myself back up and running, but does anyone have any thoughts on why it won't start up?

 

I set the template to debug. Here's the log: https://pastebin.com/Vk9fsWpM

sabnzbd.error.log: https://pastebin.com/RdCEK85m

 

I'm also experiencing this. My `sabnzbd.error.log` shows:

 

Traceback (most recent call last):
  File "/usr/lib/sabnzbd/SABnzbd.py", line 1786, in <module>
    main()
  File "/usr/lib/sabnzbd/SABnzbd.py", line 1238, in main
    publicipv4()
  File "/usr/lib/sabnzbd/sabnzbd/getipaddress.py", line 114, in publicipv4
    result = addresslookup4(sabnzbd.cfg.selftest_host())
  File "/usr/lib/sabnzbd/sabnzbd/getipaddress.py", line 48, in func_wrapper
    return sabnzbd.THREAD_POOL.submit(item, *args, **kwargs).result(max_timeout)
  File "/usr/lib/python3.10/concurrent/futures/_base.py", line 448, in result
    raise TimeoutError()
concurrent.futures._base.TimeoutError

 

Yeah I’m having the same issues as set out above. 
 

Rolling back fixed the error and also the proxy connections started working again. 

Edited June 15, 20224 yr by stridemat

Hi, I'm having a strange issue. Sabnzbdvpn became inaccessible via my browser so I decided to re-install it. However for some reason it installs with Default Base Folder: /config rather than /data. 

 

I can't figure out what I am doing wrong but I have tried numerous times to change it.

I am sure you want me to post some logs or something so please let me know where from?

 

Thanks for your help.

 

Unraid 6.10.3

Was exited to start with sabnzbdvpn.

I ran the install, but sabnzbd is not started. In the log I see that the VPN is started.

 

in supervisor.log I see the following:

2022-07-16 11:06:51,201 DEBG 'start-script' stderr output:
modprobe: FATAL: Module tun not found in directory /lib/modules/5.15.0-41-generic

2022-07-16 11:06:51,201 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module using modprobe, trying insmod...

2022-07-16 11:06:51,202 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory

2022-07-16 11:06:51,203 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module, assuming its dynamically loaded

2022-07-16 11:06:51,211 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2022-07-16 11:06:51,213 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/5.15.0-41-generic

2022-07-16 11:06:51,213 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2022-07-16 11:06:51,214 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2022-07-16 11:06:51,214 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

2022-07-16 11:06:51,224 DEBG 'start-script' stdout output:
[info] Default route for container is 172.26.0.1

2022-07-16 11:06:51,237 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.26.0.0/16

2022-07-16 11:06:51,240 DEBG 'start-script' stdout output:
[info] Adding 192.168.2.0/24 as route via docker eth0

2022-07-16 11:06:51,241 DEBG 'start-script' stderr output:
RTNETLINK answers: Operation not permitted

 

The process table doesnt seem to be OK:

UID          PID    PPID  C STIME TTY          TIME CMD
root           1       0  0 11:09 ?        00:00:00 /usr/bin/tini -g -- /bin/bash /usr/local/bin/init.sh
root           6       1  0 11:09 ?        00:00:03 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n
root         170       6  0 11:09 ?        00:00:00 /bin/bash /usr/local/bin/shutdown.sh sabnzbd
root         171       6  0 11:09 ?        00:00:01 /bin/bash /root/start.sh
root         172       6  0 11:09 ?        00:00:02 /bin/bash /home/nobody/watchdog.sh
root         173     170  0 11:09 ?        00:00:00 sleep infinity
root         372       0  0 11:10 pts/0    00:00:00 bash
root         629     171  0 11:10 ?        00:00:00 /bin/bash /root/start.sh
root        1927       0  0 11:12 pts/1    00:00:00 bash
root        8968     629  0 11:23 ?        00:00:00 sleep 30s
root        8992     171  7 11:23 ?        00:00:00 /usr/bin/openvpn --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV privado --setenv VPN_CLIENT openvpn --setenv DEBUG true -
root        8996     172  0 11:23 ?        00:00:00 sleep 0.1s
root        8997    1927  0 11:23 pts/1    00:00:00 ps -ef

 

I have kept almost all values the same as stated on https://hub.docker.com/r/binhex/arch-sabnzbdvpn

 

Anybody an idea ?

On 7/16/2022 at 11:27 AM, JohnDX said:

Was exited to start with sabnzbdvpn.

I ran the install, but sabnzbd is not started. In the log I see that the VPN is started.

 

in supervisor.log I see the following:

2022-07-16 11:06:51,201 DEBG 'start-script' stderr output:
modprobe: FATAL: Module tun not found in directory /lib/modules/5.15.0-41-generic

2022-07-16 11:06:51,201 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module using modprobe, trying insmod...

2022-07-16 11:06:51,202 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory

2022-07-16 11:06:51,203 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module, assuming its dynamically loaded

2022-07-16 11:06:51,211 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2022-07-16 11:06:51,213 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/5.15.0-41-generic

2022-07-16 11:06:51,213 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2022-07-16 11:06:51,214 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2022-07-16 11:06:51,214 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

2022-07-16 11:06:51,224 DEBG 'start-script' stdout output:
[info] Default route for container is 172.26.0.1

2022-07-16 11:06:51,237 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.26.0.0/16

2022-07-16 11:06:51,240 DEBG 'start-script' stdout output:
[info] Adding 192.168.2.0/24 as route via docker eth0

2022-07-16 11:06:51,241 DEBG 'start-script' stderr output:
RTNETLINK answers: Operation not permitted

 

The process table doesnt seem to be OK:

UID          PID    PPID  C STIME TTY          TIME CMD
root           1       0  0 11:09 ?        00:00:00 /usr/bin/tini -g -- /bin/bash /usr/local/bin/init.sh
root           6       1  0 11:09 ?        00:00:03 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n
root         170       6  0 11:09 ?        00:00:00 /bin/bash /usr/local/bin/shutdown.sh sabnzbd
root         171       6  0 11:09 ?        00:00:01 /bin/bash /root/start.sh
root         172       6  0 11:09 ?        00:00:02 /bin/bash /home/nobody/watchdog.sh
root         173     170  0 11:09 ?        00:00:00 sleep infinity
root         372       0  0 11:10 pts/0    00:00:00 bash
root         629     171  0 11:10 ?        00:00:00 /bin/bash /root/start.sh
root        1927       0  0 11:12 pts/1    00:00:00 bash
root        8968     629  0 11:23 ?        00:00:00 sleep 30s
root        8992     171  7 11:23 ?        00:00:00 /usr/bin/openvpn --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV privado --setenv VPN_CLIENT openvpn --setenv DEBUG true -
root        8996     172  0 11:23 ?        00:00:00 sleep 0.1s
root        8997    1927  0 11:23 pts/1    00:00:00 ps -ef

 

I have kept almost all values the same as stated on https://hub.docker.com/r/binhex/arch-sabnzbdvpn

 

Anybody an idea ?

I have remove the line "remote-cert-tls server" from the ovpn file as I read earlier on on this forum.

Unfortunately results are the same.

 

The logfile show somethings interesting:

2022-07-18 11:30:54,267 DEBG 'start-script' stdout output:
2022-07-18 11:30:54 ROUTE_GATEWAY 172.26.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:1a:00:02
2022-07-18 11:30:54 ERROR: Cannot ioctl TUNSETIFF tun: Operation not permitted (errno=1)
2022-07-18 11:30:54 Exiting due to fatal error

This keeps repeating many, many times.

Solved the issue:

 

Added the following to my docker.compose file:

    cap_add:
      - NET_ADMIN

This solved the issue. Found a hint in an earlier post.

3 hours ago, JohnDX said:

Found a hint in an earlier post.

and its in the readme.md (linked in op):- https://github.com/binhex/arch-sabnzbdvpn

ERROR 3 hours ago Error while adding Sc*-In The Kin*REMASTERED-CD-FLAC-2012-YARD.nzb, removing
Traceback (most recent call last):
  File "/usr/lib/sabnzbd/sabnzbd/nzbparser.py", line 319, in process_single_nzb
    nzo = nzbstuff.NzbObject(
  File "/usr/lib/sabnzbd/sabnzbd/nzbstuff.py", line 778, in __init__
    admin_dir = os.path.join(self.download_path, JOB_ADMIN)
  File "/usr/lib/python3.10/posixpath.py", line 76, in join
    a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not bool

ERROR 3 hours ago Failed making (/downloads/incomplete/Sc*-In The Kin*REMASTERED-CD-FLAC-2012-YARD)
Traceback (most recent call last):
  File "/usr/lib/sabnzbd/sabnzbd/filesystem.py", line 719, in create_all_dirs
    os.mkdir(path_part_combined)
OSError: [Errno 5] Input/output error: '/downloads/incomplete/Sc*-In The Kin*REMASTERED-CD-FLAC-2012-YARD'

ERROR 9 hours ago Error while adding Sc*-In The Kin*REMASTERED-CD-FLAC-2012-YARD.nzb, removing
Traceback (most recent call last):
  File "/usr/lib/sabnzbd/sabnzbd/nzbparser.py", line 319, in process_single_nzb
    nzo = nzbstuff.NzbObject(
  File "/usr/lib/sabnzbd/sabnzbd/nzbstuff.py", line 778, in __init__
    admin_dir = os.path.join(self.download_path, JOB_ADMIN)
  File "/usr/lib/python3.10/posixpath.py", line 76, in join
    a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not bool

ERROR 9 hours ago Failed making (/downloads/incomplete/Sc*-In The Kin*REMASTERED-CD-FLAC-2012-YARD)
Traceback (most recent call last):
  File "/usr/lib/sabnzbd/sabnzbd/filesystem.py", line 719, in create_all_dirs
    os.mkdir(path_part_combined)
OSError: [Errno 5] Input/output error: '/downloads/incomplete/Sc*-In The Kin*REMASTERED-CD-FLAC-2012-YARD'

 

 

 

 

 

 

 

Just saw this in sab.  First time this has ever happened.  I can ssh in and access the download folder just fine.

 

I recently changed from PIA to Mullvad using this guide. But the Webgui does not work anymore. This is a rundown of my settings:

• Priviliged container
• Extra parameters: --sysctl="net.ipv4.conf.all.src_valid_mark=1
• VPN enabled
• vpn username/password default
• VPN_PROV = custom
• VPN_CLIENT = wireguard
• No strict portforward
• Lan network = 192.168.178.0/24 (server ip is 192.168.178.x)
• Name servers = default

I let Sabnzbd run, drag my wireguard config in there and rename it to wg0.conf. The container starts without any error and sabnzbd also has no errors in the log.

 

What am I doing wrong here? I tried different container tags, different settings, different WIreguard configs but nothing helps. I saw some threads where people had the same problem but they did not post a fix (like this one).

 

I think I found it. I'm using Tailscale subnet router to connect to my machines so therefore I am not in the LAN network I have defined. I need to find out what IP my container is seeing when I cannot to it so I can add it to the LAN network.

final edit: I fixed it by adding 100.64.0.0/10 (found the cidr here) to the lan_network variable

Edited July 24, 20223 yr by Zero

In the past few days I have lost WebUI access to my binhex-sabnzbdvpn docker.  I tried rolling back the version to 3.5.3 and that didn't work.  Here is my log file for the docker.  I have no clue why it stopped working.  Other dockers are working.  I have also noted that Sonar can no longer access Sab either.  At this point I think it is a network issue, but I am not sure.

sabnzbdvpnLOG.txt

Sabnzbd Network ifconfig.txt

Edited August 20, 20223 yr by poet_will

I'm having the same issue as poet_will with not being able to access the webui, thi sis also an issue with qbittorrentvpn.

8 minutes ago, goose1701 said:

I'm having the same issue as poet_will with not being able to access the webui, thi sis also an issue with qbittorrentvpn.

 

On 8/20/2022 at 1:17 AM, poet_will said:

In the past few days I have lost WebUI access to my binhex-sabnzbdvpn docker.  I tried rolling back the version to 3.5.3 and that didn't work.  Here is my log file for the docker.  I have no clue why it stopped working.  Other dockers are working.  I have also noted that Sonar can no longer access Sab either.  At this point I think it is a network issue, but I am not sure.

sabnzbdvpnLOG.txt 4.86 kB · 0 downloads

Sabnzbd Network ifconfig.txt 772 B · 0 downloads

im going to need you both to do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Here you are:

 

 

supervisord.log