JohnDX

July 18, 2022

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.

July 18, 2022

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.

July 16, 2022

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 ?

JohnDX

Posts

Joined

Last visited

Content Type

Profiles

Forums

Downloads

Store

Gallery

Bug Reports

Documentation

Landing

Posts posted by JohnDX

[Support] binhex - SABnzbdVPN

[Support] binhex - SABnzbdVPN

[Support] binhex - SABnzbdVPN