6.1. Installing the License¶

6.1.1. Using a Proxy Server to Activate Licenses¶

In situations when a direct Internet connection is not possible, you can specify an HTTP proxy to access the Key Administration (KA) server through. To do that, add the HTTP proxy information to the /etc/vz/vz.conf file as follows:

HTTP_PROXY="http://<host>:<port>/"
HTTP_PROXY_USER="<username>"
HTTP_PROXY_PASSWORD="<password>"

Note the following:

• You may need to create /etc/vz/vz.conf first.

• The proxy server must have the port 5224 approved for SSL traffic.

• The vzlicutils package is required for license auto-updating to work. If the package is not installed on your system for some reason, you can install it manually with yum. To enable license auto-updates after installing the package, launch the vzlicmon service with systemctl start vzlicmon. The service will show as /usr/sbin/vzlicmonitor in the running processes list.

Once the access to the proxy server is configured, proceed to install the license.

Virtuozzo Hybrid Server licenses are updated automatically by default. A few days before the current license expires, the vzlicmon service (a part of the vzlicutils RPM package) attempts to contact the Virtuozzo KA server over the Internet and obtain a new license.

6.1.2. Installing the License from Product Keys, Activation Codes, or License Files¶

To install a license from a product key or an activation code, run the vzlicload -p command or, to install from a license file, the vzlicload -f command. For example:

# vzlicload -p <key_or_code>
# vzlicload -f <license_file>

When you install a product key or activate a code, a license file is generated and installed in the etc/vz/licenses/ directory on the server. The difference between the product key and activation code is that the code needs to be activated online, so the server must be connected to the Internet. To activate the code, the installation tool accesses the Key Authentication (KA) licensing server and transmits the specified activation code to it. The KA server generates a license file, sends it back, and the license file is installed on the server automatically.