29 minutes ago, Simon said:

Thanks. I just went back to that version too and it works again (Q5 at https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md for anyone want to do the same)

 

43 minutes ago, ThatCanuck said:

I've been randomly having issues today with PIA, can confirm that it was working well yesterday.  My docker config uses ouroboros to auto update, and it looks like DelugeVPN latest was updated last night. 

 

Several troubleshooting steps, but the one that worked was to revert to what looks like the previous build in docker.  Can confirm that binhex/arch-delugevpn:2.0.4.dev38_g23a48dd01-2-15 works.

 

This fixed it for me as well

Tagging @binhex so you don't spend too much time going down the AirVPN rabbit hole.  Looks like a regression of some sort in the latest build.  

I can also confirm the latest update broke my openvpn connection. I rolled back to binhex/arch-delugevpn:2.0.4.dev38_g23a48dd01-2-15 and everything worked again. If you need logs or .ovpn files please let me know. 

17 hours ago, Simon said:

I've been using this for months with no issue with ExpressVPN, but a recent update has caused it to fail with

 

2020-11-29 10:10:34,196 DEBG 'start-script' stdout output:
2020-11-29 10:10:34 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.

2020-11-29 10:10:34,196 DEBG 'start-script' stdout output:
2020-11-29 10:10:34 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Options error: --proto tcp is ambiguous in this context. Please specify --proto tcp-server or --proto tcp-client
Use --help for more information.

2020-11-29 10:10:34,198 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

repeatedly occurring in the log file. Any idea what's up?

 

Edit: Seems to be reported here too https://github.com/binhex/arch-delugevpn/issues/230

supervisord.log 1.42 MB · 3 downloads

17 hours ago, phiper said:

I'm having the exact same issue. I'm using the Expressvpn Toronto server.

 

The .ovpn and credentials file are working fine with binhex-sabnzbvpn.

 

Hi,

 

Same problem here with Express VPN. Tried other locations, redownloaded the certificates, tried to reconfigure, restored from a backup, nothing worked.

Adding --proto udp doesn't seem to be working, since i still get the TCP error, when adding --proto tcp-client, i get another error, that fragments can only be used with udp.

I just applied the docker update that was just realesed and now I can't connect to the web gui. I get "the site can't be reached". Worked fine until I applied the update. I went in and disabled the VN Enabled option and it works. I use air vpn and went to the website and my id and password works and my account is active.

Edited November 30, 20205 yr by DigitalDivide

HOw does one roll back to the last known working version?

I'm using AirVPN and have had the same issue.

To get round this I used the AirVPN config generator to create a TCP rather than UPD protocol .ovpn

Not ideal but worked for me.

28 minutes ago, gesutc said:

I'm using AirVPN and have had the same issue.

To get round this I used the AirVPN config generator to create a TCP rather than UPD protocol .ovpn

Not ideal but worked for me.

please can you try the 'test' tagged image, let me know if it fixes it.

40 minutes ago, DigitalDivide said:

HOw does one roll back to the last known working version?

Using tags.

After the repository name type a colon and then the tag for the version you want to install. You can get previous versions here.

are there any instructions on how to do this? I have no idea about tags. Do I do this on the command line? 

12 minutes ago, DigitalDivide said:

are there any instructions on how to do this? I have no idea about tags. Do I do this on the command line? 

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

Edited November 30, 20205 yr by Simon

10 minutes ago, DigitalDivide said:

are there any instructions on how to do this? I have no idea about tags. Do I do this on the command line? 

You just edit the repository setting in the docker configuration. Type a colon and then the version number after the name.

15 minutes ago, DigitalDivide said:

are there any instructions on how to do this? I have no idea about tags. Do I do this on the command line? 

@binhex has just pushed another release. It may fix whatever your issue is.

Just uninstalled and reinstalled but same problem. For the previous version do I just put in the following

binhex/arch-delugevpn:2.0.4.dev38+g23a48dd01-2-15

3 minutes ago, wgstarks said:

@binhex has just pushed another release. It may fix whatever your issue is.

imminent fix for protocol issue for non pia vpn providers, the image is just building, please pull down latest in approx 30 mins from now.

1 hour ago, binhex said:

please can you try the 'test' tagged image, let me know if it fixes it.

Works for me.  Thank you.

Ok, managed to get the "test" one installed and it resolved my issue.

4 minutes ago, binhex said:

imminent fix for protocol issue for non pia vpn providers

I was having issues with PIA NextGen that were resolved by reverting to an old version.  Should that be addressed in the updates you just made to latest?

Just now, ThatCanuck said:

I was having issues with PIA NextGen that were resolved by reverting to an old version.  Should that be addressed in the updates you just made to latest?

probably not, no, please go back to latest and do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

I think I've found the cause I've my intermitant issues.
I've noticed if I schedule "off" time with deluge, when it resumes there is no connection (or rather, torrents cant connect).

 

Maybe PIA killing the connection if no activity? Or a Deluge bug of some kind?

Edited November 30, 20205 yr by tjb_altf4

4 minutes ago, tjb_altf4 said:

Maybe PIA killing the connection if no activity? Or a Deluge bug of some kind?

i would suspect Deluge, even if the connection was dropped by PIA, it would be re-created automatically by my watchdog scripts.

1 hour ago, binhex said:

probably not, no, please go back to latest and do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Latest is now working on my PIA NextGen config.  I didn't produce detailed logs per the link as the issue appears to be resolved.

Latest is failing for me - PIA/Wireguard

It just hangs, seemingly for ever.

DelugeVPNLog.txt

5 minutes ago, PeterB said:

Latest is failing for me - PIA/Wireguard

It just hangs, seemingly for ever.

DelugeVPNLog.txt 6.71 kB · 2 downloads

i think that is a vpn provider issue, i suspect its stuck at waiting for local ip address to be assigned to wg0/tun0, try turning on debug to confirm.

8 minutes ago, PeterB said:

Latest is failing for me - PIA/Wireguard

It just hangs, seemingly for ever.

Sorry - with Debug on!

DelugeVPNLog.txt