Closed harphere closed 3 years ago
Hmm -- I'll have to see what I can find out.
Can you tell me which server specifically you tried to connect to and does this error occur for any server you select?
Thanks --Tom
It occurred using Israel and Spain servers but I just now tried Toronto and Deluge connects.
Seems to be okay for me now.
OK this is has been addressed in the DelugeVPN container FAQ (I guess I should check the FAQ) :)
https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
Q22 and A22
The fix for this is to specify a fallback cipher on the client side to a cipher that PIA does support, this is done by editing the file /config/openvpn/<file with a ovpn extension>
and adding the following line:
data-ciphers-fallback aes-256-gcm
I am going to test this and then if successful I will add a fix into place for Mediabox. I'll post here when the fix has been pushed and you can update Mediabox.
OK as of commit https://github.com/tom472/mediabox/commit/58f596b9920967f114fda55e0012512ebf81f110 there is a fix in place to add the data-ciphers-fallback aes-256-gcm
line to the OVPN file in use for the DelugeVPN container.
You should be able to just re-run ./mediabox.sh
and get the update/ fix.
Thanks --Tom
I ran ./mediabox.sh
to update, but it still throwing the same error using Israel.ovpn.
I ran it again and chose Toronto, and Deluge is responding.
I did look at the FAQ, and manually changed the original Israel.ovpn in accordance with FAQ, restarted Deluge container, and Deluge responded fine.
The Toronto.ovpn works without following the FAQ changes.
I noticed though, in the FAQ, it says to remove
data-ciphers-fallback aes-256-gcm
and add
cipher aes-256-gcm
ncp-disable
But your commit adds the line data-ciphers-fallback aes-256-gcm
@nickelnine -- Yeah hazards of acting to quickly The info in the FAQ changed overnight
My comment above was literally a copy and paste from the FAQ last night.
The fix for this is to specify a fallback cipher on the client side to a cipher that PIA does support, this is done by editing the file
/config/openvpn/<file with a ovpn extension>
and adding the following line:data-ciphers-fallback aes-256-gcm
This morning I see the FAQ was then re-updated with the info you are seeing / posted. Been at work all day and haven't had a minute to push an update for the "new info" in the FAQ. Should hopefully have it pushed very quickly after work -- stay tuned.
OK let's try this again -- as of commit https://github.com/tom472/mediabox/commit/8ecb42de33ad4fc2db1e7507bf78597a56d08645 the correct fix for the PIA / OpenVPN ciphers should be fixed.
You should be able to just re-run ./mediabox.sh
and get the update/ fix.
Thanks all for hanging in ..
OK the info for the fix appears to have held solid for a while now. And the logs in the delugevpn appear to looking good. Calling this closed.
Hi,
I ran an update to
mediabox.sh
to use the Next Gen PIA network, but now I am seeing these errors in the delugevpn supervisord.log:Reading in other forums, it seems there is an incompatibly between PIA and OpenVPN, for which the suggested workaround is to downgrade OpenVPN to 2.4 until PIA issues a fix.
Is there any way to implement this in the
mediabox
script at all?Sorry I am not very techy, just a happy user!