Jump to content
binhex

[Support] binhex - DelugeVPN

4108 posts in this topic Last Reply

Recommended Posts

3 minutes ago, binhex said:

yes, point all apps at privoxy, then shutdown delugevpn, if any of the apps can still search then they arent configure correctly, if none of them can search then its working as designed - start delugevpn again.

thanks for the info,  I can see how I can test the app's but how can I test Deulge ?

 

Edited by chris_netsmart

Share this post


Link to post

Hello all, pretty new here and new to all of this Docker stuff. Have an issue at the moment. I changed some drives around, and then ended up having to recreate my docker containers. Now, the deluge docker is saying that Permission is denied on the directories it's supposed to be using, but it's using the same directory links and such that it was using before I had to re-do my dockers. It's not making sense to me, and I'm unsure how to go about fixing it or getting help, so I wanted to post here and see if anyone would be able to help. 

 

I have used spaceinvaderone's videos, googled, can't find a working fix. Please let me know what I need to do to be able to get some help!

Share this post


Link to post
3 minutes ago, BennyD said:

Please let me know what I need to do to be able to get some help!

First link in the Docker FAQ:

 

Share this post


Link to post
25 minutes ago, trurl said:

First link in the Docker FAQ:

 

Thank you... I'm not real sure why I didn't notice that at first. Here is the Run and the Log.

 

Quote

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='' -e 'VPN_PASS'='' -e 'VPN_PROV'='custom' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.50.0/24' -e 'NAME_SERVERS'='209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4' -e 'DEBUG'='true' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/Downloads/':'/downloads':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 

6f727dbce026583b38f4e32e10bdf156d85d25f8638383d16d4235693e2e80a7

The command finished successfully!

 

Quote

ErrorWarningSystemArrayLogin



2019-01-10 17:03:12,857 DEBG 'start-script' stdout output:
[debug] Show contents of hosts file

2019-01-10 17:03:12,857 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 6f727dbce026

2019-01-10 17:03:12,860 DEBG 'start-script' stdout output:
[debug] Docker interface defined as eth0

2019-01-10 17:03:12,863 DEBG 'start-script' stdout output:
[debug] Docker IP defined as 172.17.0.2

2019-01-10 17:03:12,865 DEBG 'start-script' stdout output:
[debug] Docker netmask defined as 255.255.0.0

2019-01-10 17:03:12,870 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2019-01-10 17:03:12,872 DEBG 'start-script' stdout output:
[info] Adding 192.168.50.0/24 as route via docker eth0

2019-01-10 17:03:12,873 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-01-10 17:03:12,873 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

2019-01-10 17:03:12,874 DEBG 'start-script' stdout output:
192.168.50.0/24 via 172.17.0.1 dev eth0

2019-01-10 17:03:12,874 DEBG 'start-script' stdout output:
--------------------
[debug] Modules currently loaded for kernel

2019-01-10 17:03:12,875 DEBG 'start-script' stdout output:
Module Size Used by
dm_mod 110592 1
dax 20480 1 dm_mod
xt_CHECKSUM 16384 1
iptable_mangle 16384 2
ipt_REJECT 16384 2
ebtable_filter 16384 0
ebtables 32768 1 ebtable_filter
veth 16384 0
ip6table_filter 16384 0
ip6_tables 24576 1 ip6table_filter
vhost_net 20480 1
tun 36864 4 vhost_net
vhost 32768 1 vhost_net
tap 20480 1 vhost_net
xt_nat 16384 11
ipt_MASQUERADE 16384 15
iptable_nat 16384 1
nf_conntrack_ipv4 16384 29
nf_defrag_ipv4 16384 1 nf_conntrack_ipv4
nf_nat_ipv4 16384 2 ipt_MASQUERADE,iptable_nat
iptable_filter 16384 2
ip_tables 24576 5 iptable_filter,iptable_nat,iptable_mangle
nf_nat 24576 2 nf_nat_ipv4,xt_nat
xfs 663552 3
md_mod 49152 3
bonding 110592 0
x86_pkg_temp_thermal 16384 0
intel_powerclamp 16384 0
coretemp 16384 0
kvm_intel 196608 8
kvm 364544 1 kvm_intel
crct10dif_pclmul 16384 0
crc32_pclmul 16384 0
crc32c_intel 24576 0
ghash_clmulni_intel 16384 0
pcbc 16384 0
aesni_intel 200704 0
aes_x86_64 20480 1 aesni_intel
crypto_simd 16384 1 aesni_intel
cryptd 20480 3 crypto_simd,ghash_clmulni_intel,aesni_intel
hid_logitech_hidpp 32768 0
i2c_i801 24576 0
i2c_core 40960 1 i2c_i801
glue_helper 16384 1 aesni_intel
intel_cstate 16384 0
ahci 40960 13
intel_uncore 102400 0
libahci 28672 1 ahci
mxm_wmi 16384 0
wmi 20480 1 mxm_wmi
intel_rapl_perf 16384 0
hid_logitech_dj 20480 0
pcc_cpufreq 16384 0
e1000e 180224 0
video 40960 0
backlight 16384 1 video
acpi_pad 20480 0
button 16384 0

2019-01-10 17:03:12,877 DEBG 'start-script' stdout output:
iptable_mangle 16384 2
ip_tables 24576 5 iptable_filter,iptable_nat,iptable_mangle

2019-01-10 17:03:12,877 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2019-01-10 17:03:12,930 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-01-10 17:03:12,932 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 443 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 192.168.50.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.50.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 443 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 192.168.50.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.50.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2019-01-10 17:03:12,932 DEBG 'start-script' stdout output:
--------------------

2019-01-10 17:03:12,932 DEBG 'start-script' stdout output:
[debug] OpenVPN command line:- /usr/bin/openvpn --daemon --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV 'custom' --setenv DEBUG 'true' --setenv VPN_DEVICE_TYPE 'tun0' --setenv VPN_REMOTE '96.9.247.11' --script-security 2 --up /root/openvpnup.sh --up-delay --up-restart --writepid /root/openvpn.pid --remap-usr1 SIGHUP --log-append /dev/stdout --pull-filter ignore 'up' --pull-filter ignore 'down' --pull-filter ignore 'route-ipv6' --pull-filter ignore 'ifconfig-ipv6' --pull-filter ignore 'tun-ipv6' --pull-filter ignore 'persist-tun' --pull-filter ignore 'reneg-sec' --auth-user-pass credentials.conf --cd /config/openvpn --config '/config/openvpn/us2706.nordvpn.com.tcp.ovpn'
[info] Starting OpenVPN...

2019-01-10 17:03:12,946 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:12 2019 WARNING: file 'credentials.conf' is group or others accessible
Thu Jan 10 17:03:12 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Thu Jan 10 17:03:12 2019 library versions: OpenSSL 1.1.1 11 Sep 2018, LZO 2.10

2019-01-10 17:03:12,946 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:12 2019 WARNING: --ping should normally be used with --ping-restart or --ping-exit
Thu Jan 10 17:03:12 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Thu Jan 10 17:03:12 2019 NOTE: --fast-io is disabled since we are not using UDP

2019-01-10 17:03:12,947 DEBG 'start-script' stdout output:
[info] OpenVPN started
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:03:12,947 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:12 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Thu Jan 10 17:03:12 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication

2019-01-10 17:03:12,947 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:12 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]96.9.247.11:443

2019-01-10 17:03:12,947 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:12 2019 Socket Buffers: R=[87380->87380] S=[65536->65536]
Thu Jan 10 17:03:12 2019 Attempting to establish TCP connection with [AF_INET]96.9.247.11:443 [nonblock]

2019-01-10 17:03:13,947 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:13 2019 TCP connection established with [AF_INET]96.9.247.11:443
Thu Jan 10 17:03:13 2019 TCP_CLIENT link local: (not bound)
Thu Jan 10 17:03:13 2019 TCP_CLIENT link remote: [AF_INET]96.9.247.11:443

2019-01-10 17:03:13,983 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:13 2019 TLS: Initial packet from [AF_INET]96.9.247.11:443, sid=3e0e8ba8 d7250e7a

2019-01-10 17:03:14,141 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:14 2019 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA

2019-01-10 17:03:14,141 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:14 2019 VERIFY OK: depth=1, C=PA, O=NordVPN, CN=NordVPN CA3

2019-01-10 17:03:14,141 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:14 2019 VERIFY KU OK
Thu Jan 10 17:03:14 2019 Validating certificate extended key usage
Thu Jan 10 17:03:14 2019 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Thu Jan 10 17:03:14 2019 VERIFY EKU OK
Thu Jan 10 17:03:14 2019 VERIFY OK: depth=0, CN=us2706.nordvpn.com

2019-01-10 17:03:14,385 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:14 2019 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Thu Jan 10 17:03:14 2019 [us2706.nordvpn.com] Peer Connection Initiated with [AF_INET]96.9.247.11:443

2019-01-10 17:03:15,528 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 SENT CONTROL [us2706.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2019-01-10 17:03:15,655 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 103.86.96.100,dhcp-option DNS 103.86.99.100,sndbuf 524288,rcvbuf 524288,explicit-exit-notify,comp-lzo no,route-gateway 10.7.7.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.7.7.2 255.255.255.0,peer-id 0,cipher AES-256-GCM'

2019-01-10 17:03:15,655 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: timers and/or timeouts modified
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: --explicit-exit-notify can only be used with --proto udp
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: compression parms modified
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
Thu Jan 10 17:03:15 2019 Socket Buffers: R=[367360->1048576] S=[87040->1048576]
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: --ifconfig/up options modified
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: route options modified
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: route-related options modified
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: peer-id set
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: adjusting link_mtu to 1659
Thu Jan 10 17:03:15 2019 OPTIONS IMPORT: data channel crypto options modified
Thu Jan 10 17:03:15 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu Jan 10 17:03:15 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu Jan 10 17:03:15 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu Jan 10 17:03:15 2019 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:02

2019-01-10 17:03:15,655 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 TUN/TAP device tun0 opened

2019-01-10 17:03:15,656 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 TUN/TAP TX queue length set to 100
Thu Jan 10 17:03:15 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Thu Jan 10 17:03:15 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-01-10 17:03:15,656 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 /usr/bin/ip addr add dev tun0 10.7.7.2/24 broadcast 10.7.7.255

2019-01-10 17:03:15,657 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 /root/openvpnup.sh tun0 1500 1587 10.7.7.2 255.255.255.0 init

2019-01-10 17:03:15,659 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 /usr/bin/ip route add 96.9.247.11/32 via 172.17.0.1

2019-01-10 17:03:15,660 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 /usr/bin/ip route add 0.0.0.0/1 via 10.7.7.1

2019-01-10 17:03:15,661 DEBG 'start-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:03:15,661 DEBG 'start-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:03:15,662 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 /usr/bin/ip route add 128.0.0.0/1 via 10.7.7.1

2019-01-10 17:03:15,663 DEBG 'start-script' stdout output:
Thu Jan 10 17:03:15 2019 Initialization Sequence Completed

2019-01-10 17:03:15,669 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:03:15,669 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.7.7.2 different, marking for reconfigure

2019-01-10 17:03:15,671 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:03:15,672 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2019-01-10 17:03:15,674 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-01-10 17:03:15,771 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:03:15,774 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'
[debug] Attempting to get external IP using Name Server 'ns1.google.com'...
[debug] VPN provider custom is != pia, skipping incoming port detection

2019-01-10 17:03:15,775 DEBG 'privoxy-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:03:15,775 DEBG 'privoxy-script' stdout output:
[info] Configuring Privoxy...

2019-01-10 17:03:15,917 DEBG 'privoxy-script' stdout output:
[info] All checks complete, starting Privoxy...

2019-01-10 17:03:15,918 DEBG 'privoxy-script' stderr output:
2019-01-10 17:03:15.918 14de57074100 Info: Privoxy version 3.0.26
2019-01-10 17:03:15.918 14de57074100 Info: Program name: /usr/bin/privoxy

2019-01-10 17:03:15,919 DEBG 'privoxy-script' stderr output:
2019-01-10 17:03:15.919 14de57074100 Fatal error: can't load re_filterfile '/config/privoxy/default.filter': No such file or directory

2019-01-10 17:03:15,920 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 22964851813552 for <Subprocess at 22964851497872 with name privoxy-script in state RUNNING> (stdout)>
2019-01-10 17:03:15,920 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 22964851513104 for <Subprocess at 22964851497872 with name privoxy-script in state RUNNING> (stderr)>
2019-01-10 17:03:15,920 INFO exited: privoxy-script (exit status 1; not expected)
2019-01-10 17:03:15,920 DEBG received SIGCLD indicating a child quit
2019-01-10 17:03:15,932 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 96.9.247.12

2019-01-10 17:03:15,977 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '96.9.247.12'

2019-01-10 17:03:15,978 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2019-01-10 17:03:16,119 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface currently defined as 0.0.0.0
[info] Deluge listening interface will be changed to 0.0.0.0
[info] Saving changes to Deluge config file /config/core.conf...

2019-01-10 17:03:16,267 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2019-01-10 17:03:17,247 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-01-10 17:03:17,247 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-01-10 17:03:17,247 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started
[debug] VPN IP is 10.7.7.2
[debug] Deluge IP is 10.7.7.2

2019-01-10 17:03:47,248 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:03:47,367 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:03:47,372 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '96.9.247.12'

2019-01-10 17:03:47,372 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.7.7.2
[debug] Deluge IP is 10.7.7.2

2019-01-10 17:04:17,373 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:04:17,487 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:04:17,492 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '96.9.247.12'

2019-01-10 17:04:17,492 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.7.7.2
[debug] Deluge IP is 10.7.7.2

2019-01-10 17:04:47,493 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:04:47,608 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:04:47,614 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '96.9.247.12'

2019-01-10 17:04:47,614 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.7.7.2
[debug] Deluge IP is 10.7.7.2

2019-01-10 17:05:17,615 DEBG 'watchdog-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2019-01-10 17:05:17,728 DEBG 'watchdog-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.7.7.2'

2019-01-10 17:05:17,734 DEBG 'watchdog-script' stdout output:
[debug] External IP address from tunnel is '96.9.247.12'

2019-01-10 17:05:17,734 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.7.7.2
[debug] Deluge IP is 10.7.7.2

Sorry, I'm unsure on how to make this smaller!

Edited by BennyD

Share this post


Link to post
2 minutes ago, wgstarks said:

@BennyD You’ll want to change your vpn password that was in your post.

OUCH! I didn't even notice!! Thank you!

Edited by BennyD

Share this post


Link to post
6 hours ago, BennyD said:

Now, the deluge docker is saying that Permission is denied on the directories it's supposed to be using

assuming the issue is file permisisons on the host side, you can reset them by doing the following:-

 

1. stop the container

2. delete the file /config/perms.txt

3. start the container.

 

this should then set permissions to match the PUID and PGID as defined by the container.

Share this post


Link to post
3 hours ago, binhex said:

assuming the issue is file permisisons on the host side, you can reset them by doing the following:-

 

1. stop the container

2. delete the file /config/perms.txt

3. start the container.

 

this should then set permissions to match the PUID and PGID as defined by the container.

Thank you. I will try this when I get home this afternoon. 

Share this post


Link to post

Hi. I have just installed the Deluge VPN onto my Unraid, but following the attached website URl  

 

I am able to start the Deluge with no issues but when I try and open a URL to http://192.168.0.9:8112/  I am informed that the following

Quote

 

This site can’t be reached

192.168.0.9 refused to connect.

Search Google for 192 168 8112

ERR_CONNECTION_REFUSED

 

 

I have gone through all my settings in relations to the website and I can't find anything wrong,  can someone please advice.

I also have attached my Debug file.

supervisord.log

Share this post


Link to post

Anyone else get issue of some torrents never connecting to peers or seeds?

Several times a torrent just stops doing anything even though the same torrent on my local torrent client connects to peers right away.

Share this post


Link to post
40 minutes ago, chris_netsmart said:

Hi. I have just installed the Deluge VPN onto my Unraid, but following the attached website URl  

 

I am able to start the Deluge with no issues but when I try and open a URL to http://192.168.0.9:8112/  I am informed that the following

 

I have gone through all my settings in relations to the website and I can't find anything wrong,  can someone please advice.

I also have attached my Debug file.

supervisord.log

1. The Netherlands doesn't support port forwarding anymore, switch to another supported endpoint.

2. Check your credentials, the ones you put in are failing. Please use only 0-9,a-z,A-Z characters. From your log:

Quote

AUTH: Received control message: AUTH_FAILED

 

Share this post


Link to post

Strike.  Thanks for the reply.   

 

Bit confused.  Are you saying that have enter in my username and password wrong ?

 

And i will change my location to france when i get home and retry.

Edited by chris_netsmart

Share this post


Link to post
1 minute ago, chris_netsmart said:

Bit confused.  Are you saying that have enter in my username and password wrong ?

Yes, either you have put in the wrong username/password or it contains special characters which can be problematic.

Share this post


Link to post
8 hours ago, binhex said:

assuming the issue is file permisisons on the host side, you can reset them by doing the following:-

 

1. stop the container

2. delete the file /config/perms.txt

3. start the container.

 

this should then set permissions to match the PUID and PGID as defined by the container.

 

I'm not finding a /config/perms.txt. I can see a perms.txt inside of the delugevpn container, but deleting that and restarting didn't fix the issue. I'm not finding a config directory anywhere.

Edited by BennyD

Share this post


Link to post
57 minutes ago, BennyD said:

I'm not finding a config directory anywhere.

/config will be whatever you have mapped in your docker template. Usually it’s /mnt/cache/appdata/<nameofdocker> but that is user configurable.

Edited by wgstarks

Share this post


Link to post
6 minutes ago, wgstarks said:

/config will be whatever you have mapped in your docker template. Usually it’s /mnt/cache/appdata but that is user configurable.

Ahh! Right. Sorry, I'm a total noob to all of this stuff. So I did delete the correct perms.txt and restarted the docker with the same result. I'm still stuck with deluge telling me "Status: Permission denied: /data/incomplete/" This location should be correct, I have the /data in the settings of the docket mapped to /mnt/user/Downloads/ and inside of there is my incomplete, complete, and unzipped_torrents directories. So, using /data/incomplete should be the correct pathing?

Edited by BennyD

Share this post


Link to post

Deluge has permissions configurations in its settings menu. You left those off right? No special permissions configured inside the app itself?

Share this post


Link to post
3 minutes ago, wgstarks said:

Deluge has permissions configurations in its settings menu. You left those off right? No special permissions configured inside the app itself?

Correct.

Share this post


Link to post

You could try running docker safe new permissions tool and see if that helps. Tools>docker safe new perms. You can install it from the apps tab if you haven’t already.

 

Edit: make sure it’s the docker safe version of the new permissions tool.

Edited by wgstarks

Share this post


Link to post
33 minutes ago, wgstarks said:

You could try running docker safe new permissions tool and see if that helps. Tools>docker safe new perms. You can install it from the apps tab if you haven’t already.

Can't find anything in the Apps tab for anything to do with docker permissions, I have New Permissions in the Tools tab, I ran new permissions on the Downloads folder, but not sure if this is completing what you're suggesting, it had no effect.

 

 

Just noticed you had made an edit. Trying something now. Not sure how to make sure I have a docker safe version of new permissions but it's running, so let's hope! LOL. 

Edited by BennyD

Share this post


Link to post

@BennyD From your docker run command post further up your mappings are: '/mnt/user/Downloads/':'/downloads

Have you changed this after you posted? please post a new docker run command and a screenshot of your Downloads settings in deluge. Be sure to redact username/password from the ducker run command.

Share this post


Link to post
13 minutes ago, strike said:

@BennyD From your docker run command post further up your mappings are: '/mnt/user/Downloads/':'/downloads

Have you changed this after you posted? please post a new docker run command and a screenshot of your Downloads settings in deluge. Be sure to redact username/password from the ducker run command.

I have not changed this since making the post. I can't find where the "/downloads" is actually being called to be mounted. 

Quote

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='' -e 'VPN_PASS'='' -e 'VPN_PROV'='custom' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.50.0/24' -e 'NAME_SERVERS'='209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4' -e 'DEBUG'='true' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/Downloads/':'/downloads':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 

df007ddf6584b07950b3451faff18bdbb179b51ae680972bff11df5636e661cd

 

deluge.png

 

Also, I have tried using /data/incomplete, /data/complete, with the same Permission denied issue.

Edited by BennyD

Share this post


Link to post
3 minutes ago, BennyD said:

Also, I have tried using /data/incomplete, /data/complete, with the same Permission denied issue.

Where it says "Download to:" needs to be set to /downloads if you docker run command is current.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now