[Support] binhex - DelugeVPN


8664 posts in this topic Last Reply

Recommended Posts

48 minutes ago, Biloxi_1 said:

So I went to grab logs to upload this morning and my container is working again. I didnt make any changes, so my only theory is the vpn server I was connecting to was having issues, but that seems strange, because I tried 3 separate servers. Either way it is working again. Thanks for the advice, and I will remember in the future to upload logs when seeking help.

ok, I had to restart the container because I fat fingered a file path while re-configuring and I am back where I started, I cannot log into the webui from my LAN with the vpn enabled. Here is my log, would anyone be willing to assist me in figuring this out?

 

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

2018-06-29 06:38:27.775261 [info] Host is running unRAID
2018-06-29 06:38:27.797646 [info] System information Linux c66e9c800913 4.14.13-unRAID #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 x86_64 GNU/Linux
2018-06-29 06:38:27.823124 [info] PUID defined as '99'
2018-06-29 06:38:28.056046 [info] PGID defined as '100'
2018-06-29 06:38:28.510192 [info] UMASK defined as '000'
2018-06-29 06:38:28.535557 [info] Permissions already set for volume mappings
2018-06-29 06:38:28.565467 [info] VPN_ENABLED defined as 'yes'
2018-06-29 06:38:28.596707 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/ca301.nordvpn.com.udp.ovpn
dos2unix: converting file /config/openvpn/ca301.nordvpn.com.udp.ovpn to Unix format...
2018-06-29 06:38:28.648026 [info] VPN remote line defined as 'remote 207.189.31.109 1194'
2018-06-29 06:38:28.674828 [info] VPN_REMOTE defined as '207.189.31.109'
2018-06-29 06:38:28.701593 [info] VPN_PORT defined as '1194'
2018-06-29 06:38:28.735308 [info] VPN_PROTOCOL defined as 'udp'
2018-06-29 06:38:28.761654 [info] VPN_DEVICE_TYPE defined as 'tun0'
2018-06-29 06:38:28.786282 [info] VPN_PROV defined as 'custom'
2018-06-29 06:38:28.812200 [info] LAN_NETWORK defined as '10.10.10.0/24'
2018-06-29 06:38:28.837771 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4'
2018-06-29 06:38:28.863517 [info] VPN_USER defined as 'XXXXXXXX'
2018-06-29 06:38:28.888834 [info] VPN_PASS defined as 'XXXXXXXX'
2018-06-29 06:38:28.916754 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2018-06-29 06:38:28.943604 [info] ENABLE_PRIVOXY defined as 'no'
2018-06-29 06:38:28.971067 [info] Starting Supervisor...
2018-06-29 06:38:29,120 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2018-06-29 06:38:29,121 INFO Set uid to user 0 succeeded
2018-06-29 06:38:29,124 INFO supervisord started with pid 7
2018-06-29 06:38:30,126 INFO spawned: 'start-script' with pid 136
2018-06-29 06:38:30,128 INFO spawned: 'deluge-script' with pid 137
2018-06-29 06:38:30,129 INFO spawned: 'deluge-web-script' with pid 138
2018-06-29 06:38:30,129 INFO spawned: 'privoxy-script' with pid 139
2018-06-29 06:38:30,130 INFO reaped unknown pid 8
2018-06-29 06:38:30,133 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2018-06-29 06:38:30,133 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-06-29 06:38:30,133 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-06-29 06:38:30,133 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-06-29 06:38:30,133 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-06-29 06:38:30,135 DEBG 'deluge-script' stdout output:
[info] Deluge config file already exists, skipping copy

2018-06-29 06:38:30,136 DEBG 'deluge-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2018-06-29 06:38:30,136 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled

2018-06-29 06:38:30,136 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 23423994509144 for <Subprocess at 23423997082656 with name privoxy-script in state RUNNING> (stderr)>
2018-06-29 06:38:30,136 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 23423994508712 for <Subprocess at 23423997082656 with name privoxy-script in state RUNNING> (stdout)>
2018-06-29 06:38:30,136 INFO exited: privoxy-script (exit status 0; expected)
2018-06-29 06:38:30,137 DEBG received SIGCLD indicating a child quit
2018-06-29 06:38:30,139 DEBG 'start-script' stdout output:
[warn] Username contains characters which could cause authentication issues, please consider changing this if possible

2018-06-29 06:38:30,143 DEBG 'start-script' stdout output:
[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

2018-06-29 06:38:30,220 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2018-06-29 06:38:30,223 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2018-06-29 06:38:30,226 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2018-06-29 06:38:30,229 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2018-06-29 06:38:30,232 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2018-06-29 06:38:30,234 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2018-06-29 06:38:30,237 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2018-06-29 06:38:30,239 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2018-06-29 06:38:30,242 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2018-06-29 06:38:30,246 DEBG 'start-script' stdout output:
207.189.31.109

2018-06-29 06:38:30,253 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2018-06-29 06:38:30,254 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.14.13-unRAID

2018-06-29 06:38:30,255 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2018-06-29 06:38:30,255 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'

2018-06-29 06:38:30,255 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2018-06-29 06:38:30,258 DEBG 'start-script' stdout output:
[info] Adding 10.10.10.0/24 as route via docker eth0

2018-06-29 06:38:30,259 DEBG 'start-script' stdout output:
[info] ip route defined as follows...

2018-06-29 06:38:30,259 DEBG 'start-script' stdout output:
--------------------

2018-06-29 06:38:30,259 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
10.10.10.0/24 via 172.17.0.1 dev eth0

2018-06-29 06:38:30,259 DEBG 'start-script' stdout output:
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.4
--------------------

2018-06-29 06:38:30,281 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2018-06-29 06:38:30,360 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2018-06-29 06:38:30,362 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p 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 10.10.10.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 OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p 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 10.10.10.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

2018-06-29 06:38:30,362 DEBG 'start-script' stdout output:
--------------------

2018-06-29 06:38:30,363 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2018-06-29 06:38:30,382 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 WARNING: file 'credentials.conf' is group or others accessible
Fri Jun 29 06:38:30 2018 OpenVPN 2.4.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 1 2018
Fri Jun 29 06:38:30 2018 library versions: OpenSSL 1.1.0g 2 Nov 2017, LZO 2.10

2018-06-29 06:38:30,382 DEBG 'start-script' stdout output:
[info] OpenVPN started

2018-06-29 06:38:30,383 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 WARNING: --ping should normally be used with --ping-restart or --ping-exit
Fri Jun 29 06:38:30 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Fri Jun 29 06:38:30 2018 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Fri Jun 29 06:38:30 2018 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication

2018-06-29 06:38:30,383 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.31.109:1194
Fri Jun 29 06:38:30 2018 Socket Buffers: R=[212992->212992] S=[212992->212992]
Fri Jun 29 06:38:30 2018 UDP link local: (not bound)
Fri Jun 29 06:38:30 2018 UDP link remote: [AF_INET]207.189.31.109:1194

2018-06-29 06:38:30,469 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 TLS: Initial packet from [AF_INET]207.189.31.109:1194, sid=f931ff2c 29853a57

2018-06-29 06:38:30,559 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA

2018-06-29 06:38:30,560 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 VERIFY OK: depth=1, C=PA, O=NordVPN, CN=NordVPN CA2

2018-06-29 06:38:30,560 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 VERIFY KU OK
Fri Jun 29 06:38:30 2018 Validating certificate extended key usage
Fri Jun 29 06:38:30 2018 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication

2018-06-29 06:38:30,560 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 VERIFY EKU OK
Fri Jun 29 06:38:30 2018 VERIFY OK: depth=0, CN=ca301.nordvpn.com

2018-06-29 06:38:30,915 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Fri Jun 29 06:38:30 2018 [ca301.nordvpn.com] Peer Connection Initiated with [AF_INET]207.189.31.109:1194

2018-06-29 06:38:31,936 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:31 2018 SENT CONTROL [ca301.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2018-06-29 06:38:32,021 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,sndbuf 524288,rcvbuf 524288,dhcp-option DNS 103.86.96.100,dhcp-option DNS 103.86.99.100,route-gateway 10.8.8.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.8.8.68 255.255.255.0,peer-id 12,cipher AES-256-GCM'

2018-06-29 06:38:32,021 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: timers and/or timeouts modified
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
Fri Jun 29 06:38:32 2018 Socket Buffers: R=[212992->1048576] S=[212992->1048576]
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: --ifconfig/up options modified
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: route options modified
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: route-related options modified
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: peer-id set
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: adjusting link_mtu to 1657
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: data channel crypto options modified
Fri Jun 29 06:38:32 2018 Data Channel: using negotiated cipher 'AES-256-GCM'
Fri Jun 29 06:38:32 2018 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jun 29 06:38:32 2018 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jun 29 06:38:32 2018 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:04

2018-06-29 06:38:32,022 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 TUN/TAP device tun0 opened
Fri Jun 29 06:38:32 2018 TUN/TAP TX queue length set to 100

2018-06-29 06:38:32,022 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Fri Jun 29 06:38:32 2018 /usr/bin/ip link set dev tun0 up mtu 1500

2018-06-29 06:38:32,023 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 /usr/bin/ip addr add dev tun0 10.8.8.68/24 broadcast 10.8.8.255

2018-06-29 06:38:32,025 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 /root/openvpnup.sh tun0 1500 1585 10.8.8.68 255.255.255.0 init

2018-06-29 06:38:32,028 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 /usr/bin/ip route add 207.189.31.109/32 via 172.17.0.1

2018-06-29 06:38:32,029 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 /usr/bin/ip route add 0.0.0.0/1 via 10.8.8.1

2018-06-29 06:38:32,030 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 /usr/bin/ip route add 128.0.0.0/1 via 10.8.8.1

2018-06-29 06:38:32,031 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 Initialization Sequence Completed

2018-06-29 06:38:32,137 DEBG 'deluge-script' stdout output:
[info] Deluge not running
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.8.8.68 different, marking for reconfigure

2018-06-29 06:38:32,138 DEBG 'deluge-script' stdout output:
[info] Attempting to start Deluge...

2018-06-29 06:38:32,258 DEBG 'deluge-script' stdout output:
[info] Deluge listening interface currently defined as 10.8.8.68
[info] Deluge listening interface will be changed to 10.8.8.68
[info] Saving changes to Deluge config file /config/core.conf...

2018-06-29 06:38:32,384 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 207.189.31.109

2018-06-29 06:38:32,384 DEBG 'deluge-script' stdout output:
[info] Deluge started

2018-06-29 06:38:32,670 DEBG 'deluge-web-script' stdout output:
[info] Starting Deluge webui...

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

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

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

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

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

I can't see anything wrong in that log, but you need to post a debug log. Edit the container and set the debug variable to "true", start the container and let it run for a few min. Then post the entire suprervisord.log file (remove username/password. Also, is your unraid server IP 10.10.10.x? Do you have any special characters in your username/password? This container only supports characters 0-9, a-z,A-Z any other characters can cause issues.  

Link to post
1 hour ago, strike said:

I can't see anything wrong in that log, but you need to post a debug log. Edit the container and set the debug variable to "true", start the container and let it run for a few min. Then post the entire suprervisord.log file (remove username/password. Also, is your unraid server IP 10.10.10.x? Do you have any special characters in your username/password? This container only supports characters 0-9, a-z,A-Z any other characters can cause issues.  

Debug log attached. I do use the 10.10.10.x scheme on my network. I changed my password removing the special characters, but still no joy.

supervisord.txt

Link to post
28 minutes ago, Biloxi_1 said:

Debug log attached. I do use the 10.10.10.x scheme on my network. I changed my password removing the special characters, but still no joy.

supervisord.txt

 

And to be clear, you're not reaching the webui at all or do you reach the webui but it's blank? The warning about special characters in your password is gone, but it still complains about your username, you're sure it does not contain any special characters? Everything else seems to be ok.

Link to post
9 minutes ago, strike said:

 

And to be clear, you're not reaching the webui at all or do you reach the webui but it's blank? The warning about special characters in your password is gone, but it still complains about your username, you're sure it does not contain any special characters? Everything else seems to be ok.

I get a timeout. I do have a special character in my username, an "@" because it is an email address. Looking through my options on nord vpn I don't see where I can change it however. It was working fine for months  =/

Link to post
9 minutes ago, Biloxi_1 said:

I get a timeout. I do have a special character in my username, an "@" because it is an email address. Looking through my options on nord vpn I don't see where I can change it however. It was working fine for months  =/

Ok. Early on in your log you were having authentication issues possibly due to the special characters in your password.  It looks fine at the end of the log though (no more authentication issues), but these things with special characters can be unpredictable. It doesn't look like you have to have an e-mail address as your login, you can have a username, but it doesn't say how to change it. If they were offering a trial period you could simply just create a new account and try with another username, but it doesn't look like that they offer that? Maybe you can contact support about changing the login? 

 

Other than that I'm not sure what could be causing the issue. Maybe you can try a different browser if you haven't tried it. And as I mentioned earlier you can try to nuke the docker image and re-download all your containers using CA's previous apps. You don't have to configure anything and you won't lose any settings/data. If you don't know how to do it just ask :) I'm not sure it will have any effect in this case, but you said it has been working for months and then suddenly it stops so it could be worth a try. Recreating the docker image has helped me more than once.

Link to post
12 minutes ago, strike said:

Ok. Early on in your log you were having authentication issues possibly due to the special characters in your password.  It looks fine at the end of the log though (no more authentication issues), but these things with special characters can be unpredictable. It doesn't look like you have to have an e-mail address as your login, you can have a username, but it doesn't say how to change it. If they were offering a trial period you could simply just create a new account and try with another username, but it doesn't look like that they offer that? Maybe you can contact support about changing the login? 

 

Other than that I'm not sure what could be causing the issue. Maybe you can try a different browser if you haven't tried it. And as I mentioned earlier you can try to nuke the docker image and re-download all your containers using CA's previous apps. You don't have to configure anything and you won't lose any settings/data. If you don't know how to do it just ask :) I'm not sure it will have any effect in this case, but you said it has been working for months and then suddenly it stops so it could be worth a try. Recreating the docker image has helped me more than once.

Roger. Thanks for looking at it for me. I will try to email them about the user name , and maybe redo the docker image. I'll post back here if I get it working again.

Link to post
Hi I accidentally screwed up my container by adding a container path and now the container wont show up i unRaid, how can I manually delete this path?
Apps tab, previous apps, hit the download button not the checkbox and then edit out what you did and hit apply

Sent via Tapatalk because I'm either at work or enjoying the summer

Link to post
1 hour ago, Squid said:

Apps tab, previous apps, hit the download button not the checkbox and then edit out what you did and hit apply

Sent via Tapatalk because I'm either at work or enjoying the summer
 

Thanks mate, that did the trick

Link to post

I just got a new username and password from PIA. I changed the two fields in the Docker XML GUI editor (https://TOWER/Docker/UpdateContainer?xmlTemplate=edit:/boot/config/plugins/dockerMan/templates-user/my-binhex-delugevpn.xml), clicked "Save", and noticed it didn't change the 'binhex-delugevpn/openvpn/credentials.conf', so I changed that as well. Going back to that XML I see the new username and password are saved. When I clicked to start the Docker container, I saw in the log "SIGTERM[soft,auth-failure] received, process exiting" and when I `cat credentials.conf` I noticed the old user and password are shown(!) So, it seems somehow the old user and password are still saved somewhere, and each time I start the container (I've tried it 3Xs now) it overwrites the credentials.conf file but leaves the Docker XML alone so the new user/password remains in the Docker XML.

 

Is there anywhere else I should change the user and password?

Link to post
I just got a new username and password from PIA. I changed the two fields in the Docker XML GUI editor (https://TOWER/Docker/UpdateContainer?xmlTemplate=edit:/boot/config/plugins/dockerMan/templates-user/my-binhex-delugevpn.xml), clicked "Save", and noticed it didn't change the 'binhex-delugevpn/openvpn/credentials.conf', so I changed that as well. Going back to that XML I see the new username and password are saved. When I clicked to start the Docker container, I saw in the log "SIGTERM[soft,auth-failure] received, process exiting" and when I `cat credentials.conf` I noticed the old user and password are shown(!) So, it seems somehow the old user and password are still saved somewhere, and each time I start the container (I've tried it 3Xs now) it overwrites the credentials.conf file but leaves the Docker XML alone so the new user/password remains in the Docker XML.

 

Is there anywhere else I should change the user and password?

If by docker XML GUI editor you mean NOT left clicking the icon and selecting edit and changing the cred values then you are doing it wrong.

 

In short you shouldn't be editing the XML directly, use the docker edit option

 

Sent from my SM-G935F using Tapatalk

 

 

 

Link to post

The container doesn't seem to be maintaining the VPN connection for longer than a day or two at a time for me. There's nothing added to the log after the initial "[info] Successfully retrieved external IP address aaa.bbb.ccc.ddd" but Privoxy starts returning a 404 for everything until the container is restarted. It doesn't look like the container was auto-updated overnight.

 

Is there a way to get it to try to reconnect every 10 minutes or so if the VPN drops? At the moment, the VPN seems to just stay down permanently until I manually restart the container.

 

Failing that, as a temporary workaround, does unRAID have a way to schedule regular restarts of a container? That would at least leave everything working most of the time…

Link to post
7 hours ago, binhex said:

If by docker XML GUI editor you mean NOT left clicking the icon and selecting edit and changing the cred values then you are doing it wrong.

@binhex that's what I did to change the username and password. Left click icon -> "Edit" -> change "Key 2" (VPN_USER) and "Key 3" (VPN_PASS) -> "Save". The new username and password are retained there and don't change when I start the container. Each time I try to start the docker container, it immediately changes the binhex-delugevpn/openvpn/credentials.conf file to the old username and password, so of course it returns a can't connect error. Just changing Key 2 and Key 3 doesn't work, so I'm curious where else the user and password are saved? It looks like when the container starts, the 'credentials.conf' file is overwritten with a user/pass saved from somewhere but I can't find where it's pulling that information from.

 

This was before starting the Docker container (at 12:43):

    ls -lh /mnt/cache/appdata/binhex-delugevpn/openvpn/credentials.conf 
    -rwxrwxr-x 1 nobody users 20 Jul  1 02:11 /mnt/cache/appdata/binhex-delugevpn/openvpn/credentials.conf

This was after starting the Docker container (at 12:43):

    ls -lh /mnt/cache/appdata/binhex-delugevpn/openvpn/credentials.conf 
    -rwxrwxr-x 1 nobody users 20 Jul  1 12:43 /mnt/cache/appdata/binhex-delugevpn/openvpn/credentials.conf

 

Attached is the logfile. Before starting, I've also `find /mnt/cache/appdata/binhex-delugevpn -type f -maxdepth 3 -exec grep -H Old_Username {} \;` and only find it listed in the supervisord.log before starting the container, and of course after the container starts and I see the file modified, it shows up in the credentials.conf file.

 

Removing the credentials.conf file and starting the container also generates the credentials.conf file with the old username and password. I'm looking for something simple like `cat FILE_WITH_OLD-USER-PASS.txt > credentials.conf` but don't see anything like it here https://github.com/binhex/arch-delugevpn/search?q=credentials.conf&amp;type=Code

auth-failure.log

Link to post
14 hours ago, AndrewT said:

so I'm curious where else the user and password are saved?

 

there are only two places the credentials are stored:-

 

1. inside the credentials file (if previously run, otherwise it will be blank) /config/openvpn/credentials.conf

2. inside the xml template on your flash drive, location \\<server ip>\flash\config\plugins\dockerMan\templates-user\my-binhex-delugevpn.xml

 

Thats it, there are no other locations, so you could try deleting the credentials file and deleting the xml template from your flash drive, then delete container (and image for good measure) and then pull down and re-configure from scratch, if that doesnt do it then i suspect one or both of the following is the culprit:-

 

1. flash drive is corrupt - fix it up by running chkdsk on a windows machine

2. docker img file is corrupt - stop docker, delete docker img file then re-create docker img file and restore all containers.

Link to post

I never knew the XML files were on the flash drive! I cleaned those up, removing old ones I'll never use again. The new username and password were saved in there as expected.

 

The docker image file was the culprit. OP perfectly explained how to do it, and not too scary even for 16 containers. Seeing all the custom config info saved on the flash drive helped before deleting the img file. Thanks for the help!

 

Link to post
9 hours ago, AndrewT said:

I never knew the XML files were on the flash drive! I cleaned those up, removing old ones I'll never use again. The new username and password were saved in there as expected.

 

The docker image file was the culprit. OP perfectly explained how to do it, and not too scary even for 16 containers. Seeing all the custom config info saved on the flash drive helped before deleting the img file. Thanks for the help!

 

 

Instead of following the advice in that 3 year old post, it is even easier it so just use Community Applications, Previous Apps to get all your dockers reinstalled. Just go to Apps - Previous Apps and you can choose any and all of your previous apps and get them all installed at once.

Link to post

I have installed binhex delugevpn on my reinstalled unraid server.

I used the youtube video of spaceinvader one which was very helpfull.

 

I think i have all the settings right but when I want to open the webUI my browser says error connection refused.

When I turn of the VPN section everything is working. Can somebody help me?

 

Below is my docker configuration and the files in my openvpn folder in appdata/binhex-delugevpn

 

image.thumb.png.ff2457861d11b98963a057aad4e8d6e0.pngimage.png.00d8078ceb8ecf2ee4a8fc20bdcfc2a7.pngimage.png.a0ddf3aa490e8cef9926f6ad9ba7a101.png

Link to post
48 minutes ago, Wouter said:

I think i have all the settings right but when I want to open the webUI my browser says error connection refused.

When I turn of the VPN section everything is working. Can somebody help me?

Have you been through the Newbie VPN Guide here?

 

Link to post
52 minutes ago, Wouter said:

I think i have all the settings right but when I want to open the webUI my browser says error connection refused.

When I turn of the VPN section everything is working. Can somebody help me?

If you are still having issues after reading the newbie vpn section, post the /config/supervisord.log file after censoring your login credentials.

Link to post
19 minutes ago, Wouter said:

I think i did everthing according to the newbie vpn section. Did you mean this file supervisord.log? I can't find login credentials that needs to be censored in it.

Check that the username and password you specified in the docker settings actually work to log in to PIA, also, change to an endpoint that supports port forwarding.

Link to post
27 minutes ago, Wouter said:

I can't find login credentials that needs to be censored in it

It's in the log, so you should change it asap. If you still can't get it to work after doing what @jonathanm said, please edit the container and set the DEBUG variable to "true", delete the supervisord.log, then start the container and let it run a few min before you post a new log

Link to post
5 hours ago, Magic815 said:

Can anyone tell me how to enable 'debug' mode with this docker? I'm having an issue with the BlockList plugin inside Deluge, and I'm being told that step one is to enable 'debug' mode. Thanks!

 

Using blocklist while you're using vpn is pretty useless as @binhex once said:

 

On 10/24/2017 at 6:28 PM, binhex said:

 

yes indeed, most probably that blocklist (which is pretty useless btw) has in its list the sites your trying to use to get your external ip.

 

On 10/24/2017 at 6:38 PM, binhex said:

 

i personally think blocklists are a waste of time, they generally are out of date, and as you're using a vpn there is no point. 

 

the banned by ip filter message is not related to pia btw, this is purely telling you the site you are trying to connect to is in the blocklist, you would get the same message whether you were connected to a vpn provider or not, it makes no difference.

 

https://lime-technology.com/forums/topic/44109-support-binhex-delugevpn/?do=findComment&amp;comment=598299

https://lime-technology.com/forums/topic/44109-support-binhex-delugevpn/?do=findComment&amp;comment=598301

 

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.