6 minutes ago, elliotiscool said:

Hey Binhex. I'd appreciate some help. Sonarr and Radarr stopped properly connecting to binhex-delugevpn and I tried to fix it without any success. I first suspected it was caused by PIA not allowing Switzerland.ovpn so I downloaded PIA's updated openvpn files. I replaced it with France. I also tried deleting perms.txt. Thanks.

supervisord.log 4.98 MB · 0 downloads

i had this very issue and I had to change port forward to ‘no’ inside the docker. 

21 minutes ago, elliotiscool said:

Hey Binhex. I'd appreciate some help. Sonarr and Radarr stopped properly connecting to binhex-delugevpn and I tried to fix it without any success. I first suspected it was caused by PIA not allowing Switzerland.ovpn so I downloaded PIA's updated openvpn files. I replaced it with France. I also tried deleting perms.txt. Thanks.

supervisord.log 4.98 MB · 1 download

you are using the old pia legacy network, from your log:-

2020-10-16 11:27:36.341444 [info] VPN remote server(s) defined as 'france.privateinternetaccess.com,'

you need to switch to next-gen, see Q19 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Hi Binhex, I'm having a bit of difficulty using wireguard (with mullvad). I've managed to get the container working with openvpn by following this post:

But I've had no success when I switch from openvpn to wireguard. So far I've tried the following:

 

1. Enable privileged, change 'VPN_CLIENT' to 'wireguard', and append extra parameter

   --sysctl="net.ipv4.conf.all.src_valid_mark=1"

    

2. Generate and copy my wireguard configuration file to /wireguard/, which I rename to 'wg0.conf' (although I doubt that matters). I implemented some of the suggestions you made in earlier posts, so my conf file looks something like

   [Interface]
   PrivateKey = <private key>
   Address = x.x.x.x/32,xxxx:xxxx:xxxx:xxxx::x:xxxx/128
   
   [Peer]
   PublicKey = <public key>
   AllowedIPs = 0.0.0.0/0
   Endpoint = y.y.y.y:zzzzz

Since I'm using wireguard, I shouldn't need the openvpn files. However, if I remove the files in /openvpn/, the container almost immediately fails:

2020-10-20 21:49:51.578271 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...

If I include the openvpn config files, the container starts successfully. However,  I can easily verify (by using https://ipleak.net/ and setting the wireguard/openvpn configs to different regions) that the container is just using openvpn, not wireguard. 

 

Is there something else I can do to force the container to use wireguard instead?

4 hours ago, radiation.syrup said:

If I include the openvpn config files, the container starts successfully. However,  I can easily verify (by using https://ipleak.net/ and setting the wireguard/openvpn configs to different regions) that the container is just using openvpn, not wireguard. 

i would suspect you havent defined VPN_CLIENT correctly, see this post:-

https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=902637

 

imminent removal of support for pia legacy network coming guys - i dont think anybody will be crying into their vindaloo here, as its been mostly broken (thanks pia! \s) for some time, but thought it worth a heads up on this.

Edited October 21, 20205 yr by binhex

20 minutes ago, binhex said:

imminent removal of support for pia legacy network coming guys - i dont think anybody will be crying into their vindaloo here, as its been mostly broken (thanks pia! \s) for some time, but thought it worth a heads up on this.

Yes, some locations have already been taken down.  I use L2TP on my router so that I can selectively route traffic through the VPN - the location I was using, Chicago, has gone down today.

I have switched to us-east which still seems to be operating .... but for how long?

 

It looks like I will have to subscribe to two different VPN providers - one which supports port forwarding and one which supports L2TP.  PIA have never supported L2TP/IPsec, so at least I have the option of finding a provider which offers that - such as ExpressVPN.

6 minutes ago, PeterB said:

PIA have never supported L2TP/IPsec

not possible to use this guide? - i know you arent using windows but hopefully enough info to get it going:- https://www.privateinternetaccess.com/pages/client-support/windows8.1-l2tp

11 minutes ago, binhex said:

not possible to use this guide? - i know you arent using windows but hopefully enough info to get it going:- https://www.privateinternetaccess.com/pages/client-support/windows8.1-l2tp

I have never managed to achieve an encrypted connection - it always reverts to bare L2TP.  PIA support aren't interested in resolving the issue.

Express, on the other hand, happily negotiates IPsec.

 

The PIA guide contains this sentence:

"If you need encryption, please use the Private Internet Application or OpenVPN protocol with our service."

suggesting that they are aware that IPsec doesn't work on an L2TP connection.

4 hours ago, binhex said:

i would suspect you havent defined VPN_CLIENT correctly, see this post:-

https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=902637

 

Thanks for getting back to me so soon! Unfortunately, that doesn't seem to be the issue. I have the key (not name) set to 'VPN_CLIENT' and the value set to 'wireguard', but the container still fails with the same error. 

 

2020-10-21 06:47:01.678693 [info] System information Linux xxxx 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux
2020-10-21 06:47:01.696537 [info] PUID defined as '99'
2020-10-21 06:47:01.715871 [info] PGID defined as '100'
2020-10-21 06:47:02.009384 [info] UMASK defined as '000'
2020-10-21 06:47:02.026586 [info] Permissions already set for volume mappings
2020-10-21 06:47:02.046493 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2020-10-21 06:47:02.009384 [info] UMASK defined as '000'
2020-10-21 06:47:02.026586 [info] Permissions already set for volume mappings
2020-10-21 06:47:02.046493 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2020-10-21 06:47:02.064229 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2020-10-21 06:47:02.082173 [info] VPN_ENABLED defined as 'yes'
2020-10-21 06:47:02.104528 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...

 

Edited October 21, 20205 yr by radiation.syrup
Add full log, add image

19 minutes ago, radiation.syrup said:

Thanks for getting back to me so soon! Unfortunately, that doesn't seem to be the issue. I have the key (not name) set to 'VPN_CLIENT' and the value set to 'wireguard', but the container still fails with the same error.

then i can only assume you are not running the latest image, what is set for 'repository' for the container?.

1 minute ago, binhex said:

then i can only assume you are not running the latest image, what is set for 'repository' for the container?.

The repository is 

binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04

 

Just now, radiation.syrup said:

The repository is 

binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04

 

yep thats the problem, you are using a tagged version, you need to drop the tag (the colon and everything after it) in order to download the latest image, this will of course mean you will move onto deluge 2.x

1 minute ago, binhex said:

yep thats the problem, you are using a tagged version, you need to drop the tag (the colon and everything after it) in order to download the latest image, this will of course mean you will move onto deluge 2.x

Ah ha, of course! Yes, I switched back to Deluge 1.3.15 for compatibility reasons. I'll give the new version ago. Thanks!

Edited October 21, 20205 yr by radiation.syrup

On 10/17/2020 at 1:47 PM, 3NBR said:

Trying to get this to work on a Synology NAS. Working no problem with OpenVPN but no joy with Wireguard. I am a newb, can anyone suggest what I'm doing wrong?

docker-compose.txt 1.02 kB · 4 downloads supervisord.log 11.37 kB · 3 downloads

Wireguard is new to me, so I'm just guessing based upon 1 hour of research; it looks like our linux kernel is too old. I'm at version 3.10 with DSM 6.2. Also, Synology doesn't provide official wireguard support while unraid does.

 

I'm going to be honest here, Synology makes awesome all-in-one products with long-term support but I'm hitting the wall of possibilities. Time to move away and use my Synology unit as backup unit.

22 minutes ago, BakedPizza said:

Wireguard is new to me, so I'm just guessing based upon 1 hour of research; it looks like our linux kernel is too old. I'm at version 3.10 with DSM 6.2. Also, Synology doesn't provide official wireguard support while unraid does.

 

I'm going to be honest here, Synology makes awesome all-in-one products with long-term support but I'm hitting the wall of possibilities. Time to move away and use my Synology unit as backup unit.

if your kernel is older than 5.6.x then yep you are out of luck and will have to stick to openvpn - or join the dark side and use unraid 🙂

40 minutes ago, binhex said:

if your kernel is older than 5.6.x then yep you are out of luck and will have to stick to openvpn - or join the dark side and use unraid 🙂

Oh, I will, eventually. 😄

 

Something else; my legacy PIA config connects just fine but whenever I try to use the next-gen PIA config it's stuck at this step:

Quote

[warn] Unable to successfully download PIA json to generate token from URL 'https://10.0.0.1/authv3/generateToken'
[info] 1 retries left
[info] Retrying in 10 secs...

Attached my log. I'm currently on 2.0.4.dev38_g23a48dd01-2-12. Am I doing something wrong, did I encounter a bug or is PIA messing with me?

 

 

supervisord.log

edit: solved. thanks!

Edited October 21, 20205 yr by elliotiscool

4 minutes ago, elliotiscool said:

I followed what you said but I still cannot connect.

 

log.txt 112.45 kB · 0 downloads

Your username and password were included in this log.  I suggest you go and change them. Also, looking at this log, it's saying authentication failed.  I'd make sure you have the right username and password

Edited October 21, 20205 yr by chesh

2 minutes ago, chesh said:

Your username and password were included in this log.  I suggest you go and change them.

Thank you. just changed the pass

Since PIA moved over to the next gen stuff and broke my previous install, I've been unable to connect.  I tried moving over to wireguard, but I just get this repeating:

2020-10-21 23:35:26,774 DEBG 'start-script' stderr output:
parse error: Invalid numeric literal at line 4, column 0

2020-10-21 23:35:27,612 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token from URL 'https://89.187.174.129/authv3/generateToken'
[info] Retrying in 10 secs...

I've downloaded and copied over the latest config files from PIA, I've followed the steps in the github for moving to wireguard, I've checked, and rechecked, and generated fresh credentials, not using wireguard I just keep getting AUTH FAILED over and over on every server, tried with port forwarding off, same thing.  Is PIA broken or is there something wrong with my config?  I've wiped and reinstalled delugevpn after upgrading didn't work, everything I do, I get the same errors, no changes...

 

Edited October 22, 20205 yr by worldspawn

16 hours ago, BakedPizza said:

Something else; my legacy PIA config connects just fine but whenever I try to use the next-gen PIA config it's stuck at this step:

Quote

[warn] Unable to successfully download PIA json to generate token from URL 'https://10.0.0.1/authv3/generateToken'
[info] 1 retries left
[info] Retrying in 10 secs...

ive seen a couple of people report this but i have been unable to replicate so unsure as to the cause, you could try another endpoint and see if that helps.

3 hours ago, worldspawn said:

I just keep getting AUTH FAILED over and over on every server,

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

18 hours ago, BakedPizza said:

Wireguard is new to me, so I'm just guessing based upon 1 hour of research; it looks like our linux kernel is too old. I'm at version 3.10 with DSM 6.2. Also, Synology doesn't provide official wireguard support while unraid does.

 

I'm going to be honest here, Synology makes awesome all-in-one products with long-term support but I'm hitting the wall of possibilities. Time to move away and use my Synology unit as backup unit.

What Synology device do you have? Im curious to this as I've looked up the kernel for Synology products and I can't find a straight answer online. It seems that DSM is heavily modified to the point where they don't announce what kernels they use anymore?

Edited October 22, 20205 yr by superkrups20056

Hey guys,

 

I'm pretty new to Binhex's image and I'm coming from huagene's transmission as they do not support next gen port forwarding yet. A few questions from a Synology DS218+ user:

 

1) Is the itconfig plugin really necessary for faster speeds like the FAQ says when     

 

    "enable_incoming_tcp": false,
    "enable_incoming_utp": false,
    "enable_outgoing_utp": false,

 

is included in the core.conf file?

 

2) Why don't plugins persist between turning on and off the container on Synology DS218+? Scheduler keeps turning off when I restart the container.

3) I keep getting "failed to upload torrent" when trying to add a manual torrent file. Log doesn't say anything.

4) Is there any way to completely disable the webui "deluge" password? I saw an autologin fork but I'd rather keep binhex's image.

 

Thanks for any help you can provide.

4 hours ago, binhex said:

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

Yeah, been through that document already, if it were something that simple, I wouldn't be posting here.

 

Your subscription has run out - double check this on the vpn providers website.

-nope, logged into the site today, I have over a year left

 

You have not typed in your username and/or password - do not copy and paste, type it in manually to prevent whitespace issues.

-nope, copy/pasted, manually entered, regenerated credentials, and retried several times, this is not the issue

 

You are using the wrong credentials - ensure the credentials are for openvpn/wireguard, NOT proxy servers etc.

-this is the only 'maybe' here, I can't tell if PIA uses different credentials for wireguard, and if so, I can't find them, but I was getting the error for openvpn as well as wireguard, so either way this isn't the issue for at least one of my attempts and both are having the same issue.

 

Your password contains a character which may cause issues - please ensure it only contains letters a-z (upper case or lower case) and numbers 0-9.

-nope, using credentials generated by PIA, no unusual characters

 

Out of date openvpn config file (ovpn extension) - ensure you download the latest ovpn file from your vpn provider.

-nope, fresh download, files are dated 8-11-20, from the next-gen zip file

 

The vpn provider you have signed up with is having authentication issues - try another endpoint, failing that contact the vpn provider and explain you are having authenticaiton issues when using native openvpn/wireguard clients with AUTH_FAILED shown.

-maybe, but I'd expect a company as big as PIA to have that somewhere public if their connections have been down for days...  Tried about 5 different endpoints, all give the same issue.