Jump to content
binhex

[Support] binhex - DelugeVPN

5819 posts in this topic Last Reply

Recommended Posts

22 hours ago, Gragorg said:

Did you find a solution? Mine stopped downloading yesterday.  I restarted the docker and now I can't even access the web UI.

No, I haven't. They connect and then they time out. Not really sure whats going on.

I also tested rtorrrentVPN and the same thing happens. Or I can't even login to the webui.

Share this post


Link to post

Having a similar issue myself.  The last few days the proxy has been spotty.  I have an internet connection without issue when using it on my PC, but the docker containers say they have no connection through the proxy.  Using ExpressVPN.

Share this post


Link to post

nevermind... my vpn supplier has apparently changed their own supplier, and all configs changed.

 

All is fine again.

Edited by daemon9th

Share this post


Link to post
On 4/19/2019 at 5:19 PM, emteedubs said:

Edit: Narrowed down the issue. For some reason, the error below only happens when running the container on the docker swarm overlay network. When I run it on a docker bridge network, things are fine now. I only wish more containers supported swarm properly. =(

 

I hate to keep asking the same question. But this "write UDP: Operation not permitted (code=1)" error keeps coming back again. I was able to resolve it last time (maybe by luck) by flushing my IPtables on my Ubuntu 18.04 server. It worked for about a week and without me doing much other than maybe turning the containers off and on, it suddenly stopped working again with that error.

 

This time I tried to flush the IPtables, reboot my router, but still no go. I installed a pia-openvpn docker container on the same server as delugevpn to test if it may be a server config issue. But with this other pia-openvpn container, it was able to connect to PIA without this UDP write error using the same credentials. Unfortunately there's nothing more in the log to help me test other ways to figure out the problem. Any thoughts from the experts here? What does that error code really mean?

@emteedubs i know it's been nearly a year since you posted, but did you ever get this setup working with docker swarm? I'm stuck with the same issue, looking for some advise/direction. 

 

I don't feel comfortable with separate openvpn and deluge containers and I want @binhex container on the overlay network so my other services can communicate with it easily.

Share this post


Link to post

i hadn't done any changes for a long time then 2 days ago or so delugeVPN just completely stopped downloading/uploading anything. If i turn VPN off in the template it starts downloading/uploading instantly. and the weird thing is even when VPN is active and DelugeVPN is not downloading anything, the privoxy proxy still works for clients connected to it.

 

My provider is Mullvad and it seems they had an update (to their desktop app from what it looks like) just around that time. that could be related somehow?

 

Any ideas? attached the (hopefully) relevant log

 

edit: Started a new container with the same settings and it works, so something mustve gotten screwed up within the config :/

oh boy here i go troubleshootin again

 

edit2: had to change incoming port for whatever reason... had been running fine for months and then just died, weird.

 

Edited by MammothJerk

Share this post


Link to post

For those of you using PIA and have had their torrents stop working recently, I've found the beta version (2.0.0) of the ltConfig plugin doesn't work with Deluge 2.0.4 which is what the latest docker release is on.

 

Like another user, I created a brand new docker container which allowed my torrents to start working again, but my speeds were slow.  When I compiled and installed the ltConfig plugin in the new container, the torrents stopped working again.

 

At this point if you want PIA working with full speeds, your only bet is to roll the docker container back to Deluge 2.0.3.  You can do this by stopping the container and editing the repository setting to point to the last 2.0.3 release.  The container will automatically rollback to the specified version.  The repository should look like this,

 

binhex/arch-delugevpn:2.0.3_23_g5f1eada3e-1-03

Share this post


Link to post
2 hours ago, raiditup said:

At this point if you want PIA working with full speeds, your only bet is to roll the docker container back to Deluge 2.0.3.

What do you call "full speeds"?  My connection is, at best 100Mbps (nominally 50Mbps), and I am still seeing downloads at up to 8MBps and uploads running at the full limited rate of 6MBps, with v2.0.4.

Share this post


Link to post
29 minutes ago, PeterB said:

What do you call "full speeds"?  My connection is, at best 100Mbps (nominally 50Mbps), and I am still seeing downloads at up to 8MBps and uploads running at the full limited rate of 6MBps, with v2.0.4.

Well that's great for you, but for people like me who see a dramatic decrease in speeds without the custom settings that the ltConfig plugin provides, you should rollback to version 2.0.3.  Without it, I see at most 1MBps down and with it, downloads jump to 35-40MBps so that's what I consider "full speeds".

Share this post


Link to post

I have a question about my current configuration – I’m not having a issue with connectivity and I’m not overly concerned about speed but more hoping for a definitive answer if I have done enough to keep off the radar of my ISP and away from threating letters.  
 

Currently I’m using:

AirVPN for the Docker container

TORGuard for Socks5 proxy

 

Image: https://ibb.co/jw31t7D

 

 

The WebUI parked behind a Reverse Proxy (apache / Lets encrypt)

The Docker container is on a QNAP NAS and sits behind an ASUS RT-AC5300 router.

When I check my configuration with IPLeak It shows that the IP has been obfuscated, I have also checked with TORGuard to verify the IP has been obfuscated and both tests prove positive that the IP is being changed/masked/obfuscated

The only “Error” in the log that is visible when launching the container is:

Image: https://ibb.co/gwRm8h0

 

DEBG 'watchdog-script' stderr output:                                                                       

'ngettext'                                                                                                                          

Traceback (most recent call last):                                                                                                  

  File "/usr/lib/python3.8/site-packages/deluge/i18n/util.py", line 118, in setup_translation                                       

    builtins.__dict__['_n'] = builtins.__dict__['ngettext'] 

KeyError: 'ngettext'      

 

I have tested some small torrents to verify connectivity and all seems to work just fine. I do take a substantial hit on speed with the layers of security but I would rather be safe and slower than unsecure and shutdown.

 

My question is how do I prove that I’m secure enough to use this set up full time without bleeding/leaking and getting into trouble. I am aware this solely depends on the sustained connection of the VPN / Socks5 proxy but hypothetically if there were no fear of the VPN dropping how can I test that this setup is a ready to go to work.

 

Thank you for any comments, help, support and ideas.

 

- Usual-Noob

 

proxy.PNG

delugevpn.PNG

Edited by Usual-Noob
added images

Share this post


Link to post
11 hours ago, Usual-Noob said:

My question is how do I prove that I’m secure enough to use this set up full time without bleeding/leaking and getting into trouble. I am aware this solely depends on the sustained connection of the VPN / Socks5 proxy but hypothetically if there were no fear of the VPN dropping how can I test that this setup is a ready to go to work.

so let me confirm firstly, you are running this docker container with vpn_enabled set to yes right?, and its using airvpn config?, and as well as that you also have set deluge to use a socks5 proxy from TorGuard as a belts and braces type approach, have i got this correct?.

 

 

Share this post


Link to post
29 minutes ago, binhex said:

so let me confirm firstly, you are running this docker container with vpn_enabled set to yes right?, and its using airvpn config?, and as well as that you also have set deluge to use a socks5 proxy from TorGuard as a belts and braces type approach, have i got this correct?.

 

 

Yes sir,

Just trying to add enough to  make sure if something breaks down I'm covered.

I use the Docker with AirVPN enabled and a TorGuard Socks5 Proxy  - you have that correct.

 

-Usual-Noob

Share this post


Link to post
32 minutes ago, Usual-Noob said:

Yes sir,

Just trying to add enough to  make sure if something breaks down I'm covered.

I use the Docker with AirVPN enabled and a TorGuard Socks5 Proxy  - you have that correct.

 

-Usual-Noob

if you want to check for ip leakage the only way is to packet capture using something like tcpdump on the host and then load the capture file in a packet capture analyser, link wireshark and check for any leakage. i have done this myself a few times to ensure zero leakage and can confirm no leakage reported, but feel free to check yourself (sorry no guidance on how to do this you will have to google).

 

for a quick test, docker exec into the running container and kill the openvpn process, this will force the tunnel down, then check speeds drop to 0.

Share this post


Link to post

Whenever I docker exec into the deluge container and enter 'deluge-console' I am getting a lot of errors.

 

 

W607ofl.png

I've checked and /usr/bin/deluge-console doesn't exist. Is it installed in another location? Or am I missing something entirely. The goal is to have ruTorrent execute the deluge-console to add torrents to deluge via autodl-irssi using the following command

 

Command: /usr/bin/deluge-console

Arguments: connect localhost:port ; add -p /path/to/downloads $(TorrentPathName) ; quit

 

Any help is appreciated. Thanks

Share this post


Link to post
On 2/17/2020 at 10:40 AM, vvolfpack said:

vvolfbox-diagnostics-20200217-1058.zip 100.86 kB · 0 downloads

 

Edit 1: After a reboot, the command passes successfully, but I'm unable to start the docker. After clicking "Start". It spins for a second and returns to "Stopped" state. Any help would be much appreciated!

 

 

EDIT 2:

Getting these syslogs from trying to start the application


Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered blocking state
Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered disabled state
Feb 18 23:02:14 vvolfbox kernel: device veth72bc119 entered promiscuous mode
Feb 18 23:02:14 vvolfbox kernel: IPv6: ADDRCONF(NETDEV_UP): veth72bc119: link is not ready
Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered blocking state
Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered forwarding state
Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered disabled state
Feb 18 23:02:14 vvolfbox kernel: eth0: renamed from veth7da683a
Feb 18 23:02:14 vvolfbox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth72bc119: link becomes ready
Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered blocking state
Feb 18 23:02:14 vvolfbox kernel: docker0: port 5(veth72bc119) entered forwarding state
Feb 18 23:02:15 vvolfbox kernel: docker0: port 5(veth72bc119) entered disabled state
Feb 18 23:02:15 vvolfbox kernel: veth7da683a: renamed from eth0
Feb 18 23:02:15 vvolfbox kernel: docker0: port 5(veth72bc119) entered disabled state
Feb 18 23:02:15 vvolfbox kernel: device veth72bc119 left promiscuous mode
Feb 18 23:02:15 vvolfbox kernel: docker0: port 5(veth72bc119) entered disabled state

Any help would be much appreciated, @binhex!

Unfortunately, I'm still unable to start my docker in spite of multiple attempts to delete the app data and starting afresh. I've tried all troubleshooting steps. Would appreciate any help here!

Share this post


Link to post

Anybody get this working with Privado? I was using UsernetServer and they forced me to switch to Privado and it's no longer working. I'm using their configs from here.

 

I keep getting this in the logs:

2020-02-27 01:06:00,863 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

Before that, I get:

 

deluge        | Thu Feb 27 01:19:25 2020 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 198.18.0.1,dhcp-option DNS 198.18.0.2,rcvbuf 493216,sndbuf 493216,explicit-exit-notify 5,comp-lzo no,route-gateway 172.21.32.1,topology subnet,ping 20,ping-restart 40,ifconfig 172.21.39.33 255.255.254.0,peer-id 4,cipher AES-256-GCM'
deluge        |
deluge        | 2020-02-27 01:19:25,071 DEBG 'start-script' stdout output:
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: timers and/or timeouts modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: explicit notify parm(s) modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: compression parms modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
deluge        | Thu Feb 27 01:19:25 2020 Socket Buffers: R=[212992->425984] S=[212992->425984]
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: --ifconfig/up options modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: route options modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: route-related options modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: peer-id set
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: adjusting link_mtu to 1624
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: data channel crypto options modified
deluge        | Thu Feb 27 01:19:25 2020 Data Channel: using negotiated cipher 'AES-256-GCM'
deluge        | Thu Feb 27 01:19:25 2020 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
deluge        | Thu Feb 27 01:19:25 2020 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
deluge        | Thu Feb 27 01:19:25 2020 ROUTE_GATEWAY 172.18.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:12:00:0a
deluge        | Thu Feb 27 01:19:25 2020 TUN/TAP device tun0 opened
deluge        | Thu Feb 27 01:19:25 2020 TUN/TAP TX queue length set to 100
deluge        | Thu Feb 27 01:19:25 2020 /usr/bin/ip link set dev tun0 up mtu 1500
deluge        | Thu Feb 27 01:19:25 2020 /usr/bin/ip addr add dev tun0 172.21.39.33/23 broadcast 172.21.39.255
deluge        | Thu Feb 27 01:19:25 2020 /root/openvpnup.sh tun0 1500 1552 172.21.39.33 255.255.254.0 init
deluge        | Thu Feb 27 01:19:25 2020 /usr/bin/ip route add 45.152.182.227/32 via 172.18.0.1
deluge        | Thu Feb 27 01:19:25 2020 /usr/bin/ip route add 0.0.0.0/1 via 172.21.32.1
deluge        |
deluge        | 2020-02-27 01:19:25,073 DEBG 'start-script' stdout output:
deluge        | Error: Nexthop has invalid gateway.
deluge        | Thu Feb 27 01:19:25 2020 ERROR: Linux route add command failed: external program exited with error status: 2
deluge        | Thu Feb 27 01:19:25 2020 /usr/bin/ip route add 128.0.0.0/1 via 172.21.32.1
deluge        |
deluge        | 2020-02-27 01:19:25,076 DEBG 'start-script' stdout output:
deluge        | Error: Nexthop has invalid gateway.
deluge        |
deluge        | 2020-02-27 01:19:25,079 DEBG 'start-script' stdout output:
deluge        | Thu Feb 27 01:19:25 2020 ERROR: Linux route add command failed: external program exited with error status: 2
deluge        | Thu Feb 27 01:19:25 2020 Initialization Sequence Completed
deluge        | 
deluge        | 2020-02-27 01:19:25,195 DEBG 'start-script' stdout output:
deluge        | [info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

Any idea what could be breaking this?

Share this post


Link to post
13 hours ago, syndac said:

Anybody get this working with Privado? I was using UsernetServer and they forced me to switch to Privado and it's no longer working. I'm using their configs from here.

 

I keep getting this in the logs:


2020-02-27 01:06:00,863 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

Before that, I get:

 


deluge        | Thu Feb 27 01:19:25 2020 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 198.18.0.1,dhcp-option DNS 198.18.0.2,rcvbuf 493216,sndbuf 493216,explicit-exit-notify 5,comp-lzo no,route-gateway 172.21.32.1,topology subnet,ping 20,ping-restart 40,ifconfig 172.21.39.33 255.255.254.0,peer-id 4,cipher AES-256-GCM'
deluge        |
deluge        | 2020-02-27 01:19:25,071 DEBG 'start-script' stdout output:
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: timers and/or timeouts modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: explicit notify parm(s) modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: compression parms modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
deluge        | Thu Feb 27 01:19:25 2020 Socket Buffers: R=[212992->425984] S=[212992->425984]
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: --ifconfig/up options modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: route options modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: route-related options modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: peer-id set
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: adjusting link_mtu to 1624
deluge        | Thu Feb 27 01:19:25 2020 OPTIONS IMPORT: data channel crypto options modified
deluge        | Thu Feb 27 01:19:25 2020 Data Channel: using negotiated cipher 'AES-256-GCM'
deluge        | Thu Feb 27 01:19:25 2020 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
deluge        | Thu Feb 27 01:19:25 2020 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
deluge        | Thu Feb 27 01:19:25 2020 ROUTE_GATEWAY 172.18.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:12:00:0a
deluge        | Thu Feb 27 01:19:25 2020 TUN/TAP device tun0 opened
deluge        | Thu Feb 27 01:19:25 2020 TUN/TAP TX queue length set to 100
deluge        | Thu Feb 27 01:19:25 2020 /usr/bin/ip link set dev tun0 up mtu 1500
deluge        | Thu Feb 27 01:19:25 2020 /usr/bin/ip addr add dev tun0 172.21.39.33/23 broadcast 172.21.39.255
deluge        | Thu Feb 27 01:19:25 2020 /root/openvpnup.sh tun0 1500 1552 172.21.39.33 255.255.254.0 init
deluge        | Thu Feb 27 01:19:25 2020 /usr/bin/ip route add 45.152.182.227/32 via 172.18.0.1
deluge        | Thu Feb 27 01:19:25 2020 /usr/bin/ip route add 0.0.0.0/1 via 172.21.32.1
deluge        |
deluge        | 2020-02-27 01:19:25,073 DEBG 'start-script' stdout output:
deluge        | Error: Nexthop has invalid gateway.
deluge        | Thu Feb 27 01:19:25 2020 ERROR: Linux route add command failed: external program exited with error status: 2
deluge        | Thu Feb 27 01:19:25 2020 /usr/bin/ip route add 128.0.0.0/1 via 172.21.32.1
deluge        |
deluge        | 2020-02-27 01:19:25,076 DEBG 'start-script' stdout output:
deluge        | Error: Nexthop has invalid gateway.
deluge        |
deluge        | 2020-02-27 01:19:25,079 DEBG 'start-script' stdout output:
deluge        | Thu Feb 27 01:19:25 2020 ERROR: Linux route add command failed: external program exited with error status: 2
deluge        | Thu Feb 27 01:19:25 2020 Initialization Sequence Completed
deluge        | 
deluge        | 2020-02-27 01:19:25,195 DEBG 'start-script' stdout output:
deluge        | [info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

Any idea what could be breaking this?

 

Im also getting this (if the docker is restarted). The only way Ive been able to fix it is to recreate the docker each time.

 

I was originally using Newshosting but they are now also Privado

 

Share this post


Link to post

@Turrican Please let me know if you find a solution. I'll do the same, although recreating the image and container isn't working for me.

Share this post


Link to post
On 2/26/2020 at 1:24 PM, noraa said:

Whenever I docker exec into the deluge container and enter 'deluge-console' I am getting a lot of errors.

 

 

W607ofl.png

I've checked and /usr/bin/deluge-console doesn't exist. Is it installed in another location? Or am I missing something entirely. The goal is to have ruTorrent execute the deluge-console to add torrents to deluge via autodl-irssi using the following command

 

Command: /usr/bin/deluge-console

Arguments: connect localhost:port ; add -p /path/to/downloads $(TorrentPathName) ; quit

 

Any help is appreciated. Thanks

Sorry for the bump was just wondering if anyone might know what is causing this issue. Any help is appreciated. Thank you.

Share this post


Link to post
23 hours ago, Turrican said:

 

Im also getting this (if the docker is restarted). The only way Ive been able to fix it is to recreate the docker each time.

 

I was originally using Newshosting but they are now also Privado

 

Also getting: [debug] Having issues resolving name 'www.google.com', sleeping before retry...  in my logs since a few days.

When rebooting docker, it won't start anymore.

I'm using Torguard as VPN so I don't think it has anything to do with Privado.

 

Recreating the containers doesn't solve the problem either.

I suppose it had something to to with the update from 5 days ago.

Edited by Kopernikus

Share this post


Link to post
43 minutes ago, Kopernikus said:

Also getting: [debug] Having issues resolving name 'www.google.com', sleeping before retry...  in my logs since a few days.

When rebooting docker, it won't start anymore.

I'm using Torguard as VPN so I don't think it has anything to do with Privado.

 

Recreating the containers doesn't solve the problem either.

I suppose it had something to to with the update from 5 days ago.

Found the problem.

I was using Torguard public DNS as DNS server in the docker config, apparently Torguard changed it without warning.

After replace the old DNS with the new, all is working fine again, maybe same issue with Privado?

Share this post


Link to post
1 hour ago, Kopernikus said:

Found the problem.

I was using Torguard public DNS as DNS server in the docker config, apparently Torguard changed it without warning.

After replace the old DNS with the new, all is working fine again, maybe same issue with Privado?

What in your config, exactly, did you change? I changed the NS Servers in the Deluge environment variables to the one from the docs: 

 

Quote

209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

I then deleted both the binhex/deluge container and image and I still run into this error. Am I missing something?

Share this post


Link to post

Another Privado user here with issues. Here my log (sorry for just dumping it, not sure which bits are relevant):

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

2020-02-29 11:47:44.657071 [info] System information Linux 8d18dbc6a457 4.19.98-Unraid #1 SMP Sun Jan 26 09:15:03 PST 2020 x86_64 GNU/Linux
2020-02-29 11:47:44.679096 [info] PUID defined as '99'
2020-02-29 11:47:44.703412 [info] PGID defined as '100'
2020-02-29 11:47:44.759130 [info] UMASK defined as '000'
2020-02-29 11:47:44.780753 [info] Permissions already set for volume mappings
2020-02-29 11:47:44.804733 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2020-02-29 11:47:44.826051 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2020-02-29 11:47:44.847646 [info] VPN_ENABLED defined as 'yes'
2020-02-29 11:47:44.873887 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/den-a02.ovpn
2020-02-29 11:47:44.914337 [info] VPN remote line defined as 'remote den-a02.wlvpn.com 1194'
2020-02-29 11:47:44.935850 [info] VPN_REMOTE defined as 'den-a02.wlvpn.com'
2020-02-29 11:47:44.957671 [info] VPN_PORT defined as '1194'
2020-02-29 11:47:44.982149 [info] VPN_PROTOCOL defined as 'udp'
2020-02-29 11:47:45.003633 [info] VPN_DEVICE_TYPE defined as 'tun0'
2020-02-29 11:47:45.025082 [info] VPN_PROV defined as 'custom'
2020-02-29 11:47:45.046365 [info] LAN_NETWORK defined as '192.168.0.0/24'
2020-02-29 11:47:45.068031 [info] NAME_SERVERS defined as '9.9.9.9, 149.112.112.112, 208.67.222.222, 208.67.220.220'
2020-02-29 11:47:45.089495 [info] VPN_USER defined as [Removed]
2020-02-29 11:47:45.110903 [info] VPN_PASS defined as [Removed]
2020-02-29 11:47:45.132416 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2020-02-29 11:47:45.154436 [info] ENABLE_PRIVOXY defined as 'yes'
2020-02-29 11:47:45.178467 [info] Deleting files in /tmp (non recursive)...
2020-02-29 11:47:45.198790 [info] Starting Supervisor...
2020-02-29 11:47:45,329 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2020-02-29 11:47:45,329 INFO Set uid to user 0 succeeded
2020-02-29 11:47:45,331 INFO supervisord started with pid 6
2020-02-29 11:47:46,333 INFO spawned: 'start-script' with pid 156
2020-02-29 11:47:46,334 INFO spawned: 'watchdog-script' with pid 157
2020-02-29 11:47:46,334 INFO reaped unknown pid 7
2020-02-29 11:47:46,338 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN
[debug] Environment variables defined as follows
APPLICATION=deluge
BASH=/bin/bash
BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath
BASH_ALIASES=()
BASH_ARGC=()
BASH_ARGV=()
BASH_CMDS=()
BASH_LINENO=([0]="0")
BASH_SOURCE=([0]="/root/start.sh")
BASH_VERSINFO=([0]="5" [1]="0" [2]="16" [3]="1" [4]="release" [5]="x86_64-pc-linux-gnu")
BASH_VERSION='5.0.16(1)-release'
DEBUG=true
DELUGE_DAEMON_LOG_LEVEL=info
DELUGE_WEB_LOG_LEVEL=info
DIRSTACK=()
ENABLE_PRIVOXY=yes
EUID=0
GROUPS=()
HOME=/home/nobody
HOSTNAME=8d18dbc6a457
HOSTTYPE=x86_64

2020-02-29 11:47:46,339 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-02-29 11:47:46,339 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-02-29 11:47:46,339 DEBG 'start-script' stdout output:
HOST_OS=Unraid
IFS=$' \t\n'
LANG=en_GB.UTF-8
LAN_NETWORK=192.168.0.0/24
MACHTYPE=x86_64-pc-linux-gnu
NAME_SERVERS='9.9.9.9, 149.112.112.112, 208.67.222.222, 208.67.220.220'
OPTERR=1
OPTIND=1
OSTYPE=linux-gnu
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PGID=100
PIPESTATUS=([0]="0")
PPID=6
PS4='+ '
PUID=99
PWD=/
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:interactive-comments
SHLVL=1
STRICT_PORT_FORWARD=yes
SUPERVISOR_ENABLED=1
SUPERVISOR_GROUP_NAME=start-script
SUPERVISOR_PROCESS_NAME=start-script
TERM=xterm
TZ=Europe/London
UID=0
UMASK=000
VPN_CONFIG=/config/openvpn/den-a02.ovpn
VPN_DEVICE_TYPE=tun0
VPN_ENABLED=yes
VPN_OPTIONS=
VPN_PASS=[Removed]
VPN_PORT=1194
VPN_PROTOCOL=udp
VPN_PROV=custom
VPN_REMOTE=den-a02.wlvpn.com
VPN_USER=[Removed]
_='[debug] Environment variables defined as follows'
[debug] Directory listing of files in /config/openvpn as follows

2020-02-29 11:47:46,341 DEBG 'start-script' stdout output:
total 20
drwxrwxr-x 1 nobody users  152 Feb 29 11:47 .
drwxrwxr-x 1 nobody users  618 Feb 29 11:47 ..
-rwxrwxr-x 1 nobody users 1798 Feb 28 21:49 ams-a02.ovpn.bak
-rwxrwxr-x 1 nobody users 1793 Feb 28 16:30 cph-c09.ovpn.bak
-rwxrwxr-x 1 nobody users   34 Feb 29 11:40 credentials.conf
-rwxrwxr-x 1 nobody users 1798 Feb 29 11:47 den-a02.ovpn
-rwxrwxr-x 1 nobody users 1793 Feb 28 16:30 hel-c02.ovpn.bak

2020-02-29 11:47:46,349 DEBG 'start-script' stdout output:
[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

2020-02-29 11:47:46,375 DEBG 'start-script' stdout output:
[debug] Contents of ovpn file /config/openvpn/den-a02.ovpn as follows...

2020-02-29 11:47:46,375 DEBG 'start-script' stdout output:
remote den-a02.wlvpn.com 1194
client
dev tun
proto udp
resolv-retry infinite
nobind
persist-key
persist-remote-ip
#ca vpn.crt

tls-client
remote-cert-tls server
auth-user-pass credentials.conf
comp-lzo
verb 3

auth SHA256
cipher AES-256-CBC

<ca>
-----BEGIN CERTIFICATE-----
[Removed]
-----END CERTIFICATE-----
</ca>

2020-02-29 11:47:46,384 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2020-02-29 11:47:46,386 DEBG 'start-script' stdout output:
[info] Adding 9.9.9.9 to /etc/resolv.conf

2020-02-29 11:47:46,389 DEBG 'start-script' stdout output:
[info] Adding 149.112.112.112 to /etc/resolv.conf

2020-02-29 11:47:46,391 DEBG 'start-script' stdout output:
[info] Adding 208.67.222.222 to /etc/resolv.conf

2020-02-29 11:47:46,394 DEBG 'start-script' stdout output:
[info] Adding 208.67.220.220 to /etc/resolv.conf

2020-02-29 11:47:46,456 DEBG 'start-script' stdout output:
[debug] Show name servers defined for container

2020-02-29 11:47:46,457 DEBG 'start-script' stdout output:
nameserver 9.9.9.9
nameserver 149.112.112.112
nameserver 208.67.222.222
nameserver 208.67.220.220

2020-02-29 11:47:46,457 DEBG 'start-script' stdout output:
[debug] Show name resolution for VPN endpoint den-a02.wlvpn.com

2020-02-29 11:47:46,472 DEBG 'start-script' stdout output:
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 17761
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; den-a02.wlvpn.com.	IN	A

;; ANSWER SECTION:
den-a02.wlvpn.com.	900	IN	A	64.145.93.7

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 13 msec
;; SERVER: 208.67.222.222
;; WHEN: Sat Feb 29 11:47:46 2020
;; MSG SIZE  rcvd: 51

2020-02-29 11:47:46,472 DEBG 'start-script' stdout output:
[debug] Show contents of hosts file

2020-02-29 11:47:46,473 DEBG 'start-script' stdout output:
127.0.0.1	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
172.17.0.2	8d18dbc6a457
64.145.93.7	den-a02.wlvpn.com

2020-02-29 11:47:46,476 DEBG 'start-script' stdout output:
[debug] Docker interface defined as eth0

2020-02-29 11:47:46,478 DEBG 'start-script' stdout output:
[debug] Docker IP defined as 172.17.0.2

2020-02-29 11:47:46,481 DEBG 'start-script' stdout output:
[debug] Docker netmask defined as 255.255.0.0

2020-02-29 11:47:46,486 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2020-02-29 11:47:46,489 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.0/24 as route via docker eth0

2020-02-29 11:47:46,490 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-02-29 11:47:46,491 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0 
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2 
192.168.0.0/24 via 172.17.0.1 dev eth0 

2020-02-29 11:47:46,491 DEBG 'start-script' stdout output:
--------------------
[debug] Modules currently loaded for kernel

2020-02-29 11:47:46,493 DEBG 'start-script' stdout output:
Module                  Size  Used by
xt_CHECKSUM            16384  1
ipt_REJECT             16384  2
xt_nat                 16384  13
ip6table_mangle        16384  1
ip6table_nat           16384  1
nf_nat_ipv6            16384  1 ip6table_nat
iptable_mangle         16384  1
ip6table_filter        16384  1
ip6_tables             24576  3 ip6table_filter,ip6table_nat,ip6table_mangle
vhost_net              24576  0
tun                    36864  2 vhost_net
vhost                  32768  1 vhost_net
tap                    20480  1 vhost_net
veth                   20480  0
ipt_MASQUERADE         16384  17
iptable_filter         16384  1
iptable_nat            16384  1
nf_nat_ipv4            16384  2 ipt_MASQUERADE,iptable_nat
nf_nat                 24576  3 nf_nat_ipv6,nf_nat_ipv4,xt_nat
ip_tables              24576  3 iptable_filter,iptable_nat,iptable_mangle
xfs                   663552  1
md_mod                 49152  1
bonding               110592  0
e1000e                180224  0
r8169                  69632  0
realtek                20480  0
x86_pkg_temp_thermal    16384  0
intel_powerclamp       16384  0
coretemp               16384  0
kvm_intel             196608  0
kvm                   380928  1 kvm_intel
crct10dif_pclmul       16384  0
crc32_pclmul           16384  0
crc32c_intel           24576  0
ghash_clmulni_intel    16384  0
pcbc                   16384  0
aesni_intel           200704  0
aes_x86_64             20480  1 aesni_intel
crypto_simd            16384  1 aesni_intel
cryptd                 20480  3 crypto_simd,ghash_clmulni_intel,aesni_intel
glue_helper            16384  1 aesni_intel
ahci                   40960  3
i2c_i801               24576  0
intel_cstate           16384  0
libahci                28672  1 ahci
intel_uncore          102400  0
i2c_core               40960  1 i2c_i801
intel_rapl_perf        16384  0
video                  40960  0
backlight              16384  1 video
pcc_cpufreq            16384  0
thermal                20480  0
button                 16384  0
fan                    16384  0

2020-02-29 11:47:46,495 DEBG 'start-script' stdout output:
iptable_mangle         16384  1
ip_tables              24576  3 iptable_filter,iptable_nat,iptable_mangle

2020-02-29 11:47:46,495 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2020-02-29 11:47:46,523 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-02-29 11:47:46,524 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 1194 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A 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 1194 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.0.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2020-02-29 11:47:46,525 DEBG 'start-script' stdout output:
--------------------

2020-02-29 11:47:46,526 DEBG 'start-script' stdout output:
[debug] OpenVPN command line:- /usr/bin/openvpn --daemon --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV 'custom' --setenv DEBUG 'true' --setenv VPN_DEVICE_TYPE 'tun0' --setenv VPN_ENABLED 'yes' --setenv VPN_REMOTE 'den-a02.wlvpn.com' --setenv APPLICATION 'deluge' --script-security 2 --writepid /root/openvpn.pid --remap-usr1 SIGHUP --log-append /dev/stdout --pull-filter ignore 'up' --pull-filter ignore 'down' --pull-filter ignore 'route-ipv6' --pull-filter ignore 'ifconfig-ipv6' --pull-filter ignore 'tun-ipv6' --pull-filter ignore 'persist-tun' --pull-filter ignore 'reneg-sec' --up /root/openvpnup.sh --up-delay --up-restart --remote 64.145.93.7 1194 udp --remote-random --keepalive 10 60 --auth-user-pass credentials.conf --cd /config/openvpn --config '/config/openvpn/den-a02.ovpn'
[info] Starting OpenVPN...

2020-02-29 11:47:46,530 DEBG 'start-script' stdout output:
Sat Feb 29 11:47:46 2020 WARNING: file 'credentials.conf' is group or others accessible
Sat Feb 29 11:47:46 2020 OpenVPN 2.4.8 [git:makepkg/3976acda9bf10b5e+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jan  3 2020
Sat Feb 29 11:47:46 2020 library versions: OpenSSL 1.1.1d  10 Sep 2019, LZO 2.10

2020-02-29 11:47:46,531 DEBG 'start-script' stdout output:
[info] OpenVPN started
Sat Feb 29 11:47:46 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-02-29 11:47:46,532 DEBG 'start-script' stdout output:
Sat Feb 29 11:47:46 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]64.145.93.7:1194
Sat Feb 29 11:47:46 2020 Socket Buffers: R=[212992->212992] S=[212992->212992]
Sat Feb 29 11:47:46 2020 UDP link local: (not bound)
Sat Feb 29 11:47:46 2020 UDP link remote: [AF_INET]64.145.93.7:1194

2020-02-29 11:47:46,658 DEBG 'start-script' stdout output:
Sat Feb 29 11:47:46 2020 TLS: Initial packet from [AF_INET]64.145.93.7:1194, sid=6de6abe3 3d98d08d

2020-02-29 11:47:46,786 DEBG 'start-script' stdout output:
Sat Feb 29 11:47:46 2020 VERIFY OK: depth=1, C=US, ST=VPN, L=VPN, O=VPN, OU=VPN, CN=VPN, name=VPN, emailAddress=VPN

2020-02-29 11:47:46,786 DEBG 'start-script' stdout output:
Sat Feb 29 11:47:46 2020 VERIFY KU OK
Sat Feb 29 11:47:46 2020 Validating certificate extended key usage
Sat Feb 29 11:47:46 2020 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Sat Feb 29 11:47:46 2020 VERIFY EKU OK
Sat Feb 29 11:47:46 2020 VERIFY OK: depth=0, C=US, ST=VPN, L=VPN, O=VPN, OU=VPN, CN=vpn, name=VPN

2020-02-29 11:47:48,077 DEBG 'start-script' stdout output:
Sat Feb 29 11:47:48 2020 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Sat Feb 29 11:47:48 2020 [vpn] Peer Connection Initiated with [AF_INET]64.145.93.7:1194

2020-02-29 11:47:49,353 DEBG 'start-script' stdout output:
Sat Feb 29 11:47:49 2020 SENT CONTROL [vpn]: 'PUSH_REQUEST' (status=1)

2020-02-29 11:47:49,477 DEBG 'start-script' stdout output:
Sat Feb 29 11:47:49 2020 AUTH: Received control message: AUTH_FAILED

2020-02-29 11:47:49,477 DEBG 'start-script' stdout output:
Sat Feb 29 11:47:49 2020 SIGTERM[soft,auth-failure] received, process exiting

2020-02-29 11:48:16,537 DEBG 'start-script' stdout output:
[warn] OpenVPN process terminated, restarting OpenVPN...

2020-02-29 11:48:16,542 DEBG 'start-script' stdout output:
Sat Feb 29 11:48:16 2020 WARNING: file 'credentials.conf' is group or others accessible
Sat Feb 29 11:48:16 2020 OpenVPN 2.4.8 [git:makepkg/3976acda9bf10b5e+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jan  3 2020
Sat Feb 29 11:48:16 2020 library versions: OpenSSL 1.1.1d  10 Sep 2019, LZO 2.10

2020-02-29 11:48:16,543 DEBG 'start-script' stdout output:
[info] OpenVPN restarted
Sat Feb 29 11:48:16 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-02-29 11:48:16,544 DEBG 'start-script' stdout output:
Sat Feb 29 11:48:16 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]64.145.93.7:1194
Sat Feb 29 11:48:16 2020 Socket Buffers: R=[212992->212992] S=[212992->212992]
Sat Feb 29 11:48:16 2020 UDP link local: (not bound)
Sat Feb 29 11:48:16 2020 UDP link remote: [AF_INET]64.145.93.7:1194

2020-02-29 11:48:16,668 DEBG 'start-script' stdout output:
Sat Feb 29 11:48:16 2020 TLS: Initial packet from [AF_INET]64.145.93.7:1194, sid=5c3fd1ab 6de7e4ea

2020-02-29 11:48:16,795 DEBG 'start-script' stdout output:
Sat Feb 29 11:48:16 2020 VERIFY OK: depth=1, C=US, ST=VPN, L=VPN, O=VPN, OU=VPN, CN=VPN, name=VPN, emailAddress=VPN

2020-02-29 11:48:16,796 DEBG 'start-script' stdout output:
Sat Feb 29 11:48:16 2020 VERIFY KU OK
Sat Feb 29 11:48:16 2020 Validating certificate extended key usage
Sat Feb 29 11:48:16 2020 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Sat Feb 29 11:48:16 2020 VERIFY EKU OK
Sat Feb 29 11:48:16 2020 VERIFY OK: depth=0, C=US, ST=VPN, L=VPN, O=VPN, OU=VPN, CN=vpn, name=VPN

2020-02-29 11:48:18,085 DEBG 'start-script' stdout output:
Sat Feb 29 11:48:18 2020 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Sat Feb 29 11:48:18 2020 [vpn] Peer Connection Initiated with [AF_INET]64.145.93.7:1194

2020-02-29 11:48:19,322 DEBG 'start-script' stdout output:
Sat Feb 29 11:48:19 2020 SENT CONTROL [vpn]: 'PUSH_REQUEST' (status=1)

2020-02-29 11:48:19,446 DEBG 'start-script' stdout output:
Sat Feb 29 11:48:19 2020 AUTH: Received control message: AUTH_FAILED

2020-02-29 11:48:19,446 DEBG 'start-script' stdout output:
Sat Feb 29 11:48:19 2020 SIGTERM[soft,auth-failure] received, process exiting

I used to use Newshosting's (Usenet) own VPN but they've switched to Privado, that said I have had it up and running for a week or so just fine. It seems to have broken in the last couple of days.

 

Quote

[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

I tried changing my password but they generate it for you and always seem to have special characters in them. Having had it up and running without problems before, I would assume that special characters aren't the problem.

 

Any help appreciated. Thanks.

Share this post


Link to post

I am still having issues with PIA. I even deleted the app folders and started over again with this and the rtorrentvpn.

My PIA subscription is up this month. Not sure what service to move to.

Share this post


Link to post

Hi,

I am also having issues setting this up with Privado (to be fair i've not tried with anyone else). I Cannot open the browser website

 

i am getting this snippet

2020-03-01 11:22:33,111 DEBG 'start-script' stdout output:
Sun Mar 1 11:22:33 2020 /usr/bin/ip addr add dev tun0 172.21.43.178/23 broadcast 172.21.43.255

2020-03-01 11:22:33,112 DEBG 'start-script' stdout output:
Sun Mar 1 11:22:33 2020 /root/openvpnup.sh tun0 1500 1552 172.21.43.178 255.255.254.0 init

2020-03-01 11:22:33,114 DEBG 'start-script' stdout output:
Sun Mar 1 11:22:33 2020 /usr/bin/ip route add 91.148.224.10/32 via 172.17.0.1

2020-03-01 11:22:33,116 DEBG 'start-script' stdout output:
Sun Mar 1 11:22:33 2020 /usr/bin/ip route add 0.0.0.0/1 via 172.21.34.1

2020-03-01 11:22:33,116 DEBG 'start-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2020-03-01 11:22:33,117 DEBG 'start-script' stdout output:
Error: Nexthop has invalid gateway.


2020-03-01 11:22:33,117 DEBG 'start-script' stdout output:
Sun Mar 1 11:22:33 2020 ERROR: Linux route add command failed: external program exited with error status: 2

Sun Mar 1 11:22:33 2020 /usr/bin/ip route add 128.0.0.0/1 via 172.21.34.1

2020-03-01 11:22:33,118 DEBG 'start-script' stdout output:
Error: Nexthop has invalid gateway.


2020-03-01 11:22:33,118 DEBG 'start-script' stdout output:
Sun Mar 1 11:22:33 2020 ERROR: Linux route add command failed: external program exited with error status: 2

Sun Mar 1 11:22:33 2020 Initialization Sequence Completed

2020-03-01 11:22:33,232 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '172.21.43.178'

2020-03-01 11:22:33,232 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2020-03-01 11:22:33,233 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2020-03-01 11:22:33,237 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

2020-03-01 11:22:38,241 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

and so on...

 

Can anyone point me to anything obvious. I have read a lot of these 200+ pages but not all 

 

Thanks

 

i attached more complete logs.

binhex-delugevpn.rtf

Share this post


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.