[Support] binhex - DelugeVPN


Recommended Posts

1 hour ago, 7hr08ik said:

Hey guys,

 

Sorry for the late reply. Life!!

 

Well, been trying to give the server a bit of TLC.

- Cache drive, re-run through Preclear, with full erase

- Cache drive re-formatted

- Checked 'Fix Common Problems'

- Rebuilt Docker.img

- Re-downloaded the docker image.

- Checked log, noticed msg about password containing character that might hinder login. Changed password.

- Noticed msg about running '/sbin/modprobe iptable_mangle' so ran this

- Stopped and started the container

 

Still no luck, there are a few errors in the log files, but im sure ive seen some of these when everything was working just fine. Obviously im no expert, but it seems the container is in a loop. Trying to connect, then reloading

 

I've attached my supervisord.log

supervisord.log 27.82 kB · 1 download

the issue is your isp (vodafone) is hijacking dns, see here from your log:-

 

2019-07-04 18:25:03,594 DEBG 'start-script' stdout output:
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 30167
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; de-frankfurt.privateinternetaccess.com.	IN	A

;; ANSWER SECTION:
de-frankfurt.privateinternetaccess.com.	300	IN	A	90.255.255.14

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 17 msec
;; SERVER: 37.235.1.174
;; WHEN: Thu Jul  4 18:25:03 2019
;; MSG SIZE  rcvd: 72

de-frankfurt.privateinternetaccess.com does NOT resolve to that ip address, so you need to somehow turn off dns redirection, or whatever they are calling it from your isp's end.

 

whois lookup for proof:-

 

The IPWHOIS Lookup tool finds contact information for the owner of a specified IP address.

Enter a host name or an IP address:
90.255.255.14
  Go »
Related Tools: DNS Traversal Traceroute Vector Trace Ping WHOIS Lookup
Source: whois.ripe.netIP Address: 90.255.255.14
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '90.255.255.0 - 90.255.255.255'

% Abuse contact for '90.255.255.0 - 90.255.255.255' is '[email protected]'

inetnum:        90.255.255.0 - 90.255.255.255
netname:        VODAFONE-IP
descr:          P11 Anycast Service
country:        GB
admin-c:        BC419-RIPE
tech-c:         BC419-RIPE
remarks:        INFRA-AW
status:         ASSIGNED PA
mnt-by:         CW-EUROPE-GSOC
created:        2017-04-12T14:09:04Z
last-modified:  2017-04-12T14:09:04Z
source:         RIPE

 

Link to comment

Hello,

 

Please forgive my brevity, this message come from a happy place...

 

OMFG I LOVE YOU!!!! I didnt even realise my router had reset. God damn mothaf/*-!"$£&*%$" ISPs. Router had reset to auto DNS.

Set to cloudfare and works again! WOOOHOOOO!!!

 

As an aside....Cloudfare DNS? OpenDNS? Now to figure out whos the best choice, as it seems vodafone are redirecting my traffic.

 

Thank you oh great and powerful Lord Binhex.

May many pleasures fall upon you

Link to comment

Hello, May someone help me whenever I install deluge any of its containers it says not connected 

 

https://gyazo.com/7b58cd076101e29d6803b26c3a450417 - Deluge

https://gyazo.com/33eba307df5923779f3d7150e239a31c - Docker Config

https://gyazo.com/96a480362bfd95e3ec14eaef42094ba5 - Docker Config

 

This is the log

 

Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2019-07-04 12:26:27.167116 [info] System information Linux ab6ad1c6c53e 4.19.41-Unraid #1 SMP Wed May 8 14:23:25 PDT 2019 x86_64 GNU/Linux
2019-07-04 12:26:27.218783 [info] PUID defined as '99'
2019-07-04 12:26:27.273294 [info] PGID defined as '100'
2019-07-04 12:26:27.787395 [info] UMASK defined as '000'
2019-07-04 12:26:27.837368 [info] Permissions already set for volume mappings
2019-07-04 12:26:27.893188 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2019-07-04 12:26:27.943661 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2019-07-04 12:26:27.994683 [info] VPN_ENABLED defined as 'yes'
2019-07-04 12:26:28.061207 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/lv19.nordvpn.com.udp1194.ovpn
dos2unix: converting file /config/openvpn/lv19.nordvpn.com.udp1194.ovpn to Unix format...
2019-07-04 12:26:28.149489 [info] VPN remote line defined as 'remote 80.246.31.12 1194'
2019-07-04 12:26:28.200445 [info] VPN_REMOTE defined as '80.246.31.12'
2019-07-04 12:26:28.250795 [info] VPN_PORT defined as '1194'
2019-07-04 12:26:28.309809 [info] VPN_PROTOCOL defined as 'udp'
2019-07-04 12:26:28.362587 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-07-04 12:26:28.413789 [info] VPN_PROV defined as 'custom'
2019-07-04 12:26:28.464255 [info] LAN_NETWORK defined as '192.168.1.0/24'
2019-07-04 12:26:28.515191 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1'
2019-07-04 12:26:28.668598 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-07-04 12:26:28.718553 [info] ENABLE_PRIVOXY defined as 'yes'
2019-07-04 12:26:28.787068 [info] Starting Supervisor...
2019-07-04 12:26:31,430 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2019-07-04 12:26:31,430 INFO Set uid to user 0 succeeded
2019-07-04 12:26:31,437 INFO supervisord started with pid 6
2019-07-04 12:26:32,440 INFO spawned: 'privoxy-script' with pid 143
2019-07-04 12:26:32,442 INFO spawned: 'start-script' with pid 144
2019-07-04 12:26:32,445 INFO spawned: 'watchdog-script' with pid 145
2019-07-04 12:26:32,445 INFO reaped unknown pid 7
2019-07-04 12:26:32,456 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2019-07-04 12:26:32,457 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-07-04 12:26:32,458 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-07-04 12:26:32,458 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-07-04 12:26:32,459 DEBG 'watchdog-script' stdout output:
[info] Deluge-web config file doesn't exist, copying default...

2019-07-04 12:26:32,476 DEBG 'start-script' stdout output:
[warn] Username contains characters which could cause authentication issues, please consider changing this if possible

2019-07-04 12:26:32,477 DEBG 'watchdog-script' stdout output:
[info] Deluge config file doesn't exist, copying default...

2019-07-04 12:26:32,489 DEBG 'watchdog-script' stderr output:
dos2unix: converting file /config/core.conf to Unix format...

2019-07-04 12:26:32,722 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2019-07-04 12:26:32,728 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2019-07-04 12:26:32,732 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2019-07-04 12:26:32,737 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2019-07-04 12:26:32,742 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2019-07-04 12:26:32,747 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2019-07-04 12:26:32,752 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2019-07-04 12:26:32,757 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2019-07-04 12:26:32,762 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2019-07-04 12:26:32,766 DEBG 'start-script' stdout output:
80.246.31.12

2019-07-04 12:26:32,781 DEBG 'start-script' stdout output:
[info] Attempting to load tun kernel module...

2019-07-04 12:26:32,783 DEBG 'start-script' stderr output:
modprobe: FATAL: Module tun not found in directory /lib/modules/4.19.41-Unraid

2019-07-04 12:26:32,783 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module using modprobe, trying insmod...

2019-07-04 12:26:32,785 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory

2019-07-04 12:26:32,786 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module, assuming its dynamically loaded

2019-07-04 12:26:32,792 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2019-07-04 12:26:32,794 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.19.41-Unraid

2019-07-04 12:26:32,794 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2019-07-04 12:26:32,795 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2019-07-04 12:26:32,796 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'

2019-07-04 12:26:32,839 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2019-07-04 12:26:32,844 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2019-07-04 12:26:32,846 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-07-04 12:26:32,847 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.5
192.168.1.0/24 via 172.17.0.1 dev eth0

2019-07-04 12:26:32,848 DEBG 'start-script' stdout output:
--------------------

2019-07-04 12:26:33,032 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-07-04 12:26:33,034 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-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 udp -m udp --sport 1194 -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.1.0/24 -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 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1194 -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.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 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2019-07-04 12:26:33,035 DEBG 'start-script' stdout output:
--------------------

2019-07-04 12:26:33,035 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2019-07-04 12:26:33,317 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:33 2019 WARNING: file 'credentials.conf' is group or others accessible
Thu Jul 4 12:26:33 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019
Thu Jul 4 12:26:33 2019 library versions: OpenSSL 1.1.1c 28 May 2019, LZO 2.10

2019-07-04 12:26:33,319 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:33 2019 WARNING: --ping should normally be used with --ping-restart or --ping-exit
Thu Jul 4 12:26:33 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-07-04 12:26:33,319 DEBG 'start-script' stdout output:
[info] OpenVPN started
Thu Jul 4 12:26:33 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Thu Jul 4 12:26:33 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Thu Jul 4 12:26:33 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]80.246.31.12:1194
Thu Jul 4 12:26:33 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Thu Jul 4 12:26:33 2019 UDP link local: (not bound)
Thu Jul 4 12:26:33 2019 UDP link remote: [AF_INET]80.246.31.12:1194

2019-07-04 12:26:33,344 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:33 2019 TLS: Initial packet from [AF_INET]80.246.31.12:1194, sid=cc1d37b0 7c617f3d

2019-07-04 12:26:38,022 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:38 2019 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA

2019-07-04 12:26:38,023 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:38 2019 VERIFY OK: depth=1, C=PA, O=NordVPN, CN=NordVPN CA3

2019-07-04 12:26:38,024 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:38 2019 VERIFY KU OK
Thu Jul 4 12:26:38 2019 Validating certificate extended key usage
Thu Jul 4 12:26:38 2019 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Thu Jul 4 12:26:38 2019 VERIFY EKU OK
Thu Jul 4 12:26:38 2019 VERIFY OK: depth=0, CN=lv19.nordvpn.com

2019-07-04 12:26:38,243 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:38 2019 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu Jul 4 12:26:38 2019 [lv19.nordvpn.com] Peer Connection Initiated with [AF_INET]80.246.31.12:1194

2019-07-04 12:26:39,498 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:39 2019 SENT CONTROL [lv19.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2019-07-04 12:26:42,044 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:42 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.8.8.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.8.8.2 255.255.255.0,peer-id 0,cipher AES-256-GCM'

2019-07-04 12:26:42,045 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:42 2019 OPTIONS IMPORT: timers and/or timeouts modified
Thu Jul 4 12:26:42 2019 OPTIONS IMPORT: explicit notify parm(s) modified
Thu Jul 4 12:26:42 2019 OPTIONS IMPORT: compression parms modified
Thu Jul 4 12:26:42 2019 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
Thu Jul 4 12:26:42 2019 Socket Buffers: R=[212992->1048576] S=[212992->1048576]
Thu Jul 4 12:26:42 2019 OPTIONS IMPORT: --ifconfig/up options modified
Thu Jul 4 12:26:42 2019 OPTIONS IMPORT: route options modified
Thu Jul 4 12:26:42 2019 OPTIONS IMPORT: route-related options modified
Thu Jul 4 12:26:42 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Thu Jul 4 12:26:42 2019 OPTIONS IMPORT: peer-id set
Thu Jul 4 12:26:42 2019 OPTIONS IMPORT: adjusting link_mtu to 1657
Thu Jul 4 12:26:42 2019 OPTIONS IMPORT: data channel crypto options modified
Thu Jul 4 12:26:42 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu Jul 4 12:26:42 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu Jul 4 12:26:42 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu Jul 4 12:26:42 2019 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:05

2019-07-04 12:26:46,609 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:46 2019 TUN/TAP device tun0 opened
Thu Jul 4 12:26:46 2019 TUN/TAP TX queue length set to 100
Thu Jul 4 12:26:46 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-07-04 12:26:46,611 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:46 2019 /usr/bin/ip addr add dev tun0 10.8.8.2/24 broadcast 10.8.8.255

2019-07-04 12:26:46,613 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:46 2019 /root/openvpnup.sh tun0 1500 1585 10.8.8.2 255.255.255.0 init

2019-07-04 12:26:46,616 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:46 2019 /usr/bin/ip route add 80.246.31.12/32 via 172.17.0.1

2019-07-04 12:26:46,618 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:46 2019 /usr/bin/ip route add 0.0.0.0/1 via 10.8.8.1

2019-07-04 12:26:46,620 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:46 2019 /usr/bin/ip route add 128.0.0.0/1 via 10.8.8.1

2019-07-04 12:26:46,623 DEBG 'start-script' stdout output:
Thu Jul 4 12:26:46 2019 Initialization Sequence Completed

2019-07-04 12:26:46,659 DEBG 'privoxy-script' stdout output:
[info] Configuring Privoxy...

2019-07-04 12:26:46,707 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.8.8.2 different, marking for reconfigure

2019-07-04 12:26:46,713 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2019-07-04 12:26:46,719 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-07-04 12:26:46,776 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22784598123296 for <Subprocess at 22784598123800 with name privoxy-script in state RUNNING> (stdout)>
2019-07-04 12:26:46,776 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22784597560176 for <Subprocess at 22784598123800 with name privoxy-script in state RUNNING> (stderr)>
2019-07-04 12:26:46,777 INFO exited: privoxy-script (exit status 0; expected)
2019-07-04 12:26:46,777 DEBG received SIGCHLD indicating a child quit
2019-07-04 12:26:52,076 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 80.246.31.13

2019-07-04 12:26:52,098 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2019-07-04 12:26:54,007 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has an undefined value
[info] Deluge key 'listen_interface' will have a new value '10.8.8.2'
[info] Writing changes to Deluge config file '/config/core.conf'...

2019-07-04 12:26:56,400 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has an undefined value
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2019-07-04 12:26:57,291 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2019-07-04 12:26:58,083 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2019-07-04 12:27:04,164 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-07-04 12:27:04,164 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started

2019-07-04 12:27:34,339 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2019-07-04 12:27:34,513 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2019-07-04 12:27:35,553 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2019-07-04 12:27:35,564 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118
 

Edited by Guest
Link to comment
25 minutes ago, 7hr08ik said:

Hello,

 

Please forgive my brevity, this message come from a happy place...

 

OMFG I LOVE YOU!!!! I didnt even realise my router had reset. God damn mothaf/*-!"$£&*%$" ISPs. Router had reset to auto DNS.

Set to cloudfare and works again! WOOOHOOOO!!!

 

As an aside....Cloudfare DNS? OpenDNS? Now to figure out whos the best choice, as it seems vodafone are redirecting my traffic.

 

Thank you oh great and powerful Lord Binhex.

May many pleasures fall upon you

lol nice to be appreciated :-), for a list of good name servers (as in ones that dont log) see the github repo for this container in OP, there is a list at the bottom of the readme.md.

Link to comment
19 minutes ago, 7hr08ik said:

DUDE TAKE THIS DOWN NOW!!!

 

Your password is in there

 

 

16 minutes ago, Pducharme said:

Yes, and change your nordvpn password now!

Thanks

Link to comment

EDIT: Nevermind, I had forgotten about the LAN_NETWORK variable of the docker... whoops!

 

So I downgraded from the latest version to get back on 1.3.15 (binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04), and while the Web UI works fine, I'm now totally unable to connect remotely using deluge thinclient.

 

Both the server and the thinclient have the same deluge version (1.3.15)

"Allow remote connections" is checked, daemon port is default (58846)

Firewall exceptions are set for deluge

I triple checked the username and password in the auth file.

 

Still getting a red light on the thinclient connection manager. Any ideas?

Edited by dasz
Link to comment
Quote

Ok I got the tagged "Dev" working with latest deluge/flexget.  Thanks to Binhex and his fine work, I copied and pasted the changes from Summer 2018.

 

For some reason the deluge-client didn't get installed and that stops it from working.  A manual install fixes that.

 

deluge-client >=1.5 is required. `pip install deluge-client` to install.

 

 

Dockerhub Repository paulpoco/arch-delugevpn-dev:Dev

 

]# flexget -V
2.21.10

 

]# deluge --version
deluge 2.0.3
libtorrent: 1.1.12.0
Python: 3.7.3
OS: Linux Arch Linux

@Binhex deluge-client, what is that?   My Flexget complained deluge-client wasn't installed and to use `pip install deluge-client` to install.  I did put that in my github files but I guess it was at the wrong place.  Is deluge-client also available with pacman?

 

Edit: https://aur.archlinux.org/packages/python-deluge-client/

Which also needs python-setuptools.

If I add these 2 with Pacman during the build, will I be able to do a pip upgrade to get new versions?

Edited by Paul_Ber
Answered my own question maybe.
Link to comment

Hi guys, I'm getting this error and Deluge is not starting! Any ideas?

 

2019-07-10 09:03:51,082 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2019-07-10 09:03:51,303 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2019-07-10 09:03:53,323 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-07-10 09:03:55,112 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:


2019-07-10 09:03:55,115 DEBG 'watchdog-script' stderr output:

Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/twisted/internet/base.py", line 1272, in run
self.mainLoop()
File "/usr/lib/python3.7/site-packages/twisted/internet/base.py", line 1281, in mainLoop
self.runUntilCurrent()
File "/usr/lib/python3.7/site-packages/twisted/internet/base.py", line 902, in runUntilCurrent
call.func(*call.args, **call.kw)
File "/usr/lib/python3.7/site-packages/twisted/internet/task.py", line 239, in __call__
d = defer.maybeDeferred(self.f, *self.a, **self.kw)
--- <exception caught here> ---
File "/usr/lib/python3.7/site-packages/twisted/internet/defer.py", line 151, in maybeDeferred
result = f(*args, **kw)
File "/usr/lib/python3.7/site-packages/deluge/core/alertmanager.py", line 70, in update
self.handle_alerts()
File "/usr/lib/python3.7/site-packages/deluge/core/alertmanager.py", line 140, in handle_alerts
for attr in dir(alert)
File "/usr/lib/python3.7/site-packages/deluge/core/alertmanager.py", line 141, in <dictcomp>
if not attr.startswith('__')
builtins.UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe3 in position 11: invalid continuation byte

 

Link to comment
2 minutes ago, InVisibleGoD said:

Hi guys, I'm getting this error and Deluge is not starting! Any ideas?

 


2019-07-10 09:03:51,082 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2019-07-10 09:03:51,303 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2019-07-10 09:03:53,323 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-07-10 09:03:55,112 DEBG 'watchdog-script' stderr output:
Unhandled error in Deferred:


2019-07-10 09:03:55,115 DEBG 'watchdog-script' stderr output:

Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/twisted/internet/base.py", line 1272, in run
self.mainLoop()
File "/usr/lib/python3.7/site-packages/twisted/internet/base.py", line 1281, in mainLoop
self.runUntilCurrent()
File "/usr/lib/python3.7/site-packages/twisted/internet/base.py", line 902, in runUntilCurrent
call.func(*call.args, **call.kw)
File "/usr/lib/python3.7/site-packages/twisted/internet/task.py", line 239, in __call__
d = defer.maybeDeferred(self.f, *self.a, **self.kw)
--- <exception caught here> ---
File "/usr/lib/python3.7/site-packages/twisted/internet/defer.py", line 151, in maybeDeferred
result = f(*args, **kw)
File "/usr/lib/python3.7/site-packages/deluge/core/alertmanager.py", line 70, in update
self.handle_alerts()
File "/usr/lib/python3.7/site-packages/deluge/core/alertmanager.py", line 140, in handle_alerts
for attr in dir(alert)
File "/usr/lib/python3.7/site-packages/deluge/core/alertmanager.py", line 141, in <dictcomp>
if not attr.startswith('__')
builtins.UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe3 in position 11: invalid continuation byte

 

its a deluge v2 bug, see here:-

 

its been fixed but there hasnt been a new release yet.

  • Like 1
Link to comment
On 7/9/2019 at 12:54 AM, Paul_Ber said:

@Binhex deluge-client, what is that? 

https://dev.deluge-torrent.org/wiki/UserGuide/ThinClient

 

On 7/9/2019 at 12:54 AM, Paul_Ber said:

If I add these 2 with Pacman during the build, will I be able to do a pip upgrade to get new versions?

i dont think you can mix and match like that, pip will only upgrade python modules installed by pip, so no i dont think you can do that.

 

edit - quick check on pypi reveals you can just simply install python-pip and then pip install deluge-client, that is your cleanest approach:-

https://pypi.org/project/deluge-client/

Edited by binhex
  • Like 1
Link to comment

Hi binhex !

 

First I'd like to thank you for your awesome container. Seriously, I've been using it for almost 2 years and it never failed me !

 

I'd like to ask you if it is possible to add a second "lan" network in the iptables via the environment variables or something.

When I'm home I don't have any issues connecting to deluge web or the gui.

 

To connect remotely when I'm not home, I have a VPN set up on a my NAS but the ip it gives to my client is not in the range of my "normal lan" and I have no way to change that. So of course I'm unable to access deluge.

 

Do you have any idea on how I could alter the setup to make It work ?

Ideally I'd like to add the ip range of my local vpn to the container but I don't think I can add 2 "lan" networks with the env. vars.

 

Thank you again, for the container and for your time !

Link to comment
6 minutes ago, Fl4shBack said:

Hi binhex !

 

First I'd like to thank you for your awesome container. Seriously, I've been using it for almost 2 years and it never failed me !

 

I'd like to ask you if it is possible to add a second "lan" network in the iptables via the environment variables or something.

When I'm home I don't have any issues connecting to deluge web or the gui.

 

To connect remotely when I'm not home, I have a VPN set up on a my NAS but the ip it gives to my client is not in the range of my "normal lan" and I have no way to change that. So of course I'm unable to access deluge.

 

Do you have any idea on how I could alter the setup to make It work ?

Ideally I'd like to add the ip range of my local vpn to the container but I don't think I can add 2 "lan" networks with the env. vars.

 

Thank you again, for the container and for your time !

simple enough, just add your additional network to the LAN_NETWORK env var using a comma to separate them, e.g.:-

LAN_NETWORK=192.168.1.0/24,10.1.1.0/24

Link to comment

I'm not using Black Hole but, since the deluge interface from CouchPotato no longer works with deluge v2, I have set CP to use the BH method of sending magnet/torrent files to deluge V2.

Simply configure the 'AutoAdd' plugin in deluge to find the magnet/torrent files.

Link to comment

I must begin and end with IMMENSE appreciation for Binhex for creating all these setups for us to use, and the authors of these software that are incredibly useful.   THANK YOU, THANK YOU

 

Deluge V2 seems to be a huge improvement, but I have found this to be a brutal breaking change given that there are no compatible clients for Windows or OS X.  While I use other utilities like sonarr and radarr to initiate deluge downloading, I also use a Deluge client on my Mac.  Furthermore,  I'm afraid to downgrade, given the reports of losing older seeding torrents.

How do maintainers (such as Binhex) choose when to upgrade underlying components and when to create a new version?  Please feel free to point me at relevant discussion, I'm haven't found anything about this despite my searching.

Please accept this post as feedback that, as a user, I would have preferred to wait for a Deluge V2 upgrade after a OS X client was available.
 

That said, I must begin and end with IMMENSE appreciation for Binhex for creating all these setups for us to use, and the authors of these software that are incredibly useful.   THANK YOU, THANK YOU

Link to comment

I'm not sure which docker is having this issue. But what is going on is that i'm telling radarr or sonarr to search for a show/movie and it finds it and sends it over to delugevpn no problem. When it is finished it put it back to the bottom of the queue at 100% with no number indicated on the order it is in. For the TV shows it is going to /mnt/user/media/Tv_Shows/ but it is still in the completed folder I have as well. But for the movies it does not go to  /mnt/user/media/Movies like it is set to do and it just stays in the completed folder. I've tried looking for any invalid characters or non English letters. I've re watched the setup videos spaceinvaderone did on each docker again to make sure it is setup correctly.

Link to comment
2 hours ago, knipster said:

I must begin and end with IMMENSE appreciation for Binhex for creating all these setups for us to use, and the authors of these software that are incredibly useful.   THANK YOU, THANK YOU

 

Deluge V2 seems to be a huge improvement, but I have found this to be a brutal breaking change given that there are no compatible clients for Windows or OS X.  While I use other utilities like sonarr and radarr to initiate deluge downloading, I also use a Deluge client on my Mac.  Furthermore,  I'm afraid to downgrade, given the reports of losing older seeding torrents.

How do maintainers (such as Binhex) choose when to upgrade underlying components and when to create a new version?  Please feel free to point me at relevant discussion, I'm haven't found anything about this despite my searching.

Please accept this post as feedback that, as a user, I would have preferred to wait for a Deluge V2 upgrade after a OS X client was available.
 

That said, I must begin and end with IMMENSE appreciation for Binhex for creating all these setups for us to use, and the authors of these software that are incredibly useful.   THANK YOU, THANK YOU

Typically dockers will update to the most recent version of the app automatically. There isn't really any decision making involved. I'm sure @binhex can provide more specifics for this particular docker.

 

You can downgrade back to deluge 1.3 using tags. Start reading here and scroll through the next several posts you'll see what version number to use in the tag. I also had to restore from backup after downgrading to get my torrents back.

Link to comment
3 hours ago, knipster said:

How do maintainers (such as Binhex) choose when to upgrade underlying components and when to create a new version?

Plex is the best example for this.

 

LSIO:  Everytime the app is restarted, it will update to the latest release from Plex Inc. (automatic)

Binhex: Whenever the update get pushed upstream to whatever repository he uses, an update to the container will be released. (automatic)

LT: Whenever the maintainer deems that the update is safe / stable / people are complaining will update the container and release an update. (manual)

 

If you take plex out of the equation, then LSIO changes to be every Friday an update is released. 

 

Pros and cons to each of the above scenarios.

 

Edited by Squid
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.