[Support] binhex - DelugeVPN


Recommended Posts

1 minute ago, wgstarks said:

Yes. Just cd to the proper directory and type mc to launch.

Just tried. according to this the username is "localclient" but when I've tried to used that in the past it's said the username doesn't exist. The password is something ridiculously long, will give these details a go and see what happens

Link to comment
On 10/8/2020 at 12:50 PM, binhex said:

guinea pig time again - wireguard support now in, if you are interested then see here:-

https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=433617

 

testing is now over, looks like its solid enough for me to release as latest, images now built for all VPN images i produce, please remove tag ':test' from the repository to pull down 'latest' again and 'force update' to ensure it is the latest image thats on disk.

 

If you wish to switch from openvpn to wireguard then please see Q21 from the following link:-

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

  • Like 2
Link to comment
10 hours ago, binhex said:

Np, it's fixed in the next release which should be out very soon.

Sent from my CLT-L09 using Tapatalk
 

So that fixed one part of my issue it looks like, but after coming back after a few hours, it looked like the docker was not connecting out. 

 

I did a ping on google.com and received a temporary domain name resolution failure notice. 

 

Any Ideas?  

Link to comment

Howzit!? I can't seem to access the webgui after installing the container. Here are some of the logs I pulled:

2020-10-10 16:21:23,188 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:23 2020 WARNING: file 'credentials.conf' is group or others accessible

2020-10-10 16:21:23,188 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:23 2020 OpenVPN 2.4.9 [git:makepkg/9b0dafca6c50b8bb+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 20 2020
Sat Oct 10 16:21:23 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10

2020-10-10 16:21:23,188 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:23 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-10-10 16:21:23,190 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:23 2020 CRL: loaded 1 CRLs from file [[INLINE]]

2020-10-10 16:21:23,190 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:23 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]172.98.89.194:1198
Sat Oct 10 16:21:23 2020 UDP link local: (not bound)
Sat Oct 10 16:21:23 2020 UDP link remote: [AF_INET]172.98.89.194:1198

2020-10-10 16:21:23,546 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:23 2020 [c83b3105a09648051d5988250060766f] Peer Connection Initiated with [AF_INET]172.98.89.194:1198

2020-10-10 16:21:24,791 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:24 2020 TUN/TAP device tun0 opened
Sat Oct 10 16:21:24 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-10-10 16:21:24,792 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:24 2020 /usr/bin/ip addr add dev tun0 local 10.92.17.10 peer 10.92.17.9

2020-10-10 16:21:24,793 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:24 2020 /root/openvpnup.sh tun0 1500 1558 10.92.17.10 10.92.17.9 init

2020-10-10 16:21:24,797 DEBG 'start-script' stdout output:
[debug] Waiting for valid local and gateway IP addresses from tunnel...

2020-10-10 16:21:24,799 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:24 2020 Initialization Sequence Completed

2020-10-10 16:21:25,812 DEBG 'start-script' stdout output:
[debug] Valid local IP address from tunnel acquired '10.92.17.10'

2020-10-10 16:21:26,829 DEBG 'start-script' stdout output:
[debug] Valid gateway IP address from tunnel acquired '10.92.17.9'

2020-10-10 16:21:26,829 DEBG 'start-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2020-10-10 16:21:26,914 DEBG 'start-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.14.196'

2020-10-10 16:21:26,915 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using Name Server 'ns1.google.com'...

2020-10-10 16:21:27,524 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 172.98.89.194

2020-10-10 16:21:27,526 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port

2020-10-10 16:21:27,526 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-vancouver.privateinternetaccess.com' is port forward enabled...

2020-10-10 16:21:28,086 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-vancouver.privateinternetaccess.com' is in the list of endpoints that support port forwarding

2020-10-10 16:21:28,086 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2020-10-10 16:21:28,258 DEBG 'start-script' stdout output:
[warn] Unable to download json for dynamically assigned port, exiting script...
[info] Port forwarding failure, creating file '/tmp/portfailure' to indicate failure...

2020-10-10 16:21:28,259 DEBG 'start-script' stdout output:
[info] Script finished to assign incoming port

2020-10-10 16:21:28,086 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-vancouver.privateinternetaccess.com' is in the list of endpoints that support port forwarding

2020-10-10 16:21:28,086 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
[info] Attempting to get dynamically assigned port...

2020-10-10 16:21:28,258 DEBG 'start-script' stdout output:
[warn] Unable to download json for dynamically assigned port, exiting script...
[info] Port forwarding failure, creating file '/tmp/portfailure' to indicate failure...

2020-10-10 16:21:28,259 DEBG 'start-script' stdout output:
[info] Script finished to assign incoming port

2020-10-10 16:21:53,157 DEBG 'start-script' stdout output:
[info] Sending SIGTERM (-15) to 'openvpn' due to incoming port allocation failure...

2020-10-10 16:21:53,161 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:53 2020 event_wait : Interrupted system call (code=4)

2020-10-10 16:21:53,165 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:53 2020 /usr/bin/ip addr del dev tun0 local 10.92.17.10 peer 10.92.17.9

2020-10-10 16:21:53,179 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:53 2020 /root/openvpndown.sh tun0 1500 1558 10.92.17.10 10.92.17.9 init

2020-10-10 16:21:53,181 DEBG 'start-script' stdout output:
/root/openvpndown.sh: line 6: kill: (7563) - No such process

2020-10-10 16:21:53,181 DEBG 'start-script' stdout output:
Sat Oct 10 16:21:53 2020 WARNING: Failed running command (--up/--down): external program exited with error status: 1
Sat Oct 10 16:21:53 2020 Exiting due to fatal error

Link to comment
15 hours ago, binhex said:

testing is now over, looks like its solid enough for me to release as latest, images now built for all VPN images i produce, please remove tag ':test' from the repository to pull down 'latest' again and 'force update' to ensure it is the latest image thats on disk.

 

If you wish to switch from openvpn to wireguard then please see Q21 from the following link:-

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

Might be a daft question, but does the wireguard config file support multiple endpoint entries, as ovpn does?

Link to comment
10 hours ago, notahtoomah said:

Howzit!? I can't seem to access the webgui after installing the container.

It looks like you are trying to connect to legacy PIA servers with the port forwarding option enabled. This is no longer working on the PIA side so you will need to switch over to a next gen server. Assuming ca-vancouver.privateinternetaccess.com is the server you are wanting to connect to, simply go into your ovpn config file and change the URL to ca-vancouver.privacy.network. Start the container and monitor the logs--you should see a port get assigned and then, finally, a message saying [info] Deluge Web UI started. WebUI should be accessible now.

Link to comment

Hi, 

 

I haven't been following too closely of late regarding WireGuard support, but I wanted to ask anyone whom has successfully got it working, what kind of speed increase are you seeing over regular openvpn? 

 

I ask as I am currently with NordVPN and Mullvad however Mullvad is a monthly subscription which I'm happy to change to PIA if its worth it. 

Link to comment

Hello,

 

I'm trying to use wireguard, but I'm running into trouble,

 

my log says:

 

[#] ip link delete dev wg0

2020-10-11 17:13:18,187 DEBG 'start-script' stderr output:

Cannot find device "wg0"

2020-10-11 17:13:18,187 DEBG 'start-script' stdout output:

[warn] WireGuard interface failed to come 'up', exit code is '1'

 

Can anyone help me, please?

 

Thanks

Link to comment
2 hours ago, TrCl said:

Hello,

 

I'm trying to use wireguard, but I'm running into trouble,

 

my log says:

 

[#] ip link delete dev wg0

2020-10-11 17:13:18,187 DEBG 'start-script' stderr output:

Cannot find device "wg0"

2020-10-11 17:13:18,187 DEBG 'start-script' stdout output:

[warn] WireGuard interface failed to come 'up', exit code is '1'

 

Can anyone help me, please?

 

Thanks

Just to check, but have you added the variable key when editing the container?
image.thumb.png.dd3758513603dc637a6408c3bf532f5f.png

Link to comment
8 hours ago, xxDeadbolt said:

Might be a daft question, but does the wireguard config file support multiple endpoint entries, as ovpn does?

right now, no, wireguard config with pia is a pita, its all dynamically generated for each host so it would take some additional code to deal with this.

  • Like 1
Link to comment
35 minutes ago, xxDeadbolt said:

Just to check, but have you added the variable key when editing the container?
image.thumb.png.dd3758513603dc637a6408c3bf532f5f.png

I added the variable VPN_CLIENT=wireguard. Is there another variable I should add? Thanks for your reply :)

Edited by TrCl
Link to comment
testing is now over, looks like its solid enough for me to release as latest, images now built for all VPN images i produce, please remove tag ':test' from the repository to pull down 'latest' again and 'force update' to ensure it is the latest image thats on disk.
 
If you wish to switch from openvpn to wireguard then please see Q21 from the following link:-
https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
 

I added the variable VPN_CLIENT=wireguard. Is there another variable I should add? Thanks for your reply

Nope, that should be it. Need to make the container have privileged access, too, but see the other quotes reply from Binhex on the steps. If you’ve done all them I’m not sure what else could be causing this.


Sent from my iPhone using Tapatalk
Link to comment
13 minutes ago, xxDeadbolt said:

 


Nope, that should be it. Need to make the container have privileged access, too, but see the other quotes reply from Binhex on the steps. If you’ve done all them I’m not sure what else could be causing this.


Sent from my iPhone using Tapatalk

 

Yeah, thanks. I think maybe it's the kernel version I'm on that's the issue. I'm running on a NAS that I believe is running version 4.14. Perhaps that's the problem. 

Link to comment

@binhex great work for fixing it. It all works like a charm again with PIA port forwarding. Been a big fan of this for a long time already. There is just one thing that used to work that does not work anymore; connecting to a specific IP of PIA's VPN severs. Before next-gen, I could replace the domain name (example: de-frankfurt.privacy.network) and replace it with an IP to ensure I'd get the same public IP assigned after a restart of the container. The connection to PIA still works when I select a specific IP, but the port forwarding somehow fails. It says that the port serving page of PIA refuses the connection (http://209.222.18.222:2000/?client_id=xxxx). I have no idea why the port forwarding suddenly breaks when trying to fix the IP in the openvpn configuration file, but is this something you could still have a look at? Some torrent sites are really paranoid and require me to provide a static IP :( The domain names rotate between a set of IPs for each region so you'll almost always have a different public IP after restarting the container or if the connection resets.

Edited by iLaurens
Link to comment
10 hours ago, dcarpenter85 said:

It looks like you are trying to connect to legacy PIA servers with the port forwarding option enabled. This is no longer working on the PIA side so you will need to switch over to a next gen server. Assuming ca-vancouver.privateinternetaccess.com is the server you are wanting to connect to, simply go into your ovpn config file and change the URL to ca-vancouver.privacy.network. Start the container and monitor the logs--you should see a port get assigned and then, finally, a message saying [info] Deluge Web UI started. WebUI should be accessible now.

Thank you! That worked. Much appreciated

Link to comment
On 10/10/2020 at 5:31 PM, southloven said:

So that fixed one part of my issue it looks like, but after coming back after a few hours, it looked like the docker was not connecting out. 

 

I did a ping on google.com and received a temporary domain name resolution failure notice. 

 

Any Ideas?  

24 hours with no issues... maybe it was a fluke. 

Link to comment
Yeah, thanks. I think maybe it's the kernel version I'm on that's the issue. I'm running on a NAS that I believe is running version 4.14. Perhaps that's the problem. 
Yes the old kennel version will be your issue, update kennel or use openvpn are your options

Sent from my CLT-L09 using Tapatalk

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.