[Support] binhex - DelugeVPN


8725 posts in this topic Last Reply

Recommended Posts

ok.  set DNS on router and the docker to just use google dns (8.8.8.8,8.8.4.4).  Same outcome.  Put static IP for the PIA server in the .ovpn file, but the log gives the port forwarding error (tried both vancouver and montreal, which are listed as supporting port forwarding), but webui comes up.  Preliminary research shows I'd probably need a router to support DNSmasq to get past comcast highjacking the dns request.  Are you aware of an alternative?  Thank you for the help!

 

log:

2019-09-01 11:30:14.654683 [info] System information Linux cf77fb93c64e 4.19.55-Unraid #1 SMP Sat Jun 22 08:31:17 PDT 2019 x86_64 GNU/Linux
2019-09-01 11:30:14.692729 [info] PUID defined as '99'
2019-09-01 11:30:14.733555 [info] PGID defined as '100'
2019-09-01 11:30:15.495578 [info] UMASK defined as '000'
2019-09-01 11:30:15.532925 [info] Permissions already set for volume mappings
2019-09-01 11:30:15.574379 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info'
2019-09-01 11:30:15.612728 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info'
2019-09-01 11:30:15.650402 [info] VPN_ENABLED defined as 'yes'
2019-09-01 11:30:15.694916 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CA Montreal.ovpn
dos2unix: converting file /config/openvpn/CA Montreal.ovpn to Unix format...
2019-09-01 11:30:15.749879 [info] VPN remote line defined as 'remote 199.229.249.140 1198'
2019-09-01 11:30:15.787831 [info] VPN_REMOTE defined as '199.229.249.140'
2019-09-01 11:30:15.833901 [info] VPN_PORT defined as '1198'
2019-09-01 11:30:15.875820 [info] VPN_PROTOCOL defined as 'udp'
2019-09-01 11:30:15.915620 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-09-01 11:30:15.953417 [info] VPN_PROV defined as 'pia'
2019-09-01 11:30:15.993647 [info] LAN_NETWORK defined as '192.168.0.0/24'
2019-09-01 11:30:16.034373 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
2019-09-01 11:30:16.072236 [info] VPN_USER defined as 'user'
2019-09-01 11:30:16.110315 [info] VPN_PASS defined as 'password'
2019-09-01 11:30:16.148060 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-09-01 11:30:16.185550 [info] STRICT_PORT_FORWARD defined as 'yes'
2019-09-01 11:30:16.226503 [info] ENABLE_PRIVOXY defined as 'no'
2019-09-01 11:30:16.271766 [info] Starting Supervisor...
2019-09-01 11:30:16,537 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2019-09-01 11:30:16,538 INFO Set uid to user 0 succeeded
2019-09-01 11:30:16,541 INFO supervisord started with pid 6
2019-09-01 11:30:16.034373 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
2019-09-01 11:30:16.072236 [info] VPN_USER defined as 'user'
2019-09-01 11:30:16.110315 [info] VPN_PASS defined as 'password'
2019-09-01 11:30:16.148060 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-09-01 11:30:16.185550 [info] STRICT_PORT_FORWARD defined as 'yes'
2019-09-01 11:30:16.226503 [info] ENABLE_PRIVOXY defined as 'no'
2019-09-01 11:30:16.271766 [info] Starting Supervisor...
2019-09-01 11:30:16,537 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2019-09-01 11:30:16,538 INFO Set uid to user 0 succeeded
2019-09-01 11:30:16,541 INFO supervisord started with pid 6
2019-09-01 11:30:17,544 INFO spawned: 'start-script' with pid 149
2019-09-01 11:30:17,546 INFO spawned: 'watchdog-script' with pid 150
2019-09-01 11:30:17,546 INFO reaped unknown pid 7
2019-09-01 11:30:17,553 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2019-09-01 11:30:17,554 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-09-01 11:30:17,554 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-09-01 11:30:17,557 DEBG 'watchdog-script' stderr output:
dos2unix:
2019-09-01 11:30:17,557 DEBG 'watchdog-script' stderr output:
converting file /config/core.conf to Unix format...

2019-09-01 11:30:17,668 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2019-09-01 11:30:17,672 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2019-09-01 11:30:17,676 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2019-09-01 11:30:17,680 DEBG 'start-script' stdout output:
199.229.249.140

2019-09-01 11:30:17,712 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2019-09-01 11:30:17,716 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.0/24 as route via docker eth0

2019-09-01 11:30:17,718 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-09-01 11:30:17,720 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.4
192.168.0.0/24 via 172.17.0.1 dev eth0

2019-09-01 11:30:17,720 DEBG 'start-script' stdout output:
--------------------

2019-09-01 11:30:17,723 DEBG 'start-script' stdout output:
iptable_mangle 16384 2
ip_tables 24576 5 iptable_filter,iptable_nat,iptable_mangle

2019-09-01 11:30:17,724 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2019-09-01 11:30:17,763 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-09-01 11:30:17,765 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 -i eth0 -p udp -m udp --sport 1198 -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.0.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -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 1198 -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.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -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-09-01 11:30:17,767 DEBG 'start-script' stdout output:
--------------------

2019-09-01 11:30:17,767 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2019-09-01 11:30:17,783 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:17 2019 WARNING: file 'credentials.conf' is group or others accessible
Sun Sep 1 11:30:17 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
Sun Sep 1 11:30:17 2019 library versions: OpenSSL 1.1.1c 28 May 2019, LZO 2.10

2019-09-01 11:30:17,784 DEBG 'start-script' stdout output:
[info] OpenVPN started
Sun Sep 1 11:30:17 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-09-01 11:30:17,785 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:17 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]199.229.249.140:1198

2019-09-01 11:30:17,785 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:17 2019 UDP link local: (not bound)
Sun Sep 1 11:30:17 2019 UDP link remote: [AF_INET]199.229.249.140:1198

2019-09-01 11:30:18,217 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:18 2019 [8afa1118096e2faab887e67d29332f3d] Peer Connection Initiated with [AF_INET]199.229.249.140:1198

2019-09-01 11:30:19,337 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 TUN/TAP device tun0 opened
Sun Sep 1 11:30:19 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-09-01 11:30:19,339 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 /usr/bin/ip addr add dev tun0 local 10.80.10.6 peer 10.80.10.5

2019-09-01 11:30:19,340 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 /root/openvpnup.sh tun0 1500 1558 10.80.10.6 10.80.10.5 init

2019-09-01 11:30:19,350 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 Initialization Sequence Completed

2019-09-01 11:30:19,477 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint '199.229.249.140' is port forward enabled...

2019-09-01 11:30:19,337 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 TUN/TAP device tun0 opened
Sun Sep 1 11:30:19 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-09-01 11:30:19,339 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 /usr/bin/ip addr add dev tun0 local 10.80.10.6 peer 10.80.10.5

2019-09-01 11:30:19,340 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 /root/openvpnup.sh tun0 1500 1558 10.80.10.6 10.80.10.5 init

2019-09-01 11:30:19,350 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 Initialization Sequence Completed

2019-09-01 11:30:19,477 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint '199.229.249.140' is port forward enabled...

2019-09-01 11:30:19,504 DEBG 'start-script' stdout output:
[info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82...

2019-09-01 11:30:20,554 DEBG 'start-script' stdout output:
[info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200

2019-09-01 11:30:20,886 DEBG 'start-script' stdout output:
[warn] PIA endpoint '199.229.249.140' is not in the list of endpoints that support port forwarding, DL/UL speeds maybe slow
[info] Please consider switching to one of the endpoints shown below

2019-09-01 11:30:20,886 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-

2019-09-01 11:30:20,887 DEBG 'start-script' stdout output:
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] sweden.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2019-09-01 11:30:20,913 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=c642926ef6183f16b694d25bc3e503a9fa7839683e96436051193b2ad578f892...

2019-09-01 11:30:21,574 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=c642926ef6183f16b694d25bc3e503a9fa7839683e96436051193b2ad578f892, response code 200

2019-09-01 11:30:21,615 DEBG 'start-script' stdout output:
[info] Successfully assigned incoming port 44987

2019-09-01 11:30:21,617 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2019-09-01 11:30:21,802 DEBG 'start-script' stdout output:
[info] DNS operational, we can resolve name 'www.google.com' to address '172.217.165.4'

2019-09-01 11:30:21,806 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2019-09-01 11:30:22,219 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 199.229.249.140

2019-09-01 11:30:22,501 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.80.10.6 different, marking for reconfigure

2019-09-01 11:30:22,505 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2019-09-01 11:30:22,509 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-09-01 11:30:22,509 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 44987 different, marking for reconfigure

2019-09-01 11:30:22,510 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2019-09-01 11:30:24,355 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.1.11.10'
[info] Deluge key 'listen_interface' will have a new value '10.80.10.6'
[info] Writing changes to Deluge config file '/config/core.conf'...

2019-09-01 11:30:24,660 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2019-09-01 11:30:24,934 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'a1b91b5489ec17c4d147c3063509a7a8cfa43cfd'
[info] Deluge key 'default_daemon' will have a new value 'a1b91b5489ec17c4d147c3063509a7a8cfa43cfd'
[info] Writing changes to Deluge config file '/config/web.conf'...

2019-09-01 11:30:25,772 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2019-09-01 11:30:26,252 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2019-09-01 11:30:32,210 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-09-01 11:30:32,210 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-09-01 11:30:39,973 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (44987, 44987)
Configuration value successfully updated.

2019-09-01 11:30:45,834 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-09-01 11:30:45,834 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-09-01 11:30:45,834 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

 

 

 

Link to post
  • Replies 8.7k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

OK guys, multi remote endpoint support is now in for this image please pull down the new image (this change will be rolled out to all my vpn images shortly).   What this means is that the im

There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A n

I wanted to summarize how I got Mullvad working with DelugeVPN as I had to piece together several "solutions" from different comments in this thread and there was some incorrect info; likely old.

Posted Images

8 minutes ago, ispoonfite said:

ok.  set DNS on router and the docker to just use google dns (8.8.8.8,8.8.4.4).  Same outcome.  Put static IP for the PIA server in the .ovpn file, but the log gives the port forwarding error (tried both vancouver and montreal, which are listed as supporting port forwarding), but webui comes up.  Preliminary research shows I'd probably need a router to support DNSmasq to get past comcast highjacking the dns request.  Are you aware of an alternative?  Thank you for the help!

 

log:

2019-09-01 11:30:14.654683 [info] System information Linux cf77fb93c64e 4.19.55-Unraid #1 SMP Sat Jun 22 08:31:17 PDT 2019 x86_64 GNU/Linux
2019-09-01 11:30:14.692729 [info] PUID defined as '99'
2019-09-01 11:30:14.733555 [info] PGID defined as '100'
2019-09-01 11:30:15.495578 [info] UMASK defined as '000'
2019-09-01 11:30:15.532925 [info] Permissions already set for volume mappings
2019-09-01 11:30:15.574379 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info'
2019-09-01 11:30:15.612728 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info'
2019-09-01 11:30:15.650402 [info] VPN_ENABLED defined as 'yes'
2019-09-01 11:30:15.694916 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CA Montreal.ovpn
dos2unix: converting file /config/openvpn/CA Montreal.ovpn to Unix format...
2019-09-01 11:30:15.749879 [info] VPN remote line defined as 'remote 199.229.249.140 1198'
2019-09-01 11:30:15.787831 [info] VPN_REMOTE defined as '199.229.249.140'
2019-09-01 11:30:15.833901 [info] VPN_PORT defined as '1198'
2019-09-01 11:30:15.875820 [info] VPN_PROTOCOL defined as 'udp'
2019-09-01 11:30:15.915620 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-09-01 11:30:15.953417 [info] VPN_PROV defined as 'pia'
2019-09-01 11:30:15.993647 [info] LAN_NETWORK defined as '192.168.0.0/24'
2019-09-01 11:30:16.034373 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
2019-09-01 11:30:16.072236 [info] VPN_USER defined as 'user'
2019-09-01 11:30:16.110315 [info] VPN_PASS defined as 'password'
2019-09-01 11:30:16.148060 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-09-01 11:30:16.185550 [info] STRICT_PORT_FORWARD defined as 'yes'
2019-09-01 11:30:16.226503 [info] ENABLE_PRIVOXY defined as 'no'
2019-09-01 11:30:16.271766 [info] Starting Supervisor...
2019-09-01 11:30:16,537 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2019-09-01 11:30:16,538 INFO Set uid to user 0 succeeded
2019-09-01 11:30:16,541 INFO supervisord started with pid 6
2019-09-01 11:30:16.034373 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
2019-09-01 11:30:16.072236 [info] VPN_USER defined as 'user'
2019-09-01 11:30:16.110315 [info] VPN_PASS defined as 'password'
2019-09-01 11:30:16.148060 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-09-01 11:30:16.185550 [info] STRICT_PORT_FORWARD defined as 'yes'
2019-09-01 11:30:16.226503 [info] ENABLE_PRIVOXY defined as 'no'
2019-09-01 11:30:16.271766 [info] Starting Supervisor...
2019-09-01 11:30:16,537 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2019-09-01 11:30:16,538 INFO Set uid to user 0 succeeded
2019-09-01 11:30:16,541 INFO supervisord started with pid 6
2019-09-01 11:30:17,544 INFO spawned: 'start-script' with pid 149
2019-09-01 11:30:17,546 INFO spawned: 'watchdog-script' with pid 150
2019-09-01 11:30:17,546 INFO reaped unknown pid 7
2019-09-01 11:30:17,553 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2019-09-01 11:30:17,554 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-09-01 11:30:17,554 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-09-01 11:30:17,557 DEBG 'watchdog-script' stderr output:
dos2unix:
2019-09-01 11:30:17,557 DEBG 'watchdog-script' stderr output:
converting file /config/core.conf to Unix format...

2019-09-01 11:30:17,668 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2019-09-01 11:30:17,672 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2019-09-01 11:30:17,676 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2019-09-01 11:30:17,680 DEBG 'start-script' stdout output:
199.229.249.140

2019-09-01 11:30:17,712 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2019-09-01 11:30:17,716 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.0/24 as route via docker eth0

2019-09-01 11:30:17,718 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-09-01 11:30:17,720 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.4
192.168.0.0/24 via 172.17.0.1 dev eth0

2019-09-01 11:30:17,720 DEBG 'start-script' stdout output:
--------------------

2019-09-01 11:30:17,723 DEBG 'start-script' stdout output:
iptable_mangle 16384 2
ip_tables 24576 5 iptable_filter,iptable_nat,iptable_mangle

2019-09-01 11:30:17,724 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2019-09-01 11:30:17,763 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-09-01 11:30:17,765 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 -i eth0 -p udp -m udp --sport 1198 -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.0.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -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 1198 -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.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -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-09-01 11:30:17,767 DEBG 'start-script' stdout output:
--------------------

2019-09-01 11:30:17,767 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2019-09-01 11:30:17,783 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:17 2019 WARNING: file 'credentials.conf' is group or others accessible
Sun Sep 1 11:30:17 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
Sun Sep 1 11:30:17 2019 library versions: OpenSSL 1.1.1c 28 May 2019, LZO 2.10

2019-09-01 11:30:17,784 DEBG 'start-script' stdout output:
[info] OpenVPN started
Sun Sep 1 11:30:17 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-09-01 11:30:17,785 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:17 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]199.229.249.140:1198

2019-09-01 11:30:17,785 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:17 2019 UDP link local: (not bound)
Sun Sep 1 11:30:17 2019 UDP link remote: [AF_INET]199.229.249.140:1198

2019-09-01 11:30:18,217 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:18 2019 [8afa1118096e2faab887e67d29332f3d] Peer Connection Initiated with [AF_INET]199.229.249.140:1198

2019-09-01 11:30:19,337 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 TUN/TAP device tun0 opened
Sun Sep 1 11:30:19 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-09-01 11:30:19,339 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 /usr/bin/ip addr add dev tun0 local 10.80.10.6 peer 10.80.10.5

2019-09-01 11:30:19,340 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 /root/openvpnup.sh tun0 1500 1558 10.80.10.6 10.80.10.5 init

2019-09-01 11:30:19,350 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 Initialization Sequence Completed

2019-09-01 11:30:19,477 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint '199.229.249.140' is port forward enabled...

2019-09-01 11:30:19,337 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 TUN/TAP device tun0 opened
Sun Sep 1 11:30:19 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-09-01 11:30:19,339 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 /usr/bin/ip addr add dev tun0 local 10.80.10.6 peer 10.80.10.5

2019-09-01 11:30:19,340 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 /root/openvpnup.sh tun0 1500 1558 10.80.10.6 10.80.10.5 init

2019-09-01 11:30:19,350 DEBG 'start-script' stdout output:
Sun Sep 1 11:30:19 2019 Initialization Sequence Completed

2019-09-01 11:30:19,477 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint '199.229.249.140' is port forward enabled...

2019-09-01 11:30:19,504 DEBG 'start-script' stdout output:
[info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82...

2019-09-01 11:30:20,554 DEBG 'start-script' stdout output:
[info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200

2019-09-01 11:30:20,886 DEBG 'start-script' stdout output:
[warn] PIA endpoint '199.229.249.140' is not in the list of endpoints that support port forwarding, DL/UL speeds maybe slow
[info] Please consider switching to one of the endpoints shown below

2019-09-01 11:30:20,886 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-

2019-09-01 11:30:20,887 DEBG 'start-script' stdout output:
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] sweden.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2019-09-01 11:30:20,913 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=c642926ef6183f16b694d25bc3e503a9fa7839683e96436051193b2ad578f892...

2019-09-01 11:30:21,574 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=c642926ef6183f16b694d25bc3e503a9fa7839683e96436051193b2ad578f892, response code 200

2019-09-01 11:30:21,615 DEBG 'start-script' stdout output:
[info] Successfully assigned incoming port 44987

2019-09-01 11:30:21,617 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2019-09-01 11:30:21,802 DEBG 'start-script' stdout output:
[info] DNS operational, we can resolve name 'www.google.com' to address '172.217.165.4'

2019-09-01 11:30:21,806 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2019-09-01 11:30:22,219 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 199.229.249.140

2019-09-01 11:30:22,501 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.80.10.6 different, marking for reconfigure

2019-09-01 11:30:22,505 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2019-09-01 11:30:22,509 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-09-01 11:30:22,509 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 44987 different, marking for reconfigure

2019-09-01 11:30:22,510 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2019-09-01 11:30:24,355 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.1.11.10'
[info] Deluge key 'listen_interface' will have a new value '10.80.10.6'
[info] Writing changes to Deluge config file '/config/core.conf'...

2019-09-01 11:30:24,660 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2019-09-01 11:30:24,934 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'a1b91b5489ec17c4d147c3063509a7a8cfa43cfd'
[info] Deluge key 'default_daemon' will have a new value 'a1b91b5489ec17c4d147c3063509a7a8cfa43cfd'
[info] Writing changes to Deluge config file '/config/web.conf'...

2019-09-01 11:30:25,772 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2019-09-01 11:30:26,252 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2019-09-01 11:30:32,210 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-09-01 11:30:32,210 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-09-01 11:30:39,973 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (44987, 44987)
Configuration value successfully updated.

2019-09-01 11:30:45,834 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-09-01 11:30:45,834 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-09-01 11:30:45,834 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

 

 

 

Do you have or are you using a 3rd party VP’? The vpn site you are using might not support port forwarding.  That’s what the logs tell me. 

1. You chose pita as your vpn and you are using a site that doesn’t support port forwarding.

 

Link to post

Used the static IP for the ca-montreal site in the .opvn file - I get the same error for 3 sites that PIA lists as supporting port forwarding (vancouver, france, montreal, all using static IP instead).  It is working and DL speeds do not seem effected, thinking it is what it is.

Link to post
Used the static IP for the ca-montreal site in the .opvn file - I get the same error for 3 sites that PIA lists as supporting port forwarding (vancouver, france, montreal, all using static IP instead).  It is working and DL speeds do not seem effected, thinking it is what it is.
It is s warning not an error, the log you posted shows it does get a port assigned, so it all looks good to me.

Sent from my CLT-L09 using Tapatalk

Link to post
On 8/31/2019 at 12:33 PM, Ranzingabon Hagglesmith said:

Hiya Lipora - have you been able to solve the init.sh problem? That's the exact problem I'm having since I tried to update my Deluge by using the "clear" function in the Synology DSM Docker. My setup is entirely crippled without Deluge! 

No nothing yet.  Was hoping to see an update possibly from BinHex but notta...

Link to post

 

On 8/31/2019 at 7:33 PM, Ranzingabon Hagglesmith said:

Hiya Lipora - have you been able to solve the init.sh problem? That's the exact problem I'm having since I tried to update my Deluge by using the "clear" function in the Synology DSM Docker. My setup is entirely crippled without Deluge! 

The issue is with the Synology implementation of Docker (or perhaps use of Ouroboros? see end of this post) , for whatever reason it is not running the correct command on startup leading to the error:-

/bin/bash: /root/init.sh: No such file or directory

This also affected people running the linux application ouroboros (similar to watchtower), i confirmed the docker image is correct and a manual pull and run works on all platforms i could test on (mac, unraid (linux), and ubuntu). 

 

11 hours ago, Lipora said:

No nothing yet.  Was hoping to see an update possibly from BinHex but notta...

so with nothing to fix im afraid there wont be an update, at least not an update to fix this issue as this looks (to me at least) to be a Synology specific issue.

 

see here for the original 'issue' raised on github:-

https://github.com/binhex/arch-delugevpn/issues/124

 

p.s. are you guys by any chance using Ouroboros in a docker container on your Synology appliance?.

Edited by binhex
Link to post
7 hours ago, binhex said:

 

The issue is with the Synology implementation of Docker (or perhaps use of Ouroboros? see end of this post) , for whatever reason it is not running the correct command on startup leading to the error:-


/bin/bash: /root/init.sh: No such file or directory

This also affected people running the linux application ouroboros (similar to watchtower), i confirmed the docker image is correct and a manual pull and run works on all platforms i could test on (mac, unraid (linux), and ubuntu). 

 

so with nothing to fix im afraid there wont be an update, at least not an update to fix this issue as this looks (to me at least) to be a Synology specific issue.

 

see here for the original 'issue' raised on github:-

https://github.com/binhex/arch-delugevpn/issues/124

 

p.s. are you guys by any chance using Ouroboros in a docker container on your Synology appliance?.

 

Thanks for the reply. I'm not using any Ouroboros, so that's not causing the problem on my end. The only active containers I typically have are Sonarr, Jackett, and my beloved DelugeVPN.

 

Hmmm, is there I way I can manually fix this problem I'm experiencing manually? Or just use the correct start command manually? Or maybe revert to an earlier version...

Link to post

I am getting an error on the log file that says:

 

[warn] Cannot determine external IP address, exausted retries setting to tunnel IP 10.8.8.3

Nothing downloads because of it. I am using SurfShark VPN and can confirm it works fine when I download torrents on my phone trough the VPN.

Link to post
10 hours ago, binhex said:

 

The issue is with the Synology implementation of Docker (or perhaps use of Ouroboros? see end of this post) , for whatever reason it is not running the correct command on startup leading to the error:-


/bin/bash: /root/init.sh: No such file or directory

This also affected people running the linux application ouroboros (similar to watchtower), i confirmed the docker image is correct and a manual pull and run works on all platforms i could test on (mac, unraid (linux), and ubuntu). 

 

so with nothing to fix im afraid there wont be an update, at least not an update to fix this issue as this looks (to me at least) to be a Synology specific issue.

 

see here for the original 'issue' raised on github:-

https://github.com/binhex/arch-delugevpn/issues/124

 

p.s. are you guys by any chance using Ouroboros in a docker container on your Synology appliance?.

 

Okay, update:

 

I figured out on my own how to switch  back to an earlier version of DelugeVPN. I was able to get 2.0.3-1-04 running -- but not 1-05 or 1-06, so some change that occurred after 1-04 creates this problem on Synology docker, if that helps anyone.

 

Then I found out that Deluge 2+ hasn't been whitelisted yet in a lot of places so I reverted to 1.3.15_18_ge050905b2-1-04 which is relatively sluggish but functional.

Link to post
14 minutes ago, Kir said:

Hi,

It looks like the latest version of Deluge ignores the proxy settings. I've always had it set up with Socks5 auth to port 1080, and now it just totally ignores it.

 

Is it a known issue?

this has been a known issue for years with deluge, this is THE reason that i created delugevpn :-)

Link to post
3 minutes ago, binhex said:

this has been a known issue for years with deluge, this is THE reason that i created delugevpn 🙂

Well... it kind of worked with the previous release. Now it doesn't even try to connect on 1080...

Link to post
2 minutes ago, Kir said:

Well... it kind of worked with the previous release. Now it doesn't even try to connect on 1080...

can i ask why you want to do this?, you dont need socks proxy if the application is connected to a vpn tunnel.

Link to post
1 minute ago, binhex said:

can i ask why you want to do this?, you dont need socks proxy if the application is connected to a vpn tunnel.

 

My VPN provider does not allow port forwarding, so Socks5 through them is the only option.

Link to post
6 minutes ago, Kir said:

 

My VPN provider does not allow port forwarding, so Socks5 through them is the only option.

so just to check, im assuming you have VPN_ENABLED set to 'no' then, right?

Link to post
1 minute ago, binhex said:

so just to check, im assuming you have VPN_ENABLED set to 'no' then, right?

Correct

2019-09-06 10:58:02.532672 [info] VPN_ENABLED defined as 'no'
2019-09-06 10:58:02.562400 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE

 

Link to post
6 minutes ago, Kir said:

Correct


2019-09-06 10:58:02.532672 [info] VPN_ENABLED defined as 'no'
2019-09-06 10:58:02.562400 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE

 

ok then im afraid for now your only option is to roll back to deluge 1.x, if you want to get it fixed in deluge 2.x then you could also raise an issue with deluge dev.

 

p.s. as i alluded to earlier, socks proxy is NOT a secure method (at least it wasnt for deluge 1.x last time i checked) , if the socks proxy connection drops for whatever reason then deluge will happily switch over to sending traffic over your LAN. i would encourage you to switch VPN provider and go with one that does support port forwarding, such as PIA.

Edited by binhex
Link to post
1 hour ago, binhex said:

ok then im afraid for now your only option is to roll back to deluge 1.x, if you want to get it fixed in deluge 2.x then you could also raise an issue with deluge dev.

 

p.s. as i alluded to earlier, socks proxy is NOT a secure method (at least it wasnt for deluge 1.x last time i checked) , if the socks proxy connection drops for whatever reason then deluge will happily switch over to sending traffic over your LAN. i would encourage you to switch VPN provider and go with one that does support port forwarding, such as PIA.

 Rolling back to 1.3.15_18 fixed the issue.

PS: In my case, it's secure enough - I only allow socks connections from that host. This is how I found out it broke ;)

Edited by Kir
Link to post

Let me start by saying, I don't believe I am having and issues with my setup; everything seems to be working as it should. This is more for my personal knowledge. 

 

Now, these are probably dumb questions and have probably already been answered but I was unable to find a solid answer from my searches. I am very new to this so please forgive my ignorance....

 

I have DelugeVPN setup to download "/data/incomplete", once the download completes, it moves to file/folder to "/data/completed". This is working flawlessly. 

 

I have the Sonarr container path: /media set to "/mnt/user/T.V. Shows/" and the container path: /data set to "/mnt/user/Downloads/". 

I have Radarr set up similarly; container path: /media set to "/mnt/user/Movies/" and the container path: /data set to "/mnt/user/Downloads/".

 

I set Sonarr to download a TV Show, it went into Deluge as it should have. When it began downloading it was in the "incomplete" folder. When it finished downloading, it was moved to the "completed" folder. I then looked in my T.V. Shows folder and found the new folder with the individual season folder inside. 

 

I have Sonarr, Radarr, and Jackett setup to fetch the downloads. This is where my confusion sets in. To my understanding, Sonarr and Radarr are supposed to move the downloads from "/data/completed" to the appropriate media folders once Deluge has finished downloading them. As I mentioned, this appears to be happening.

 

My first question is, how does this magic happen? I guess I'm just confused about the flow of everything. 

 

Second question: after Sonarr moved the download file from the "completed" folder, I now have two copies of the downloaded file. One copy is still in the "completed" folder and the other is in "/mnt/user/T.V. Shows/" folder. Is this because the file is still seeding in Deluge? 

 

Sorry for the long post, I also attached an image of my settings in unraid. 

File Mappings.jpg

Link to post
11 minutes ago, Nano said:

Hi, i cannot get a .egg file to work, even if i put it in plugins manually, trying to get the autoremovetorrent plugin to work, any ideas??

Are you using the proper version? Many plugins have not yet been updated to work with 2.X

Link to post

Hi,

 

Has anyone got this to work with vpn unlimited, I don't want to sign up for another vpn service.

I tried following space invaders deluge vpn video. I can get deluge webui to run if i disable vpn. 

When I run the configuration it doesn't create appdata/binhex-delugevpn/"openvpn" folder

 

Thanks

 

Bernard

open vpn folder.jpg

Link to post
46 minutes ago, bgeorge104 said:

Has anyone got this to work with vpn unlimited, I don't want to sign up for another vpn service.

I took a good look around their website, and I found two pertinent things. 1, they only allow P2P / torrenting on some of their endpoints, 2, they don't mention how to get an open port, so you are going to need to get in touch with their tech support to see if they even support port forwarding.

 

You are probably going to be swimming upstream pretty hard trying to get this working, I guess it depends how much your time is worth chasing it.

Link to post

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.