Install 'net-tools' and 'wget' packages on CentOS 7:
yum install net-tools wget
Type wget followed by the pasted URL:
wget <paste copied url>
Install downloaded package on RedHat/CentOS/Fedora system:
rpm -Uvh openvpn-as-2.1.12-CentOS7.x86_64.rpm
The installation process should then commence and finish. The output may look like this:
The Access Server has been successfully installed in
/usr/local/openvpn_as Configuration log file has been written to
/usr/local/openvpn_as/init.log Please enter "
passwd openvpn" to set the initial administrative password, then login as "openvpn" to continue configuration here:
https://192.168.70.222:943/admin To reconfigure manually, use the
/usr/local/openvpn_as/bin/ovpn-init tool. Access Server web UIs are available here: Admin UI:
https://192.168.47.222:943/admin Client UI:
The Access Server tries to adapt itself to the network configuration it finds. But if you have a complex network setup you may need to run the ovpn-init tool to reconfigure to listen to another network interface. It's worth mentioning that the ovpn-init tool can be used to wipe all OpenVPN Access Server configuration with the --force option in case you make a mistake during initial setup. Don't use the --force option on an existing installation unless you can live with losing all configuration and certificates and want to start over. Also, the program will ask for a license key, but you do not have to enter one. If no valid license key is found it will just assume a demonstration mode where all functions work but you're limited to 2 simultaneous VPN tunnel connections.
Finishing configuration and using the product
Once the program is installed it will automatically configure itself with some standard settings. The installation process will also tell you where to find the client web service, which is the web based GUI that you can use to log on and connect to the Access Server, and where to find the admin web service, which is where you can log on as an administrative user and manage the configuration, certificate, users, etcetera, in the web based GUI. Usually the client UI is at the address of your server, for example
https://192.168.70.222/. The admin UI is usually at the /admin/ address, for example
https://192.168.70.222/admin/. Please note that the web services by default actually run on port TCP 943, so you can visit them at
https://192.168.70.222:943/ as well. The OpenVPN TCP daemon that runs on TCP port 443 redirects incoming browser requests so that it is slightly easier for users to open the web interface.
Initially a single administrative user is added to the system. But it has no password set and therefore cannot be used yet. To use it a password must be set first:
You can now point your web browser at the admin UI web interface. Because the Access Server comes with a self-signed SSL certificate to begin with, you will receive a warning in the browser like "Invalid certificate" or "Cannot verify identity of the server". You will have to confirm that you wish to continue to the web interface. You will then see the login screen and you can then enter the username openvpn and the password you have just set with the "
passwd openvpn" command.