[Support] binhex - DelugeVPN


Recommended Posts

41 minutes ago, PitRejection2359 said:

Ok, will do.

From your log:

022-04-03 10:00:34,126 DEBG 'start-script' stdout output:
2022-04-03 10:00:34 [UNDEF] Inactivity timeout (--ping-restart), restarting

2022-04-03 10:00:34,127 DEBG 'start-script' stdout output:
2022-04-03 10:00:34 SIGHUP[soft,ping-restart] received, process restarting

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

  • Like 1
Link to comment
From your log:
022-04-03 10:00:34,126 DEBG 'start-script' stdout output:2022-04-03 10:00:34 [uNDEF] Inactivity timeout (--ping-restart), restarting2022-04-03 10:00:34,127 DEBG 'start-script' stdout output:2022-04-03 10:00:34 SIGHUP[soft,ping-restart] received, process restarting

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

Thank you, I'll take a look and see if I can work out how to resolve that...

Sent from my SM-G965F using Tapatalk

Link to comment

I've been using this container for a few years, but starting on 2022-03-30, I've had an issue where torrent can be added, but will not download or upload.

 

INFO:

  • I can access both the webUI and thin client just fine.
  • The bottom status bar in deluge show `N/A` for the IP.
  • Torguard's test torrent is showing the correct TorGuard VPN IP address (matches the address in the torguard wireguard config `wg0.conf`)
  • Adding a torrent via magnet populates the info about size, peers and seeders
  • For example, recently added `ubuntu-20.04.4-desktop-amd64.iso` is showing as 3.1GB with 1214 seeds
  • I have not touched unRaid in the last few weeks, so no changes have been made to the OS (uptime 40+ days)
  • Containers are set to auto-update, but I'm unsure if binhex has released a new container since 2022-03-29
  • My privoxy works perfectly fine
  • Nothing out of the ordinary in the logs (but I may have missed something). See below
Spoiler

supervisor.log
 

2022-04-03 15:32:30,955 DEBG received SIGCHLD indicating a child quit
Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2022-04-03 15:32:50.029456 [info] Host is running unRAID
2022-04-03 15:32:50.075089 [info] System information Linux <HOSTNAME REDACTED> 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2022-04-03 15:32:50.130961 [info] OS_ARCH defined as 'x86-64'
2022-04-03 15:32:50.186675 [info] PUID defined as '1000'
2022-04-03 15:32:50.269570 [info] PGID defined as '100'
2022-04-03 15:32:50.382378 [info] UMASK defined as '000'
2022-04-03 15:32:50.434390 [info] Permissions already set for '/config'
2022-04-03 15:32:50.501694 [info] Deleting files in /tmp (non recursive)...
2022-04-03 15:32:50.566203 [info] VPN_ENABLED defined as 'yes'
2022-04-03 15:32:50.614770 [info] VPN_CLIENT defined as 'wireguard'
2022-04-03 15:32:50.661079 [info] VPN_PROV defined as 'custom'
2022-04-03 15:32:50.739894 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2022-04-03 15:32:50.815279 [info] VPN_REMOTE_SERVER defined as '45.128.36.146'
2022-04-03 15:32:50.865800 [info] VPN_REMOTE_PORT defined as '1443'
2022-04-03 15:32:50.907893 [info] VPN_DEVICE_TYPE defined as 'wg0'
2022-04-03 15:32:50.953076 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2022-04-03 15:32:51.003618 [info] LAN_NETWORK defined as '192.168.1.0/24'
2022-04-03 15:32:51.054978 [info] NAME_SERVERS defined as '1.1.1.1,1.0.0.1'
2022-04-03 15:32:51.104507 [info] VPN_USER defined as '<REDACTED>'
2022-04-03 15:32:51.155385 [info] VPN_PASS defined as '<REDACTED>'
2022-04-03 15:32:51.206595 [info] ENABLE_PRIVOXY defined as 'yes'
2022-04-03 15:32:51.262809 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2022-04-03 15:32:51.313165 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2022-04-03 15:32:51.363272 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info'
2022-04-03 15:32:51.413867 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info'
2022-04-03 15:32:51.470195 [info] Starting Supervisor...
2022-04-03 15:32:52,088 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2022-04-03 15:32:52,088 INFO Set uid to user 0 succeeded
2022-04-03 15:32:52,095 INFO supervisord started with pid 7
2022-04-03 15:32:53,099 INFO spawned: 'shutdown-script' with pid 162
2022-04-03 15:32:53,102 INFO spawned: 'start-script' with pid 163
2022-04-03 15:32:53,105 INFO spawned: 'watchdog-script' with pid 164
2022-04-03 15:32:53,106 INFO reaped unknown pid 8 (exit status 0)
2022-04-03 15:32:53,114 DEBG 'shutdown-script' stdout output:
[info] Signal not specified as parameter 2, assuming signal '15' (sigterm)
[info] Process owner not specified as parameter 3, assuming owner 'nobody'

2022-04-03 15:32:53,115 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-04-03 15:32:53,115 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-04-03 15:32:53,116 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-04-03 15:32:53,117 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN
[debug] Environment variables defined as follows
ADDITIONAL_PORTS=
APPLICATION=deluge
BASH=/bin/bash
BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath
BASH_ALIASES=()
BASH_ARGC=()
BASH_ARGV=()
BASH_CMDS=()
BASH_LINENO=([0]="0")
BASH_SOURCE=([0]="/root/start.sh")
BASH_VERSINFO=([0]="5" [1]="1" [2]="12" [3]="1" [4]="release" [5]="x86_64-pc-linux-gnu")
BASH_VERSION='5.1.12(1)-release'
DEBUG=true
DELUGE_DAEMON_LOG_LEVEL=info
DELUGE_WEB_LOG_LEVEL=info
DIRSTACK=()
ENABLE_PRIVOXY=yes
EUID=0
GROUPS=()
HOME=/home/nobody
HOSTNAME=<HOSTNAME REDACTED>
HOSTTYPE=x86_64
HOST_OS=Unraid
IFS=$' \t\n'
LANG=en_GB.UTF-8
LAN_NETWORK=192.168.1.0/24
MACHTYPE=x86_64-pc-linux-gnu
NAME_SERVERS=1.1.1.1,1.0.0.1
OPTERR=1
OPTIND=1
OSTYPE=linux-gnu
OS_ARCH=x86-64
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PGID=100
PIPESTATUS=([0]="0")
PPID=7
PS4='+ '
PUID=1000
PWD=/
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:interactive-comments
SHLVL=1
STRICT_PORT_FORWARD=no
SUPERVISOR_ENABLED=1
SUPERVISOR_GROUP_NAME=start-script
SUPERVISOR_PROCESS_NAME=start-script
TERM=xterm
TZ=America/<REDACTED>
UID=0
UMASK=000
VPN_CLIENT=wireguard
VPN_CONFIG=/config/wireguard/wg0.conf
VPN_DEVICE_TYPE=wg0
VPN_ENABLED=yes
VPN_INPUT_PORTS=
VPN_OPTIONS=
VPN_OUTPUT_PORTS=
VPN_PASS=<REDACTED>
VPN_PROV=custom
VPN_REMOTE_PORT=1443
VPN_REMOTE_PROTOCOL=udp
VPN_REMOTE_SERVER=45.128.36.146
VPN_USER=<REDACTED>
_='[debug] Environment variables defined as follows'
[debug] Directory listing of files in /config/wireguard/ as follows

2022-04-03 15:32:53,128 DEBG 'start-script' stdout output:
total 4
drwxrwxr-x 1 nobody users  16 Apr  3 15:29 .
drwxrwxr-x 1 nobody users 948 Apr  3 15:32 ..
-rwxrwxr-x 1 nobody users 379 Apr  3 15:29 wg0.conf

2022-04-03 15:32:53,129 DEBG 'start-script' stdout output:
[debug] Contents of WireGuard config file '/config/wireguard/wg0.conf' as follows...

2022-04-03 15:32:53,131 DEBG 'start-script' stdout output:
# TorGuard WireGuard Config
[Interface]
PostUp = '/root/wireguardup.sh'
PostDown = '/root/wireguarddown.sh'
PrivateKey = <REDACTED>/4k8=
ListenPort = 42000
MTU = 1292
DNS = 1.1.1.1
Address = 10.13.22.169/24

[Peer]
PublicKey = <REDACTED>=
AllowedIPs = 0.0.0.0/0
Endpoint = 45.128.36.146:1443
PersistentKeepalive = 25

2022-04-03 15:32:53,136 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2022-04-03 15:32:53,142 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2022-04-03 15:32:53,151 DEBG 'start-script' stdout output:
45.128.36.146

2022-04-03 15:32:53,168 DEBG 'start-script' stdout output:
[debug] Show name servers defined for container

2022-04-03 15:32:53,169 DEBG 'start-script' stdout output:
nameserver 1.1.1.1
nameserver 1.0.0.1

2022-04-03 15:32:53,170 DEBG 'start-script' stdout output:
[debug] Show name resolution for VPN endpoint 45.128.36.146

2022-04-03 15:32:53,202 DEBG 'start-script' stdout output:
;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 57986
;; flags: qr aa rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 
;; QUESTION SECTION:
;; 45.128.36.146.	IN	A

;; ANSWER SECTION:

;; AUTHORITY SECTION:
.	86400	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2022040301 1800 900 604800 86400

;; ADDITIONAL SECTION:

;; Query time: 24 msec
;; SERVER: 1.1.1.1
;; WHEN: Sun Apr  3 15:32:53 2022
;; MSG SIZE  rcvd: 106

2022-04-03 15:32:53,203 DEBG 'start-script' stdout output:
[debug] Show contents of hosts file

2022-04-03 15:32:53,204 DEBG 'start-script' stdout output:
127.0.0.1	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
172.17.0.2	<HOSTNAME REDACTED>

2022-04-03 15:32:53,254 DEBG 'start-script' stdout output:
[debug] Docker interface defined as eth0

2022-04-03 15:32:53,262 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2022-04-03 15:32:53,268 DEBG 'start-script' stdout output:
[debug] Docker IP defined as 172.17.0.2

2022-04-03 15:32:53,274 DEBG 'start-script' stdout output:
[debug] Docker netmask defined as 255.255.0.0

2022-04-03 15:32:53,288 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2022-04-03 15:32:53,293 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2022-04-03 15:32:53,295 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2022-04-03 15:32:53,297 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0 
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2 
192.168.1.0/24 via 172.17.0.1 dev eth0 
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1 
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 
broadcast 172.17.0.0 dev eth0 table local proto kernel scope link src 172.17.0.2 
local 172.17.0.2 dev eth0 table local proto kernel scope host src 172.17.0.2 
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.2 

2022-04-03 15:32:53,297 DEBG 'start-script' stdout output:
--------------------
[debug] Modules currently loaded for kernel

2022-04-03 15:32:53,303 DEBG 'start-script' stdout output:
Module                  Size  Used by
xt_connmark            16384  2
xt_comment             16384  3
iptable_raw            16384  1
xt_mark                16384  2
xt_CHECKSUM            16384  1
ipt_REJECT             16384  2
nf_reject_ipv4         16384  1 ipt_REJECT
ip6table_mangle        16384  1
ip6table_nat           16384  1
iptable_mangle         16384  2
nf_tables             180224  0
vhost_net              24576  0
tun                    45056  2 vhost_net
vhost                  28672  1 vhost_net
vhost_iotlb            16384  1 vhost
tap                    24576  1 vhost_net
veth                   24576  0
xt_nat                 16384  31
xt_tcpudp              16384  87
xt_conntrack           16384  3
nf_conntrack_netlink    45056  0
nfnetlink              16384  3 nf_conntrack_netlink,nf_tables
xt_addrtype            16384  3
br_netfilter           24576  0
xfs                   671744  12
nfsd                  106496  11
lockd                  73728  1 nfsd
grace                  16384  1 lockd
sunrpc                237568  14 nfsd,lockd
md_mod                 45056  12
ipmi_devintf           16384  0
iptable_nat            16384  4
xt_MASQUERADE          16384  25
nf_nat                 40960  4 ip6table_nat,xt_nat,iptable_nat,xt_MASQUERADE
nf_conntrack          110592  6 xt_conntrack,nf_nat,xt_nat,nf_conntrack_netlink,xt_connmark,xt_MASQUERADE
nf_defrag_ipv6         16384  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
wireguard              81920  0
curve25519_x86_64      32768  1 wireguard
libcurve25519_generic    49152  2 curve25519_x86_64,wireguard
libchacha20poly1305    16384  1 wireguard
chacha_x86_64          28672  1 libchacha20poly1305
poly1305_x86_64        28672  1 libchacha20poly1305
ip6_udp_tunnel         16384  1 wireguard
udp_tunnel             20480  1 wireguard
libblake2s             16384  1 wireguard
blake2s_x86_64         20480  1 libblake2s
libblake2s_generic     20480  1 blake2s_x86_64
libchacha              16384  1 chacha_x86_64
ip6table_filter        16384  1
ip6_tables             28672  3 ip6table_filter,ip6table_nat,ip6table_mangle
iptable_filter         16384  2
ip_tables              28672  6 iptable_filter,iptable_raw,iptable_nat,iptable_mangle
x_tables               28672  17 ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,xt_comment,ip6_tables,ipt_REJECT,xt_connmark,iptable_raw,ip_tables,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark
bonding               114688  0
intel_powerclamp       16384  0
coretemp               16384  0
kvm_intel             212992  0
kvm                   421888  1 kvm_intel
mpt3sas               237568  8
ahci                   40960  6
crc32c_intel           24576  3
i2c_i801               24576  0
libahci                28672  1 ahci
raid_class             16384  1 mpt3sas
i2c_smbus              16384  1 i2c_i801
i5500_temp             16384  0
intel_cstate           16384  0
e1000e                180224  0
i2c_core               45056  2 i2c_smbus,i2c_i801
input_leds             16384  0
ipmi_si                49152  0
scsi_transport_sas     32768  1 mpt3sas
intel_uncore          131072  0
led_class              16384  1 input_leds
i7core_edac            28672  0
button                 16384  0
acpi_cpufreq           16384  1

2022-04-03 15:32:53,308 DEBG 'start-script' stdout output:
iptable_mangle         16384  2
ip_tables              28672  6 iptable_filter,iptable_raw,iptable_nat,iptable_mangle
x_tables               28672  17 ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,xt_comment,ip6_tables,ipt_REJECT,xt_connmark,iptable_raw,ip_tables,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark

2022-04-03 15:32:53,309 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2022-04-03 15:32:53,396 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2022-04-03 15:32:53,398 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 45.128.36.146/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i wg0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 45.128.36.146/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 8118 -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

2022-04-03 15:32:53,400 DEBG 'start-script' stdout output:
--------------------

2022-04-03 15:32:53,405 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2022-04-03 15:32:53,425 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2022-04-03 15:32:53,441 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2022-04-03 15:32:53,444 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2022-04-03 15:32:53,455 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.13.22.169/24 dev wg0

2022-04-03 15:32:53,457 DEBG 'start-script' stderr output:
[#] ip link set mtu 1292 up dev wg0

2022-04-03 15:32:53,473 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x

2022-04-03 15:32:53,491 DEBG 'start-script' stderr output:
could not detect a useable init system

2022-04-03 15:32:53,557 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2022-04-03 15:32:53,559 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2022-04-03 15:32:53,560 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2022-04-03 15:32:53,562 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2022-04-03 15:32:53,567 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2022-04-03 15:32:53,571 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2022-04-03 15:32:53,578 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2022-04-03 15:32:53,583 DEBG 'start-script' stdout output:
[debug] Waiting for valid local and gateway IP addresses from tunnel...

2022-04-03 15:32:54,606 DEBG 'start-script' stdout output:
[debug] Valid local IP address from tunnel acquired '10.13.22.169'

2022-04-03 15:32:54,607 DEBG 'start-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-04-03 15:32:54,660 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-04-03 15:32:54,662 DEBG 'start-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.251.40.164'

2022-04-03 15:32:54,668 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2022-04-03 15:32:54,717 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.176.196'

2022-04-03 15:32:54,911 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 45.128.36.146

2022-04-03 15:32:54,913 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2022-04-03 15:32:54,914 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2022-04-03 15:32:54,921 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2022-04-03 15:32:54,936 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2022-04-03 15:32:54,937 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.13.22.169 different, marking for reconfigure

2022-04-03 15:32:54,963 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2022-04-03 15:32:54,970 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2022-04-03 15:32:54,978 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2022-04-03 15:32:54,979 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2022-04-03 15:32:55,345 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.13.22.169'
[info] Deluge key 'listen_interface' will have a new value '10.13.22.169'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-04-03 15:32:55,635 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-04-03 15:32:55,940 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '<REDACTED>'
[info] Deluge key 'default_daemon' will have a new value '<REDACTED>'
[info] Writing changes to Deluge config file '/config/web.conf'...

2022-04-03 15:32:56,774 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2022-04-03 15:32:57,311 DEBG 'watchdog-script' stderr output:
/config/plugins/SimpleExtractor-1.4-py3.8.egg/deluge_simpleextractor/core.py:129: SyntaxWarning: "is not" with a literal. Did you mean "!="?

2022-04-03 15:32:57,315 DEBG 'watchdog-script' stderr output:
/config/plugins/SimpleExtractor-1.4-py3.8.egg/deluge_simpleextractor/core.py:129: SyntaxWarning: "is not" with a literal. Did you mean "!="?

2022-04-03 15:32:57,327 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2022-04-03 15:33:03,622 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2022-04-03 15:33:03,622 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2022-04-03 15:33:03,623 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2022-04-03 15:33:03,626 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2022-04-03 15:33:04,640 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2022-04-03 15:33:04,648 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2022-04-03 15:33:04,648 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.13.22.169
[debug] Deluge IP is 10.13.22.169

2022-04-03 15:33:34,651 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-04-03 15:33:34,706 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.72.100'

2022-04-03 15:33:34,707 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2022-04-03 15:33:34,723 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2022-04-03 15:33:34,745 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.13.22.169
[debug] Deluge IP is 10.13.22.169

 

 

Link to comment
On 4/3/2022 at 3:02 PM, PitRejection2359 said:

Thank you, I'll take a look and see if I can work out how to resolve that...emoji1696.png

Sent from my SM-G965F using Tapatalk
 

So, I managed to use a different VPN and can now access the deluge webui with the VPN running, but it doesn't download anything. The IP address box on the bottom right within deluge is blank, but if I open a console and run "curl ifconfig.io" it shows an IP address in the country that I've set my VPN to route through. If I turn the VPN off, the download speed goes normally and i can see the IP address in Deluge.

Any ideas what is going wrong? recent supervisord.log attached.

supervisord.log

Link to comment
17 minutes ago, PitRejection2359 said:

So, I managed to use a different VPN and can now access the deluge webui with the VPN running, but it doesn't download anything. The IP address box on the bottom right within deluge is blank, but if I open a console and run "curl ifconfig.io" it shows an IP address in the country that I've set my VPN to route through. If I turn the VPN off, the download speed goes normally and i can see the IP address in Deluge.

Any ideas what is going wrong? recent supervisord.log attached.

supervisord.log 12.23 kB · 0 downloads

I figured it out - my VPN doesn't allow torrents on that particular location / IP address I had downloaded the ovpn file for - changing it to a different location & file worked fine.

Link to comment
On 4/3/2022 at 7:43 PM, Bob1215 said:

I've been using this container for a few years, but starting on 2022-03-30, I've had an issue where torrent can be added, but will not download or upload.

 

INFO:

  • I can access both the webUI and thin client just fine.
  • The bottom status bar in deluge show `N/A` for the IP.
  • Torguard's test torrent is showing the correct TorGuard VPN IP address (matches the address in the torguard wireguard config `wg0.conf`)
  • Adding a torrent via magnet populates the info about size, peers and seeders
  • For example, recently added `ubuntu-20.04.4-desktop-amd64.iso` is showing as 3.1GB with 1214 seeds
  • I have not touched unRaid in the last few weeks, so no changes have been made to the OS (uptime 40+ days)
  • Containers are set to auto-update, but I'm unsure if binhex has released a new container since 2022-03-29
  • My privoxy works perfectly fine
  • Nothing out of the ordinary in the logs (but I may have missed something). See below
  Reveal hidden contents

supervisor.log
 

2022-04-03 15:32:30,955 DEBG received SIGCHLD indicating a child quit
Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2022-04-03 15:32:50.029456 [info] Host is running unRAID
2022-04-03 15:32:50.075089 [info] System information Linux <HOSTNAME REDACTED> 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2022-04-03 15:32:50.130961 [info] OS_ARCH defined as 'x86-64'
2022-04-03 15:32:50.186675 [info] PUID defined as '1000'
2022-04-03 15:32:50.269570 [info] PGID defined as '100'
2022-04-03 15:32:50.382378 [info] UMASK defined as '000'
2022-04-03 15:32:50.434390 [info] Permissions already set for '/config'
2022-04-03 15:32:50.501694 [info] Deleting files in /tmp (non recursive)...
2022-04-03 15:32:50.566203 [info] VPN_ENABLED defined as 'yes'
2022-04-03 15:32:50.614770 [info] VPN_CLIENT defined as 'wireguard'
2022-04-03 15:32:50.661079 [info] VPN_PROV defined as 'custom'
2022-04-03 15:32:50.739894 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2022-04-03 15:32:50.815279 [info] VPN_REMOTE_SERVER defined as '45.128.36.146'
2022-04-03 15:32:50.865800 [info] VPN_REMOTE_PORT defined as '1443'
2022-04-03 15:32:50.907893 [info] VPN_DEVICE_TYPE defined as 'wg0'
2022-04-03 15:32:50.953076 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2022-04-03 15:32:51.003618 [info] LAN_NETWORK defined as '192.168.1.0/24'
2022-04-03 15:32:51.054978 [info] NAME_SERVERS defined as '1.1.1.1,1.0.0.1'
2022-04-03 15:32:51.104507 [info] VPN_USER defined as '<REDACTED>'
2022-04-03 15:32:51.155385 [info] VPN_PASS defined as '<REDACTED>'
2022-04-03 15:32:51.206595 [info] ENABLE_PRIVOXY defined as 'yes'
2022-04-03 15:32:51.262809 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2022-04-03 15:32:51.313165 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2022-04-03 15:32:51.363272 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info'
2022-04-03 15:32:51.413867 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info'
2022-04-03 15:32:51.470195 [info] Starting Supervisor...
2022-04-03 15:32:52,088 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2022-04-03 15:32:52,088 INFO Set uid to user 0 succeeded
2022-04-03 15:32:52,095 INFO supervisord started with pid 7
2022-04-03 15:32:53,099 INFO spawned: 'shutdown-script' with pid 162
2022-04-03 15:32:53,102 INFO spawned: 'start-script' with pid 163
2022-04-03 15:32:53,105 INFO spawned: 'watchdog-script' with pid 164
2022-04-03 15:32:53,106 INFO reaped unknown pid 8 (exit status 0)
2022-04-03 15:32:53,114 DEBG 'shutdown-script' stdout output:
[info] Signal not specified as parameter 2, assuming signal '15' (sigterm)
[info] Process owner not specified as parameter 3, assuming owner 'nobody'

2022-04-03 15:32:53,115 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-04-03 15:32:53,115 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-04-03 15:32:53,116 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-04-03 15:32:53,117 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN
[debug] Environment variables defined as follows
ADDITIONAL_PORTS=
APPLICATION=deluge
BASH=/bin/bash
BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath
BASH_ALIASES=()
BASH_ARGC=()
BASH_ARGV=()
BASH_CMDS=()
BASH_LINENO=([0]="0")
BASH_SOURCE=([0]="/root/start.sh")
BASH_VERSINFO=([0]="5" [1]="1" [2]="12" [3]="1" [4]="release" [5]="x86_64-pc-linux-gnu")
BASH_VERSION='5.1.12(1)-release'
DEBUG=true
DELUGE_DAEMON_LOG_LEVEL=info
DELUGE_WEB_LOG_LEVEL=info
DIRSTACK=()
ENABLE_PRIVOXY=yes
EUID=0
GROUPS=()
HOME=/home/nobody
HOSTNAME=<HOSTNAME REDACTED>
HOSTTYPE=x86_64
HOST_OS=Unraid
IFS=$' \t\n'
LANG=en_GB.UTF-8
LAN_NETWORK=192.168.1.0/24
MACHTYPE=x86_64-pc-linux-gnu
NAME_SERVERS=1.1.1.1,1.0.0.1
OPTERR=1
OPTIND=1
OSTYPE=linux-gnu
OS_ARCH=x86-64
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PGID=100
PIPESTATUS=([0]="0")
PPID=7
PS4='+ '
PUID=1000
PWD=/
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:interactive-comments
SHLVL=1
STRICT_PORT_FORWARD=no
SUPERVISOR_ENABLED=1
SUPERVISOR_GROUP_NAME=start-script
SUPERVISOR_PROCESS_NAME=start-script
TERM=xterm
TZ=America/<REDACTED>
UID=0
UMASK=000
VPN_CLIENT=wireguard
VPN_CONFIG=/config/wireguard/wg0.conf
VPN_DEVICE_TYPE=wg0
VPN_ENABLED=yes
VPN_INPUT_PORTS=
VPN_OPTIONS=
VPN_OUTPUT_PORTS=
VPN_PASS=<REDACTED>
VPN_PROV=custom
VPN_REMOTE_PORT=1443
VPN_REMOTE_PROTOCOL=udp
VPN_REMOTE_SERVER=45.128.36.146
VPN_USER=<REDACTED>
_='[debug] Environment variables defined as follows'
[debug] Directory listing of files in /config/wireguard/ as follows

2022-04-03 15:32:53,128 DEBG 'start-script' stdout output:
total 4
drwxrwxr-x 1 nobody users  16 Apr  3 15:29 .
drwxrwxr-x 1 nobody users 948 Apr  3 15:32 ..
-rwxrwxr-x 1 nobody users 379 Apr  3 15:29 wg0.conf

2022-04-03 15:32:53,129 DEBG 'start-script' stdout output:
[debug] Contents of WireGuard config file '/config/wireguard/wg0.conf' as follows...

2022-04-03 15:32:53,131 DEBG 'start-script' stdout output:
# TorGuard WireGuard Config
[Interface]
PostUp = '/root/wireguardup.sh'
PostDown = '/root/wireguarddown.sh'
PrivateKey = <REDACTED>/4k8=
ListenPort = 42000
MTU = 1292
DNS = 1.1.1.1
Address = 10.13.22.169/24

[Peer]
PublicKey = <REDACTED>=
AllowedIPs = 0.0.0.0/0
Endpoint = 45.128.36.146:1443
PersistentKeepalive = 25

2022-04-03 15:32:53,136 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2022-04-03 15:32:53,142 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2022-04-03 15:32:53,151 DEBG 'start-script' stdout output:
45.128.36.146

2022-04-03 15:32:53,168 DEBG 'start-script' stdout output:
[debug] Show name servers defined for container

2022-04-03 15:32:53,169 DEBG 'start-script' stdout output:
nameserver 1.1.1.1
nameserver 1.0.0.1

2022-04-03 15:32:53,170 DEBG 'start-script' stdout output:
[debug] Show name resolution for VPN endpoint 45.128.36.146

2022-04-03 15:32:53,202 DEBG 'start-script' stdout output:
;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 57986
;; flags: qr aa rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 
;; QUESTION SECTION:
;; 45.128.36.146.	IN	A

;; ANSWER SECTION:

;; AUTHORITY SECTION:
.	86400	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2022040301 1800 900 604800 86400

;; ADDITIONAL SECTION:

;; Query time: 24 msec
;; SERVER: 1.1.1.1
;; WHEN: Sun Apr  3 15:32:53 2022
;; MSG SIZE  rcvd: 106

2022-04-03 15:32:53,203 DEBG 'start-script' stdout output:
[debug] Show contents of hosts file

2022-04-03 15:32:53,204 DEBG 'start-script' stdout output:
127.0.0.1	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
172.17.0.2	<HOSTNAME REDACTED>

2022-04-03 15:32:53,254 DEBG 'start-script' stdout output:
[debug] Docker interface defined as eth0

2022-04-03 15:32:53,262 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2022-04-03 15:32:53,268 DEBG 'start-script' stdout output:
[debug] Docker IP defined as 172.17.0.2

2022-04-03 15:32:53,274 DEBG 'start-script' stdout output:
[debug] Docker netmask defined as 255.255.0.0

2022-04-03 15:32:53,288 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2022-04-03 15:32:53,293 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2022-04-03 15:32:53,295 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2022-04-03 15:32:53,297 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0 
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2 
192.168.1.0/24 via 172.17.0.1 dev eth0 
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1 
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 
broadcast 172.17.0.0 dev eth0 table local proto kernel scope link src 172.17.0.2 
local 172.17.0.2 dev eth0 table local proto kernel scope host src 172.17.0.2 
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.2 

2022-04-03 15:32:53,297 DEBG 'start-script' stdout output:
--------------------
[debug] Modules currently loaded for kernel

2022-04-03 15:32:53,303 DEBG 'start-script' stdout output:
Module                  Size  Used by
xt_connmark            16384  2
xt_comment             16384  3
iptable_raw            16384  1
xt_mark                16384  2
xt_CHECKSUM            16384  1
ipt_REJECT             16384  2
nf_reject_ipv4         16384  1 ipt_REJECT
ip6table_mangle        16384  1
ip6table_nat           16384  1
iptable_mangle         16384  2
nf_tables             180224  0
vhost_net              24576  0
tun                    45056  2 vhost_net
vhost                  28672  1 vhost_net
vhost_iotlb            16384  1 vhost
tap                    24576  1 vhost_net
veth                   24576  0
xt_nat                 16384  31
xt_tcpudp              16384  87
xt_conntrack           16384  3
nf_conntrack_netlink    45056  0
nfnetlink              16384  3 nf_conntrack_netlink,nf_tables
xt_addrtype            16384  3
br_netfilter           24576  0
xfs                   671744  12
nfsd                  106496  11
lockd                  73728  1 nfsd
grace                  16384  1 lockd
sunrpc                237568  14 nfsd,lockd
md_mod                 45056  12
ipmi_devintf           16384  0
iptable_nat            16384  4
xt_MASQUERADE          16384  25
nf_nat                 40960  4 ip6table_nat,xt_nat,iptable_nat,xt_MASQUERADE
nf_conntrack          110592  6 xt_conntrack,nf_nat,xt_nat,nf_conntrack_netlink,xt_connmark,xt_MASQUERADE
nf_defrag_ipv6         16384  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
wireguard              81920  0
curve25519_x86_64      32768  1 wireguard
libcurve25519_generic    49152  2 curve25519_x86_64,wireguard
libchacha20poly1305    16384  1 wireguard
chacha_x86_64          28672  1 libchacha20poly1305
poly1305_x86_64        28672  1 libchacha20poly1305
ip6_udp_tunnel         16384  1 wireguard
udp_tunnel             20480  1 wireguard
libblake2s             16384  1 wireguard
blake2s_x86_64         20480  1 libblake2s
libblake2s_generic     20480  1 blake2s_x86_64
libchacha              16384  1 chacha_x86_64
ip6table_filter        16384  1
ip6_tables             28672  3 ip6table_filter,ip6table_nat,ip6table_mangle
iptable_filter         16384  2
ip_tables              28672  6 iptable_filter,iptable_raw,iptable_nat,iptable_mangle
x_tables               28672  17 ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,xt_comment,ip6_tables,ipt_REJECT,xt_connmark,iptable_raw,ip_tables,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark
bonding               114688  0
intel_powerclamp       16384  0
coretemp               16384  0
kvm_intel             212992  0
kvm                   421888  1 kvm_intel
mpt3sas               237568  8
ahci                   40960  6
crc32c_intel           24576  3
i2c_i801               24576  0
libahci                28672  1 ahci
raid_class             16384  1 mpt3sas
i2c_smbus              16384  1 i2c_i801
i5500_temp             16384  0
intel_cstate           16384  0
e1000e                180224  0
i2c_core               45056  2 i2c_smbus,i2c_i801
input_leds             16384  0
ipmi_si                49152  0
scsi_transport_sas     32768  1 mpt3sas
intel_uncore          131072  0
led_class              16384  1 input_leds
i7core_edac            28672  0
button                 16384  0
acpi_cpufreq           16384  1

2022-04-03 15:32:53,308 DEBG 'start-script' stdout output:
iptable_mangle         16384  2
ip_tables              28672  6 iptable_filter,iptable_raw,iptable_nat,iptable_mangle
x_tables               28672  17 ip6table_filter,xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,xt_comment,ip6_tables,ipt_REJECT,xt_connmark,iptable_raw,ip_tables,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark

2022-04-03 15:32:53,309 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2022-04-03 15:32:53,396 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2022-04-03 15:32:53,398 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 45.128.36.146/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i wg0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 45.128.36.146/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 8118 -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

2022-04-03 15:32:53,400 DEBG 'start-script' stdout output:
--------------------

2022-04-03 15:32:53,405 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2022-04-03 15:32:53,425 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2022-04-03 15:32:53,441 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2022-04-03 15:32:53,444 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2022-04-03 15:32:53,455 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.13.22.169/24 dev wg0

2022-04-03 15:32:53,457 DEBG 'start-script' stderr output:
[#] ip link set mtu 1292 up dev wg0

2022-04-03 15:32:53,473 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x

2022-04-03 15:32:53,491 DEBG 'start-script' stderr output:
could not detect a useable init system

2022-04-03 15:32:53,557 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2022-04-03 15:32:53,559 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2022-04-03 15:32:53,560 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2022-04-03 15:32:53,562 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2022-04-03 15:32:53,567 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2022-04-03 15:32:53,571 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2022-04-03 15:32:53,578 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2022-04-03 15:32:53,583 DEBG 'start-script' stdout output:
[debug] Waiting for valid local and gateway IP addresses from tunnel...

2022-04-03 15:32:54,606 DEBG 'start-script' stdout output:
[debug] Valid local IP address from tunnel acquired '10.13.22.169'

2022-04-03 15:32:54,607 DEBG 'start-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-04-03 15:32:54,660 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-04-03 15:32:54,662 DEBG 'start-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.251.40.164'

2022-04-03 15:32:54,668 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2022-04-03 15:32:54,717 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.176.196'

2022-04-03 15:32:54,911 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 45.128.36.146

2022-04-03 15:32:54,913 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2022-04-03 15:32:54,914 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2022-04-03 15:32:54,921 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2022-04-03 15:32:54,936 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2022-04-03 15:32:54,937 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.13.22.169 different, marking for reconfigure

2022-04-03 15:32:54,963 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2022-04-03 15:32:54,970 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2022-04-03 15:32:54,978 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2022-04-03 15:32:54,979 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2022-04-03 15:32:55,345 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.13.22.169'
[info] Deluge key 'listen_interface' will have a new value '10.13.22.169'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-04-03 15:32:55,635 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-04-03 15:32:55,940 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of '<REDACTED>'
[info] Deluge key 'default_daemon' will have a new value '<REDACTED>'
[info] Writing changes to Deluge config file '/config/web.conf'...

2022-04-03 15:32:56,774 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2022-04-03 15:32:57,311 DEBG 'watchdog-script' stderr output:
/config/plugins/SimpleExtractor-1.4-py3.8.egg/deluge_simpleextractor/core.py:129: SyntaxWarning: "is not" with a literal. Did you mean "!="?

2022-04-03 15:32:57,315 DEBG 'watchdog-script' stderr output:
/config/plugins/SimpleExtractor-1.4-py3.8.egg/deluge_simpleextractor/core.py:129: SyntaxWarning: "is not" with a literal. Did you mean "!="?

2022-04-03 15:32:57,327 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2022-04-03 15:33:03,622 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2022-04-03 15:33:03,622 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2022-04-03 15:33:03,623 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2022-04-03 15:33:03,626 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2022-04-03 15:33:04,640 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2022-04-03 15:33:04,648 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2022-04-03 15:33:04,648 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.13.22.169
[debug] Deluge IP is 10.13.22.169

2022-04-03 15:33:34,651 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-04-03 15:33:34,706 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.72.100'

2022-04-03 15:33:34,707 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2022-04-03 15:33:34,723 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2022-04-03 15:33:34,745 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.13.22.169
[debug] Deluge IP is 10.13.22.169

 

 

@binhex have you seen this issue before? I'm a bit perplexed by it, and there has been no download/upload activity for about a week. Assuming this was a VPN provider issue, as there does not seem to have been any updates to this container or unRAID OS recently, and everything is working again

Edited by Bob1215
issue has been resolved
Link to comment

EDIT:  Solution

 

 

 

Today I setup a separate physical nic for unRAID server and another physical nic for my docker containers and VM's.  I have everything working perfectly except for the fact that I cannot access the WebGUI for binhex-delugevpn.  I can access binhex-delugevpn GUI by using my Win10 VM with Deluge 2.0.4.dev38 setup as a thin client and connecting to the binhex-delugevpn docker that way.  This is not a VPN issue or normal WebGUI issue.  In fact, this is the supervisor.log:

 

 

2022-04-09 02:01:49,314 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2022-04-09 02:01:49,314 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

 

I can access all other docker WebGUI's including binhex-nzbget, binhex-krusader, PlexServer...

 

This is my network config in unRAID, docker config, and delugevpn config.

 

network.thumb.png.e0fd072a0ababebf4ac59c85d19b7885.pngnetwork.thumb.png.e0fd072a0ababebf4ac59c85d19b7885.png

 

docker.thumb.png.ccc904bdf777c5eab84fbca158174bb7.png

 

deluge.thumb.png.598c8fb874d4aaf7122e35f3b91d71b5.png

 

Any ideas on what the problem may be?

 

Thanks,

craigr

 

 

Edited by craigr
Solution link added
Link to comment
On 4/9/2022 at 8:17 AM, JonathanM said:

 

 EDIT:  Solution

 

 

Thanks Jonathan.  I had read that already and just went through the motions anyway to be sure.  However, I don't see where my error lies?  Could you please give me just a little bit more of a push?

 

For what it's worth, I had things running well, but not quite technically correct.  I used Ronaldus' posts in this thread to get it to what I thought is perfect: 

 

I have other questions, but I don't want to derail this thread by going off topic.

 

Thank you so much!

craigr

Edited by craigr
Solution link added
Link to comment

Can anyone help with my issue? I've been using DelugeVPN for years now and today the docker is started but not finishing the boot enough to get the UI started. Just keeps looping per the log. 

i've attached my log. If i set the VPN to no in the docker it boots up fine so clearly its something with the VPN.

 So far I have tried - removing and reloading the docker and creating new Configs from my VPN (Torguard) and both have not didn't resolved the issue.

 

 

Appreciate any help.

supervisord.log

Link to comment
38 minutes ago, Beholder said:

Can anyone help with my issue? I've been using DelugeVPN for years now and today the docker is started but not finishing the boot enough to get the UI started. Just keeps looping per the log. 

i've attached my log. If i set the VPN to no in the docker it boots up fine so clearly its something with the VPN.

 So far I have tried - removing and reloading the docker and creating new Configs from my VPN (Torguard) and both have not didn't resolved the issue.

 

 

Appreciate any help.

supervisord.log 17.9 kB · 1 download

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

Scroll down to Q17.

Link to comment

Hi All, first post ever in the unraid forums, had a power outage and now since rebooting i cannot access the WebUI of DelugeVPN, JackettVPN or NZBGETVPN but they're all functioning correctly and all other dockers can see them, i just cannot access the webui of these ones in particular, which are all VPN based ones. Any idea what the go might be?

 

I tried removing them and installing again from scratch, tried restoring app data but neither of these seem to help. Even tried removing the docker, manually deleting the app data folder and installing from scratch but still, no go. 

Link to comment
7 hours ago, Coshy93 said:

Hi All, first post ever in the unraid forums, had a power outage and now since rebooting i cannot access the WebUI of DelugeVPN, JackettVPN or NZBGETVPN but they're all functioning correctly and all other dockers can see them, i just cannot access the webui of these ones in particular, which are all VPN based ones. Any idea what the go might be?

 

I tried removing them and installing again from scratch, tried restoring app data but neither of these seem to help. Even tried removing the docker, manually deleting the app data folder and installing from scratch but still, no go. 

Have you checked the log file?  I bet you are having an issue reconnecting to your VPN.

 

craigr

Link to comment
7 hours ago, craigr said:

Have you checked the log file?  I bet you are having an issue reconnecting to your VPN.

 

craigr

Well, i would have thought that if i was having a VPN issue, the docker therefore wouldn't work? But they are working fine. Also, in the log file, it's making it passed all the VPN stage and getting to the WebUI started section. I tested without the ovpn files and it got hung up at the VPN stage, put the file back in and again, went to the webUI stage and the docker started working fine. Just, couldn't get to its webUI. 

Link to comment

Hey binhex;

I've got your delugevpn docker image pulled and (i think) configured correctly to work with nordvpn,  but when I launch it seems to get stuck in an eternal startup loop, do you have any ideas?

 

pastbin of logs: https://pastebin.com/2ZiMeHvJ

 

I've set up a docker-compose file for it which may be the root of my issues....

version: '3.3'
services:
    arch-delugevpn:
        ports:
            - '192.168.1.200:8112:8112'
            - '192.168.1.200:8118:8118'
            - '192.168.1.200:58846:58846'
            - '192.168.1.200:58946:58946'
        container_name: 'Deluge'
        volumes:
            - '/home/andrew/transmission/data:/data'
            - '/home/andrew/transmission:/config'
            - '/etc/localtime:/etc/localtime:ro'
        environment:
            - VPN_ENABLED=yes
            - VPN_USER=<USER>
            - VPN_PASS=<PASSWORD>
            - VPN_PROV=custom
            - VPN_CLIENT=openvpn
            - VPN_OPTIONS=
            - STRICT_PORT_FORWARD=yes
            - ENABLE_PRIVOXY=no
            - LAN_NETWORK=192.168.1.0/24
            - NAME_SERVERS=
            - DELUGE_DAEMON_LOG_LEVEL=info
            - DELUGE_WEB_LOG_LEVEL=info
            - VPN_INPUT_PORTS=
            - VPN_OUTPUT_PORTS=
            - DEBUG=true
            - UMASK=000
            - PUID=1000
            - PGID=1000
        image: binhex/arch-delugevpn

any suggestions?

Edit: also, I have the selected nordvpn .ovp file in the generated openvpn folder

Edited by Solderfiend
adding information
Link to comment
Hey binhex;
I've got your delugevpn docker image pulled and (i think) configured correctly to work with nordvpn,  but when I launch it seems to get stuck in an eternal startup loop, do you have any ideas?
 
pastbin of logs: https://pastebin.com/2ZiMeHvJ
 
I've set up a docker-compose file for it which may be the root of my issues....
version: '3.3'services:   arch-delugevpn:       ports:           - '192.168.1.200:8112:8112'           - '192.168.1.200:8118:8118'           - '192.168.1.200:58846:58846'           - '192.168.1.200:58946:58946'       container_name: 'Deluge'       volumes:           - '/home/andrew/transmission/data:/data'           - '/home/andrew/transmission:/config'           - '/etc/localtime:/etc/localtime:ro'       environment:           - VPN_ENABLED=yes           - VPN_USER=           - VPN_PASS=           - VPN_PROV=custom           - VPN_CLIENT=openvpn           - VPN_OPTIONS=           - STRICT_PORT_FORWARD=yes           - ENABLE_PRIVOXY=no           - LAN_NETWORK=192.168.1.0/24           - NAME_SERVERS=           - DELUGE_DAEMON_LOG_LEVEL=info           - DELUGE_WEB_LOG_LEVEL=info           - VPN_INPUT_PORTS=           - VPN_OUTPUT_PORTS=           - DEBUG=true           - UMASK=000           - PUID=1000           - PGID=1000       image: binhex/arch-delugevpn

any suggestions?
Edit: also, I have the selected nordvpn .ovp file in the generated openvpn folder

Authentication failure, from your log:-
2022-04-14 18:45:31 SIGTERM[soft,auth-failure] received, process exiting

Check your username and password

Sent from my CLT-L09 using Tapatalk

Link to comment
On 4/9/2022 at 2:36 AM, craigr said:

Today I setup a separate physical nic for unRAID server and another physical nic for my docker containers and VM's.  I have everything working perfectly except for the fact that I cannot access the WebGUI for binhex-delugevpn.  I can access binhex-delugevpn GUI by using my Win10 VM with Deluge 2.0.4.dev38 setup as a thin client and connecting to the binhex-delugevpn docker that way.  This is not a VPN issue or normal WebGUI issue.  In fact, this is the supervisor.log:

 

2022-04-09 02:01:49,314 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2022-04-09 02:01:49,314 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

 

I can access all other docker WebGUI's including binhex-nzbget, binhex-krusader, PlexServer...

 

This is my network config in unRAID, docker config, and delugevpn config.

 

network.thumb.png.e0fd072a0ababebf4ac59c85d19b7885.pngnetwork.thumb.png.e0fd072a0ababebf4ac59c85d19b7885.png

 

docker.thumb.png.ccc904bdf777c5eab84fbca158174bb7.png

 

deluge.thumb.png.598c8fb874d4aaf7122e35f3b91d71b5.png

 

Finally figured it out.  Settings > Docker > IPv4 custom network on interface br1:

 

docker2.thumb.png.353253cf7afe2d15b8c1ff36fe9d18a5.png

 

Don't know why I didn't see it sooner.

 

craigr

Link to comment
46 minutes ago, wgstarks said:

What did you figure out? Were you trying to access the wrong IP?

I have dual nics; one for direct internet connection of dockers and VM's to the multi-gig LAN port on my router.  The other nic is for unRAID server.  The docker and VM NIC connects to my router's 2.5Gb LAN port.  The second nic connects to my Brocade ICX6450-24P at 10Gb to serve video's all over the house.

 

When I setup the second nic, I could no longer get the Binhex-DelugeVPN docker WebGUI anymore and couldn't figure out why.  I could connect to it through Deluge installed on Windows in thin client mode, but not with a browser.  The problem was, that in the DOCKER setup page in unRAID for DHCP pool, I had /25 (default) and it obviously needed to be /24 because the IP address I assigned the Binhex-DelugeVPN docker is 192.168.1.200.  Now the WebGUI works as it should.

 

lan.png.03ca566ad52095c8e35abe5f28e53244.png

 

craigr

Link to comment

Screenshot of binhex-nzbget docker pulling in files from the internet at ~250MB/sec:

 

 

nzbget.png.593dacdddfde40eb86f93f69c9ebe68f.png

 

This is totally sick!!!

 

Untitled.png.b31df083d2312e8bdb114aaa4cee56a6.png

 

 

Some days I can pull in 3000Mb/s, but obviously than it saturates the 2.5Gb LAN port.

 

craigr

Edited by craigr
Link to comment

I am having an issues with my deluge-VPN docker.

 

it has been as stable as a rock for over 3 years with no issues, but of late I have see that evertime I am downloading something within the deluge docker, then my network traffic drops from a avg of 100mbs down to 1mb.  and this only happens when I am downloading something

 

my setup is that I have all my binhex traffic going through the deluge docker "Sonarr, Radar, Jacket"  with a kill switch within my pfsense.

 

any ideals on why this is happening ?

 

I have attached my log file in the help that his might help you.

and I look forward to hearing from you

 

 

 

Edited by chris_netsmart
Link to comment
7 minutes ago, chris_netsmart said:

I am having an issues with my deluge-VPN docker.

 

it has been as stable as a rock for over 3 years with no issues, but of late I have see that evertime I am downloading something within the deluge docker, then my network traffic drops from a avg of 100mbs down to 1mb.  and this only happens when I am downloading something

 

my setup is that I have all my binhex traffic going through the deluge docker "Sonarr, Radar, Jacket"  with a kill switch within my pfsense.

 

any ideals on why this is happening ?

 

I have attached my log file in the help that his might help you.

and I look forward to hearing from you

 

 

Log.txt 6.95 kB · 0 downloads

you realise you are running this with the vpn disabled right?, so no protection, from your log:-
 

2022-04-17 03:28:38.281269 [info] VPN_ENABLED defined as 'no'
2022-04-17 03:28:38.303147 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE

as to the cause of the slowdown, its possible that your isp is throttling your torrent traffic as its visible, and/or you havent setup port forwarding correctly.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.