[Support] binhex - DelugeVPN


Recommended Posts

So got a little further but still can't access the webgui even though I'm not sure what it is exactly.  I'm guessing it's localhost:58946...under deployed host ports I see binhex-delugevpn 8112 58846 58946 58946 8118.  I tried them all no success.

 

In the error log which is attached I see the following warning Sat Nov 18 13:33:14 2017 WARNING: file 'credentials.conf' is group or others accessible.

 

 

Log for_ binhex-delugevpn.html

Link to comment
2 minutes ago, DigitalDivide said:

gee everyone must have more important things to do on a Saturday afternoon...go figure! :)

Patience is a virtue.?

 

 

2 minutes ago, DigitalDivide said:

Ok so regenerated the ovpn file for just one server and I was able to connect to the gui.  I guess I now have to run a test and see if it downloads/uploads

If you continue to have issues I’d recommend attaching the supervisord.log from your appdata folder and maybe screenshots of your docker configuration.

Link to comment

I'm just joking. Using the single server I was able to connect and able to download a torrent.  I still have to verify if it's allowing uploads somehow.

 

Not sure if the speed is what I should expect. I'm getting a download speed of 1.7mbps but on my Raspberry Pi Deluge Server I'm getting almost 5mbps for the same file when running a test.  Is there something I can check for a better speed?

 

 

 

Link to comment

After updating the docker, I'm no longer able to connect to the GUI.  I get this error which may be a clue -

 

2017-11-18 05:13:08,564 DEBG 'start-script' stdout output:
Options error: Each 'connection' block must contain exactly one 'remote' directive

Any assistance would be appreciate.  Thank you...

Link to comment

I'm also having issues connecting to the GUI following the update of the container, Watchtower does this for me automatically. 

 

It appears to be a permission issue starting Iptables so I tried starting the container with higher privileges and this works, I never had to do this previously though. Related logs below.

 

Cheers.

 

2017-11-18 21:23:13 stdout  
2017-11-18 21:23:13 stdout Sun Nov 19 08:23:13 2017 Exiting due to fatal error
2017-11-18 21:23:13 stdout Sun Nov 19 08:23:13 2017 ERROR: Cannot ioctl TUNSETIFF tun: Operation not permitted (errno=1)
2017-11-18 21:23:13 stdout Sun Nov 19 08:23:13 2017 auth-token received, disabling auth-nocache for the authentication token
2017-11-18 21:23:13 stdout 2017-11-19 08:23:13,571 DEBG 'start-script' stdout output:
2017-11-18 21:23:11 stdout  
2017-11-18 21:23:11 stdout Sun Nov 19 08:23:11 2017 [138e01b0564ddddbe1a967299453a46d] Peer Connection Initiated with [AF_INET]109.201.154.154:1198
2017-11-18 21:23:11 stdout 2017-11-19 08:23:11,984 DEBG 'start-script' stdout output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout Sun Nov 19 08:23:10 2017 UDP link remote: [AF_INET]109.201.154.154:1198
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,466 DEBG 'start-script' stdout output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout Sun Nov 19 08:23:10 2017 UDP link local: (not bound)
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,464 DEBG 'start-script' stdout output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout Sun Nov 19 08:23:10 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]109.201.154.154:1198
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,461 DEBG 'start-script' stdout output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout Sun Nov 19 08:23:10 2017 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,451 DEBG 'start-script' stdout output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout [info] OpenVPN started
2017-11-18 21:23:10 stdout Sun Nov 19 08:23:10 2017 library versions: OpenSSL 1.1.0f  25 May 2017, LZO 2.10
2017-11-18 21:23:10 stdout Sun Nov 19 08:23:10 2017 OpenVPN 2.4.4 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 26 2017
2017-11-18 21:23:10 stdout Sun Nov 19 08:23:10 2017 WARNING: file 'credentials.conf' is group or others accessible
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,427 DEBG 'start-script' stdout output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout [info] Starting OpenVPN...
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,133 DEBG 'start-script' stdout output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout --------------------
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,133 DEBG 'start-script' stdout output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:10 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,132 DEBG 'start-script' stderr output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout --------------------
2017-11-18 21:23:10 stdout [info] iptables defined as follows...
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,129 DEBG 'start-script' stdout output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:10 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,128 DEBG 'start-script' stderr output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:10 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,124 DEBG 'start-script' stderr output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:10 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,120 DEBG 'start-script' stderr output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:10 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,116 DEBG 'start-script' stderr output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:10 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,105 DEBG 'start-script' stderr output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:10 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,101 DEBG 'start-script' stderr output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout getsockopt failed strangely: Operation not permitted
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,094 DEBG 'start-script' stderr output:
2017-11-18 21:23:10 stdout  
2017-11-18 21:23:10 stdout getsockopt failed strangely: Operation not permitted
2017-11-18 21:23:10 stdout 2017-11-19 08:23:10,063 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,904 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,896 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,891 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,888 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,884 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,880 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,794 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,791 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,778 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,774 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,749 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,384 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,367 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout Perhaps iptables or your kernel needs to be upgraded.
2017-11-18 21:23:09 stdout iptables v1.6.1: can't initialize iptables table `filter': Permission denied (you must be root)
2017-11-18 21:23:09 stdout 2017-11-19 08:23:09,223 DEBG 'start-script' stderr output:
2017-11-18 21:23:09 stdout  
2017-11-18 21:23:09 stdout [info] Docker network defined as    172.17.0.0/16
2017-11-18 21:23:08 stdout 2017-11-19 08:23:08,677 DEBG 'start-script' stdout output:
2017-11-18 21:23:08 stdout  
2017-11-18 21:23:08 stdout RTNETLINK answers: Operation not permitted
2017-11-18 21:23:08 stdout 2017-11-19 08:23:08,365 DEBG 'start-script' stderr output:
2017-11-18 21:23:08 stdout  
2017-11-18 21:23:08 stdout RTNETLINK answers: Operation not permitted
2017-11-18 21:23:08 stdout 2017-11-19 08:23:08,363 DEBG 'start-script' stderr output:
2017-11-18 21:23:08 stdout  
2017-11-18 21:23:08 stdout [info] iptable_mangle support detected, adding fwmark for tables
2017-11-18 21:23:08 stdout 2017-11-19 08:23:08,361 DEBG 'start-script' stdout output:
2017-11-18 21:23:08 stdout  
2017-11-18 21:23:08 stdout --------------------
2017-11-18 21:23:08 stdout 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.3 
2017-11-18 21:23:08 stdout default via 172.17.0.1 dev eth0 
2017-11-18 21:23:08 stdout 2017-11-19 08:23:08,203 DEBG 'start-script' stdout output:
2017-11-18 21:23:08 stdout  
2017-11-18 21:23:08 stdout --------------------
2017-11-18 21:23:08 stdout [info] ip route defined as follows...
2017-11-18 21:23:08 stdout 2017-11-19 08:23:08,202 DEBG 'start-script' stdout output:
2017-11-18 21:23:08 stdout  
2017-11-18 21:23:08 stdout RTNETLINK answers: Operation not permitted
2017-11-18 21:23:08 stdout 2017-11-19 08:23:08,201 DEBG 'start-script' stderr output:
2017-11-18 21:23:08 stdout  
2017-11-18 21:23:08 stdout [info] Adding 10.53.53.0/24 as route via docker eth0
2017-11-18 21:23:08 stdout 2017-11-19 08:23:08,199 DEBG 'start-script' stdout output:
2017-11-18 21:23:06 stdout  
2017-11-18 21:23:06 stdout [info] Adding 8.8.4.4 to /etc/resolv.conf
2017-11-18 21:23:06 stdout 2017-11-19 08:23:06,231 DEBG 'start-script' stdout output:
2017-11-18 21:23:06 stdout  
2017-11-18 21:23:06 stdout [info] Adding 37.235.1.177 to /etc/resolv.conf
2017-11-18 21:23:06 stdout 2017-11-19 08:23:06,225 DEBG 'start-script' stdout output:
2017-11-18 21:23:06 stdout  
2017-11-18 21:23:06 stdout [info] Adding 209.222.18.218 to /etc/resolv.conf
2017-11-18 21:23:06 stdout 2017-11-19 08:23:06,214 DEBG 'start-script' stdout output:
2017-11-18 21:23:06 stdout  
2017-11-18 21:23:06 stdout [info] Adding 8.8.8.8 to /etc/resolv.conf
2017-11-18 21:23:06 stdout 2017-11-19 08:23:06,205 DEBG 'start-script' stdout output:
2017-11-18 21:23:06 stdout  
2017-11-18 21:23:06 stdout [info] Adding 37.235.1.174 to /etc/resolv.conf
2017-11-18 21:23:06 stdout 2017-11-19 08:23:06,194 DEBG 'start-script' stdout output:
2017-11-18 21:23:06 stdout  
2017-11-18 21:23:06 stdout [info] Adding 209.222.18.222 to /etc/resolv.conf
2017-11-18 21:23:06 stdout 2017-11-19 08:23:06,187 DEBG 'start-script' stdout output:
2017-11-18 21:23:06 stdout  
2017-11-18 21:23:06 stdout [info] Default route for container is 172.17.0.1
2017-11-18 21:23:06 stdout 2017-11-19 08:23:06,175 DEBG 'start-script' stdout output:
2017-11-18 21:23:05 stdout  
2017-11-18 21:23:05 stdout [info] VPN is enabled, checking VPN tunnel local ip is valid
2017-11-18 21:23:05 stdout 2017-11-19 08:23:05,405 DEBG 'deluge-script' stdout output:
2017-11-18 21:23:05 stdout  
2017-11-18 21:23:05 stdout [info] Deluge config file already exists, skipping copy
2017-11-18 21:23:05 stdout 2017-11-19 08:23:05,402 DEBG 'deluge-script' stdout output:
2017-11-18 21:23:05 stdout 2017-11-19 08:23:05,357 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-11-18 21:23:05 stdout 2017-11-19 08:23:05,356 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-11-18 21:23:05 stdout 2017-11-19 08:23:05,356 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-11-18 21:23:05 stdout 2017-11-19 08:23:05,356 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-11-18 21:23:05 stdout  
2017-11-18 21:23:05 stdout [info] VPN is enabled, beginning configuration of VPN
2017-11-18 21:23:05 stdout 2017-11-19 08:23:05,356 DEBG 'start-script' stdout output:
2017-11-18 21:23:05 stdout 2017-11-19 08:23:05,126 INFO reaped unknown pid 8
2017-11-18 21:23:05 stdout 2017-11-19 08:23:05,122 INFO spawned: 'privoxy-script' with pid 132
2017-11-18 21:23:05 stdout 2017-11-19 08:23:05,119 INFO spawned: 'deluge-web-script' with pid 131
2017-11-18 21:23:05 stdout 2017-11-19 08:23:05,116 INFO spawned: 'deluge-script' with pid 130
2017-11-18 21:23:05 stdout 2017-11-19 08:23:05,114 INFO spawned: 'start-script' with pid 129
2017-11-18 21:23:04 stdout 2017-11-19 08:23:04,110 INFO supervisord started with pid 7
2017-11-18 21:23:03 stdout 2017-11-19 08:23:03,963 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2017-11-18 21:23:03 stdout 2017-11-19 08:23:03,963 CRIT Set uid to user 0
2017-11-18 21:22:56 stdout 2017-11-19 08:22:56.021712 [info] Starting Supervisor...
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.910929 [info] Setting permissions on files/folders inside container...
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.853812 [info] ENABLE_PRIVOXY defined as 'yes'
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.789607 [info] STRICT_PORT_FORWARD defined as 'yes'
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.726069 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.662415 [info] VPN_PASS defined as 'REDACTED'
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.599028 [info] VPN_USER defined as 'REDACTED'
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.534956 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,8.8.8.8,209.222.18.218,37.235.1.177,8.8.4.4'
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.464257 [info] LAN_NETWORK defined as '10.53.53.0/24'
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.395615 [info] VPN_PROV defined as 'pia'
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.329266 [info] VPN_DEVICE_TYPE defined as 'tun'
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.265987 [info] VPN_PROTOCOL defined as 'udp'
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.199734 [info] VPN_PORT defined as '1198'
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.133069 [info] VPN_REMOTE defined as 'nl.privateinternetaccess.com'
2017-11-18 21:22:55 stdout 2017-11-19 08:22:55.069179 [info] VPN remote line defined as 'nl.privateinternetaccess.com 1198'
2017-11-18 21:22:55 stdout dos2unix: converting file /config/openvpn/Netherlands.ovpn to Unix format...
2017-11-18 21:22:55 stdout 2017-11-19 08:22:54.993098 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Netherlands.ovpn
2017-11-18 21:22:55 stdout 2017-11-19 08:22:54.712350 [info] VPN_ENABLED defined as 'yes'
2017-11-18 21:22:54 stdout 2017-11-19 08:22:54.567682 [info] Permissions already set for volume mappings
2017-11-18 21:22:54 stdout 2017-11-19 08:22:54.496492 [warn] UMASK not defined (via -e UMASK), defaulting to '000'
2017-11-18 21:22:53 stdout 2017-11-19 08:22:53.537321 [info] PGID defined as '100'
2017-11-18 21:22:53 stdout 2017-11-19 08:22:53.273899 [info] PUID defined as '1024'
2017-11-18 21:22:53 stdout 2017-11-19 08:22:53.036911 [info] System information Linux Deluge 4.4.59+ #22259 SMP PREEMPT Mon Oct 2 02:42:20 CST 2017
Link to comment

Hi all

 

Hoping for some help. I did have delugevpn running, recently couchpotato and sonarr have stopped connecting to the indexers and i can get to their web gui.

 

Delguevpn cannot start in the docker and i cannot access the webgui at all. Attached are the logs for all three. Looking at them it appeared my usenet server subscription was the issue but i have checked and it is still active.

 

I am not an expert and would appreciate any direction to solve my issues.

 

Thanks

 

deluge logs after restart.docx

couchpotato logsf.docx

sonaar logs.docx

Link to comment
Hi all

 

Hoping for some help. I did have delugevpn running, recently couchpotato and sonarr have stopped connecting to the indexers and i can get to their web gui.

 

Delguevpn cannot start in the docker and i cannot access the webgui at all. Attached are the logs for all three. Looking at them it appeared my usenet server subscription was the issue but i have checked and it is still active.

 

I am not an expert and would appreciate any direction to solve my issues.

 

Thanks

 

deluge logs after restart.docx

couchpotato logsf.docx

sonaar logs.docx

Looks like your .ovpn file is not correct. Try to redownload that and the certificates from yohr vpn provider.

 

And sonarr is complaining about the proxy. Are you using delugevpn's proxy? If so, it wont work until ypur vpn config is fixed

 

Sent from my SGH-I337M using Tapatalk

 

 

 

Link to comment
On 11/17/2017 at 12:01 PM, Lytic said:

Question / Problem:

I have been using DelugeVPN and I seem to be having issues with port forwarding with PIA. I know that DelugeVPN automatically designates Deluge's incoming port to reflect the single open port reported by PIA. Once I see this port in Deluge's settings I hop over to my router's GUI and open the port manually through my router. At this point, all of my torrents become connectable to each tracker's server.

 

My problem is that every day or so my torrents become unconnectable. If I go back into my settings the port has not changed and if I go back to my router the port is still open. In order to fix this problem I have to manually restart DelugeVPN every morning and go back through to open my ports.

 

What is going wrong? And how can I become connectable without restarting the docker every single day? Thanks a ton in advance.

Does anyone have any ideas about my issue? I only have 10 more days on my unRAID trial and I can't commit to purchasing it if I continue having this issue.

 

By the way, here is a section of my log file. It looks like SYN flooding may be connected to my connection problems?

 

 

Nov 19 03:58:42 unRAID kernel: docker0: port 2(veth90dd007) entered disabled state
Nov 19 03:58:42 unRAID kernel: device veth90dd007 left promiscuous mode
Nov 19 03:58:42 unRAID kernel: docker0: port 2(veth90dd007) entered disabled state
Nov 19 03:58:43 unRAID kernel: docker0: port 2(veth83ec97d) entered blocking state
Nov 19 03:58:43 unRAID kernel: docker0: port 2(veth83ec97d) entered disabled state
Nov 19 03:58:43 unRAID kernel: device veth83ec97d entered promiscuous mode
Nov 19 03:58:43 unRAID kernel: docker0: port 2(veth83ec97d) entered blocking state
Nov 19 03:58:43 unRAID kernel: docker0: port 2(veth83ec97d) entered forwarding state
Nov 19 03:58:43 unRAID kernel: eth0: renamed from veth150ac6b
Nov 19 04:23:05 unRAID kernel: TCP: request_sock_TCP: Possible SYN flooding on port 27515. Sending cookies. Check SNMP counters.

 

Thanks!

Edited by Lytic
Link to comment

Hey guys, STUPID question here. I got things all set up, downloads working, Proxy working on the MacBook (checked using ipinfodb.com) But... how on EARTH do I tell if the VPN is working in deluge or not? Is there a way to see IP/Location being used? I must be missing something. Searched for about an hour and feel dumb...

Link to comment
1 hour ago, Malachi89 said:

Hey guys, STUPID question here. I got things all set up, downloads working, Proxy working on the MacBook (checked using ipinfodb.com) But... how on EARTH do I tell if the VPN is working in deluge or not? Is there a way to see IP/Location being used? I must be missing something. Searched for about an hour and feel dumb...

 

DelugeVPN will not start if the VPN does not connect. If you would like to see the IP address, you can download a torrent ip checker. Once you add the torrent to your client, click on the torrent and look down under either your "status" or "details" tab to view the IP address the torrent recorded.

Link to comment
1 hour ago, Malachi89 said:

Hey guys, STUPID question here. I got things all set up, downloads working, Proxy working on the MacBook (checked using ipinfodb.com) But... how on EARTH do I tell if the VPN is working in deluge or not? Is there a way to see IP/Location being used? I must be missing something. Searched for about an hour and feel dumb...

See the FAQ : (referenced in Binhex's .sig).

Link to comment
On 11/18/2017 at 1:21 PM, arcane said:

After updating the docker, I'm no longer able to connect to the GUI.  I get this error which may be a clue -

 


2017-11-18 05:13:08,564 DEBG 'start-script' stdout output:
Options error: Each 'connection' block must contain exactly one 'remote' directive

Any assistance would be appreciate.  Thank you...

Bump.  IF anybody has some guidance, that'd be great.  Thanks!

Link to comment
On 18/11/2017 at 8:34 PM, DigitalDivide said:

I'm just joking. Using the single server I was able to connect and able to download a torrent.  I still have to verify if it's allowing uploads somehow.

 

Not sure if the speed is what I should expect. I'm getting a download speed of 1.7mbps but on my Raspberry Pi Deluge Server I'm getting almost 5mbps for the same file when running a test.  Is there something I can check for a better speed?

 

 

 

 

have you setup port forwarding with your VPN provider (NOT your router)? unless you do this your speeds will be low.

 

Have a read of the newbie guide 

 

Link to comment
On 18/11/2017 at 9:21 PM, arcane said:

After updating the docker, I'm no longer able to connect to the GUI.  I get this error which may be a clue -

 


2017-11-18 05:13:08,564 DEBG 'start-script' stdout output:
Options error: Each 'connection' block must contain exactly one 'remote' directive

Any assistance would be appreciate.  Thank you...

 

i think is probably due to the removal of multi remote line ovpn files, looks like you are using an advanced feature i wasnt even aware of, connection blocks in your ovpn file, please post your ovpn file here removing any passwords etc.

Link to comment
On 18/11/2017 at 10:06 PM, Devo-McDuff said:

t appears to be a permission issue starting Iptables so I tried starting the container with higher privileges and this works, I never had to do this previously though.

 

the required permissions to run this docker image have not changed since its first inception,  in any case the minimum permissions defined via the docker run command are:-

 

--cap-add=NET_ADMIN

or if you cant define it at a granular level then use:-

 

--privileged=true

 

Link to comment
16 hours ago, Lytic said:

Does anyone have any ideas about my issue? I only have 10 more days on my unRAID trial and I can't commit to purchasing it if I continue having this issue.

 

By the way, here is a section of my log file. It looks like SYN flooding may be connected to my connection problems?

 

 

Nov 19 03:58:42 unRAID kernel: docker0: port 2(veth90dd007) entered disabled state
Nov 19 03:58:42 unRAID kernel: device veth90dd007 left promiscuous mode
Nov 19 03:58:42 unRAID kernel: docker0: port 2(veth90dd007) entered disabled state
Nov 19 03:58:43 unRAID kernel: docker0: port 2(veth83ec97d) entered blocking state
Nov 19 03:58:43 unRAID kernel: docker0: port 2(veth83ec97d) entered disabled state
Nov 19 03:58:43 unRAID kernel: device veth83ec97d entered promiscuous mode
Nov 19 03:58:43 unRAID kernel: docker0: port 2(veth83ec97d) entered blocking state
Nov 19 03:58:43 unRAID kernel: docker0: port 2(veth83ec97d) entered forwarding state
Nov 19 03:58:43 unRAID kernel: eth0: renamed from veth150ac6b
Nov 19 04:23:05 unRAID kernel: TCP: request_sock_TCP: Possible SYN flooding on port 27515. Sending cookies. Check SNMP counters.

 

Thanks!

 

ive not seen this before, are you guys running the unstable release candidate of unraid by any chance? when did this start happening?, im assuming it was working ok?, after latest image pull down or possibly if using unraid RC's then maybe when updating to latest RC?

 

edit - and can you establish a connection to the vpn tunnel, or does this knock you out and/or not allow you to establish a tunnel?

 

edit2 - found this link, my guess is a kernel update in unraid has triggered SYN flood protection, see here https://access.redhat.com/solutions/30453

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

Ive not seen this before, are you guys running the unstable release candidate of unraid by any chance? when did this start happening?, im assuming it was working ok?, after latest image pull down or possibly if using unraid RC's then maybe when updating to latest RC?

I’m running 6.3.5.

 

1 hour ago, binhex said:

edit - and can you establish a connection to the vpn tunnel, or does this knock you out and/or not allow you to establish a tunnel?

Everything seems to be working properly. If I hadn’t checked my logs I wouldn’t have known about the sun flooding. I only see the error once just after a restart of the docker.

 

1 hour ago, binhex said:

edit2 - found this link, my guess is a kernel update in unraid has triggered SYN flood protection, see here https://access.redhat.com/solutions/30453

I saw that too. I was able to make the threshold adjustments described in the article, but it appears that a server reboot is also required which will mean I’ll lose the changes. I know I’d need to add something to the go file but no idea what. The article says to make an edit in /etc-


echo “net.core.somaxconn = 2048” >> /etc/sysctl.conf

echo “net.ipv4.tcp_max_syn_backlog = 512” >> /etc/sysctl.conf

Im not sure how to adapt this for the go file?

 

I’m not much on network protocols but if I understand the article correctly this will just be hiding the issue. Is there some way to actually fix it?

Link to comment
39 minutes ago, wgstarks said:

if I understand the article correctly this will just be hiding the issue. Is there some way to actually fix it?

 

well its tricky, i think the reason it think there is a syn flood attempt is due to the multiple connections that torrent clients make, this is just the nature of torrents, you have a lot of inbound and outbound connections, its how it's designed, your options are, try the modifications to the kernel shown in your post, ignore it, try reducing the number of connections defined in deluge config, switch to using usenet.

 

43 minutes ago, wgstarks said:

Im not sure how to adapt this for the go file?

 

should be as simple as putting those two lines in your go file, thats it. assuming file /etc/sysctl.conf exists?

Link to comment

Tried making the changes-

 

go file-

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &
/boot/cache_dirs -w
beep -l 300 -f 220.00 -n -l 300 -f 293.66 -D 100 -n -l 150 -f 220.00 -n -l 150 -f 293.66 -D 100 -n -l 500 -f 349.23 -D 100 -n -l 500 -f 293.66 -D 100 -n -l 300 -f 349.23 -D 100 -n -l 150 -f 293.66 -D 100 -n -l 150 -f 349.23 -D 100 -n -l 500 -f 440.00 -D 100 -n -l 500 -f 349.23 -D 100 -n -l 300 -f 440.00 -D 100 -n -l 150 -f 349.23 -D 100 -n -l 150 -f 440.00 -D 100 -n -l 500 -f 523.25 -D 100 -n -l 500 -f 261.63 -D 100 -n -l 300 -f 349.23 -D 100 -n -l 150 -f 261.63 -D 100 -n -l 150 -f 349.23 -D 100 -n -l 500 -f 440.00 -D 300 -n -l 300 -f 261.63 -n -l 300 -f 349.23 -D 100 -n -l 150 -f 261.63 -n -l 150 -f 349.23 -D 100 -n -l 500 -f 440.00 -D 100 -n -l 500 -f 349.23 -D 100 -n -l 300 -f 440.00 -D 100 -n -l 150 -f 349.23 -D 100 -n -l 150 -f 440.00 -D 100 -n -l 500 -f 523.25 -D 100 -n -l 500 -f 440.00 -D 100 -n -l 300 -f 523.25 -D 100 -n -l 150 -f 440.00 -D 100 -n -l 150 -f 523.25 -D 100 -n -l 500 -f 659.26 -D 100 -n -l 500 -f 329.63 -D 100 -n -l 300 -f 440.00 -D 100 -n -l 150 -f 329.63 -D 100 -n -l 150 -f 440.00 -D 100 -n -l 500 -f 554.00 -D 300 -n -l 300 -f 220.00 -D 100 -n -l 300 -f 233.00 -D 100 -n -l 150 -f 196.00 -D 100 -n -l 300 -f 223.00 -D 100 -n -l 750 -f 293.66 -D 300 -n -l 300 -f 220.00 -D 100 -n -l 300 -f 233.00 -D 100 -n -l 150 -f 196.00 -D 100 -n -l 300 -f 223.00 -D 100 -n -l 750 -f 311.00 -D 100 -n -l 300 -f 293.66 -D 100 -n -l 150 -f 220.00 -D 100 -n -l 150 -f 293.66 -D 100 -n -l 500 -f 349.23 -D 100 -n -l 300 -f 220.00 -D 100 -n -l 300 -f 233.00 -D 100 -n -l 150 -f 196.00 -D 100 -n -l 150 -f 233.00 -D 100 -n -l 500 -f 293.66 -D 300 -n -l 300 -f 220.00 -D 100 -n -l 300 -f 233.00 -D 100 -n -l 150 -f 196.00 -D 100 -n -l 150 -f 233.00 -D 100 -n -l 500 -f 329.63 -D 100 -n -l 300 -f 220.00 -D 100 -n -l 300 -f 220.00 -D 100 -n -l 150 -f 293.66 -D 100 -n -l 150 -f 370.00 -D 100 -n -l 500 -f 440.00 -D 100
# force iptable mangle module to load (required for *vpn dockers)
/sbin/modprobe iptable_mangle
# Enlarge the LOG partition
mount -o remount,size=384m /var/log
#syn flooding changes
echo "net.core.somaxconn = 2048" >> /etc/sysctl.conf
echo "net.ipv4.tcp_max_syn_backlog = 1024" >> /etc/sysctl.conf

 

 

/etc/sysctl.config-

# from https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers
# increase the number of inotify watches
fs.inotify.max_user_watches=524288

# from: https://www.andrisoft.com/support/portal/kb/article/os-level-optimisations
# better support for 10Gb ethernet
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_wmem = 4096 65536 16777216
net.core.somaxconn = 2048
net.ipv4.tcp_max_syn_backlog = 1024

 

The changes are being written to sysctl.config but they aren'y being implemented on boot-

root@Brunnhilde:/etc# sysctl net.core.somaxconn
net.core.somaxconn = 128
root@Brunnhilde:/etc# sysctl net.ipv4.tcp_max_syn_backlog
net.ipv4.tcp_max_syn_backlog = 512
root@Brunnhilde:/etc# 

Any ideas why?

Link to comment
Tried making the changes-
 
go file-
#!/bin/bash# Start the Management Utility/usr/local/sbin/emhttp &/boot/cache_dirs -wbeep -l 300 -f 220.00 -n -l 300 -f 293.66 -D 100 -n -l 150 -f 220.00 -n -l 150 -f 293.66 -D 100 -n -l 500 -f 349.23 -D 100 -n -l 500 -f 293.66 -D 100 -n -l 300 -f 349.23 -D 100 -n -l 150 -f 293.66 -D 100 -n -l 150 -f 349.23 -D 100 -n -l 500 -f 440.00 -D 100 -n -l 500 -f 349.23 -D 100 -n -l 300 -f 440.00 -D 100 -n -l 150 -f 349.23 -D 100 -n -l 150 -f 440.00 -D 100 -n -l 500 -f 523.25 -D 100 -n -l 500 -f 261.63 -D 100 -n -l 300 -f 349.23 -D 100 -n -l 150 -f 261.63 -D 100 -n -l 150 -f 349.23 -D 100 -n -l 500 -f 440.00 -D 300 -n -l 300 -f 261.63 -n -l 300 -f 349.23 -D 100 -n -l 150 -f 261.63 -n -l 150 -f 349.23 -D 100 -n -l 500 -f 440.00 -D 100 -n -l 500 -f 349.23 -D 100 -n -l 300 -f 440.00 -D 100 -n -l 150 -f 349.23 -D 100 -n -l 150 -f 440.00 -D 100 -n -l 500 -f 523.25 -D 100 -n -l 500 -f 440.00 -D 100 -n -l 300 -f 523.25 -D 100 -n -l 150 -f 440.00 -D 100 -n -l 150 -f 523.25 -D 100 -n -l 500 -f 659.26 -D 100 -n -l 500 -f 329.63 -D 100 -n -l 300 -f 440.00 -D 100 -n -l 150 -f 329.63 -D 100 -n -l 150 -f 440.00 -D 100 -n -l 500 -f 554.00 -D 300 -n -l 300 -f 220.00 -D 100 -n -l 300 -f 233.00 -D 100 -n -l 150 -f 196.00 -D 100 -n -l 300 -f 223.00 -D 100 -n -l 750 -f 293.66 -D 300 -n -l 300 -f 220.00 -D 100 -n -l 300 -f 233.00 -D 100 -n -l 150 -f 196.00 -D 100 -n -l 300 -f 223.00 -D 100 -n -l 750 -f 311.00 -D 100 -n -l 300 -f 293.66 -D 100 -n -l 150 -f 220.00 -D 100 -n -l 150 -f 293.66 -D 100 -n -l 500 -f 349.23 -D 100 -n -l 300 -f 220.00 -D 100 -n -l 300 -f 233.00 -D 100 -n -l 150 -f 196.00 -D 100 -n -l 150 -f 233.00 -D 100 -n -l 500 -f 293.66 -D 300 -n -l 300 -f 220.00 -D 100 -n -l 300 -f 233.00 -D 100 -n -l 150 -f 196.00 -D 100 -n -l 150 -f 233.00 -D 100 -n -l 500 -f 329.63 -D 100 -n -l 300 -f 220.00 -D 100 -n -l 300 -f 220.00 -D 100 -n -l 150 -f 293.66 -D 100 -n -l 150 -f 370.00 -D 100 -n -l 500 -f 440.00 -D 100# force iptable mangle module to load (required for *vpn dockers)/sbin/modprobe iptable_mangle# Enlarge the LOG partitionmount -o remount,size=384m /var/log#syn flooding changesecho "net.core.somaxconn = 2048" >> /etc/sysctl.confecho "net.ipv4.tcp_max_syn_backlog = 1024" >> /etc/sysctl.conf

 
 
/etc/sysctl.config-

# from https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers# increase the number of inotify watchesfs.inotify.max_user_watches=524288# from: https://www.andrisoft.com/support/portal/kb/article/os-level-optimisations# better support for 10Gb ethernetnet.core.rmem_max = 16777216net.core.wmem_max = 16777216net.ipv4.tcp_rmem = 4096 87380 16777216net.ipv4.tcp_wmem = 4096 65536 16777216net.core.somaxconn = 2048net.ipv4.tcp_max_syn_backlog = 1024

 
The changes are being written to sysctl.config but they aren'y being implemented on boot-

root@Brunnhilde:/etc# sysctl net.core.somaxconnnet.core.somaxconn = 128root@Brunnhilde:/etc# sysctl net.ipv4.tcp_max_syn_backlognet.ipv4.tcp_max_syn_backlog = 512root@Brunnhilde:/etc# 

Any ideas why?

Well the file looks fine, so I can only assume the go file is run too late and thus the changes arent bring picked up, maybe somebody in general support can suggest something?

Sent from my SM-G935F using Tapatalk

Link to comment

Hi, 

I've installed Deluge with the /data/ path pointing to /mnt/user/downloads.

 

However, I would like to use it to keep my Mame roms up to date, however, my mame roms are in /mnt/user/media/Roms/MAME 0.190 ROMs (non-merged) - which I will manually change to MAME 0.191 (0.192, 0.193 etc) when new ones come out, so when I open the torrent, I want to point it to that folder, so it can scan it and download the changed / updated ROMs.

 

Is there anyway I can do this with my current setup, or would I need to point the /data/path somewhere else?

 

Cheers,

Stewart.

Link to comment

Change the name of the folder with the new release.

When the add torrent options box appears before you add a new torrent i click options and where it says data/incomplete i change it to data/completed. ( assuming your dir structure and shares are default) If not move the files back into incomplete then rename the folder with new name.

 

this will check what you have and complete the new release.

 

Best keep this chatter away from Binhex`s DelugeVPN support thread :)

 

 

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