I am still wondering why it is still using "ns-cert-type server" since that option is deprecated on 2.4 version and we are not setting up that option. This configuration is autogenerated by the access server. So far I cannot see something wrong in our setup apart from "ns-cert-type server" option. So something mush have changed in the openvpn client that breaks my setup. In this setup if instead of latest version of openvpn connect I use version 2.7.1 or openvpn cli (2.4.9) then the connection is setup correctly. This setup does not seem to work anymore since we upgraded the openvn access server (2.8.5) and the openvpn connect to the latest version. Of course I have verified that the vpn host and port is reachable from my machine. This setup has been working fine so far with tunnblick v 3.2 and openvpn connect 2.7.1 or openvpn cli 2.4.9. I have a vpn connection to get to the office network by using tunnelblick and then from office to reach servers on our cloud infrastructure we have another vpn connection (openvpn access server ) by using openvpn connect to be able to connect to some ec2 machines. Since I upgraded the Openvpn connect to the latest version it is impossible to connect anymore to the vpn (or more accurately it connect once in 50 tries ).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |