Hot answers tagged openvpn
Use a dynamic DNS service. Get a hostname for each site. configure VPN connections to use hostname for each connection instead of the sites IP address (Since you said its dynamic and subject to change) The dynamic DNS service should come with an application that monitors for an IP address change, and updates the hostname record automatically.
The SSL configuration, including the Listen directive for port 443, is in the /etc/httpd/conf.d/mod_ssl.conf file. If you don't find that file, or don't find the proper Listen directive in that file, then something is beyond wacky with your system.
I had the same error when trying this on my Raspberry Pi 2. First I found that starting the OpenVPN with this command returns some useful information. sudo /usr/sbin/openvpn --config /etc/openvpn/mullvad_linux.conf This made it clear I needed to update the config file with the correct path for the other ca.cert, mullvad.crt, mullvad.key, crl.pem by ...
Your problem is that the service startup file for CentOS will try to run any config file that's in /etc/openvpn - after all, it has no way of knowing which was the intended config file. Delete the client.conf file that's hanging around in that directory, or as raoima suggests move it to one side, and the openvpn startup script will stop trying to invoke it. ...
Use absolute path to point where each certificate/key is: ca /etc/openvpn/easy-rsa/keys/ca.crt cert /etc/openvpn/easy-rsa/keys/server.crt key /etc/openvpn/easy-rsa/keys/server.key dh /etc/openvpn/easy-rsa/keys/dh2048.pem You can also start the OpenVPN server invoking it's own binary. openvpn --config /etc/openvpn/server.conf --daemon As roaima said, ...
Only top voted, non community-wiki answers of a minimum length are eligible