What's new

OpenVPN 2.4.0 client problems [Solved]

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

MacG32

Regular Contributor
Hello all. I've tried this tutorial: https://www.snbforums.com/threads/h...ia-and-other-vpn-providers-10-15-fixed.30851/ , another tutorial, and combinations of both, but I can not get the OpenVPN client to work correctly. Ir runs, but I can't connect to the internet. My log file and settings are listed below. I tried to import the correct .ovpn file from https://www.privateinternetaccess.com/openvpn/openvpn-strong.zip and get "Error 17 while importing file - invalid key and/or certificate! Fix your config file, then import it again.", so I have to manually import the certs. Thank you.

http://pastebin.com/qL1R2Ubw

http://oi63.tinypic.com/b9hk04.jpg
 
Open the zip file, you'll have there a file if I'm not mistaken is called ca4096.crt. Paste its contents in the CA box of the vpn client config page, will look something like this:
upload_2017-2-4_13-10-48.png
 
Open the zip file, you'll have there a file if I'm not mistaken is called ca4096.crt. Paste its contents in the CA box of the vpn client config page, will look something like this:
View attachment 8444

Thank you. I did that with the ca.rsa.4096.crt file and the crl.rsa.4096.pem file. The client turns on, but I get no internet access while it's running. The log has errors in it that I don't understand.
 
Reverting back to 380.64_2 from 380.65 fixed it. This wasn't the solution I was looking for. When importing the .ovpn file in 380.64_2, I still get "Error 17 while importing file - invalid key and/or certificate! Fix your config file, then import it again.", so I have to manually import the certs. Below is the working log file. If there is a way to fix it using 380.65, I would greatly appreciate it.

http://pastebin.com/cagpyMk2
 
Last edited:
Why not contact the tech support of your tunnel provider? If their ovpn file isn't compatible with OpenVPN 2.4.0, then they will have to eventually address it on their end, as everyone will eventually upgrade to this new version.
 
Why not contact the tech support of your tunnel provider? If their ovpn file isn't compatible with OpenVPN 2.4.0, then they will have to eventually address it on their end, as everyone will eventually upgrade to this new version.

The .ovpn file doesn't import the certs, but all of the settings import on OpenVPN v2.3.14 and OpenVPN v2.4.0. Both show the identical error. When I tested this on 380.4164, it imported the file just fine. No errors. All I had to do with OpenVPN v2.3.14 and OpenVPN v2.4.0 is add the cert files.

OpenVPN v2.4.0 should be backwards compatible with v2.3.14 settings, but this doesn't seem to be the case at all here. This tutorial: https://helpdesk.privateinternetacc...ing-up-an-Asus-Router-running-Merlin-Firmware is from the provider, but it doesn't work with 380.65's implementation of OpenVPN v2.4.0 when adjusting for the stronger encryption.

Why would OpenVPN even think to write new code that isn't capable of running with current provider's standards?
 
Last edited:
Hi Guys, I do also face trouble when runing the new 380.65 stable version with OpenVpn 2.4.
Can't get the connection established anymore. Please find attached the system log.; I'm not really good in reading it.
 

Attachments

  • asuslog.txt
    18.3 KB · Views: 491
Maybe it was bit miss writing from my side, I have of course recognized the fatal error, but I have no idea how I can fix it. I guess I can find the solution inside the link I got from you @Martineau
 
Why not contact the tech support of your tunnel provider? If their ovpn file isn't compatible with OpenVPN 2.4.0, then they will have to eventually address it on their end, as everyone will eventually upgrade to this new version.

the providers need to update sooner than later - there is good stuff inside OpenVPN 2.4, but that jump is going to be a bit painful...
 
Last edited:
I didn't downgrade. I just changed my settings to match yours and Strong is working for me too.
 
Just tried the same and disabled Cipher Negotiation, but still having the same error. I contacted Perfect Privacy support in the mean time, hope they are able to help.
 
Why would OpenVPN even think to write new code that isn't capable of running with current provider's standards?

Things evolve. Old parameter might become obsolete or superceded by new ones. It's up to anyone who configures his client or server to keep up with config changes as they occur. 2.4.0 brought quite a few major changes that requires this.
 
Hi Guys, I do also face trouble when runing the new 380.65 stable version with OpenVpn 2.4.
Can't get the connection established anymore. Please find attached the system log.; I'm not really good in reading it.

The fix to your problem has been posted in the 380.65 release thread. you need to disable these two ipv6-related parameters because Asuswrt does not support IPv6 at OpenVPN's level.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top