To install VMmanager, you need license information. If you purchased VMmanager from ISPsystem, you can view this information in your personal account at eu.ispsystem.com in the "Platforms" section. To install, you need a value from the Token field.
SELinux will be disabled during the installation as it prevents the platform from working correctly.
- Connect to the server via SSH with the superuser permissions (root per default).
Download the installation script:
curl -O https://download.ispsystem.com/6/installer/vm/vmCODE
Make it executable:
chmod +x vmCODE
Run the installation process using the activation key (license token):
./vm install -l="<token>" -s=<version>CODE
<token> — the value of the Token parameter of your license. You can find it in the Client area eu.ispsystem.com on the license information page in the Platforms section;
- -s — platform release version. The default value is stable. Possible values:
- stable — stable software version;
regular — regular software version that includes all functionality updates;
The stable version can only be upgraded to the latest stable version; the regular version can only be upgraded to the latest regular version.
- Optional parameters
Optional command parameters:
-n — domain name of the server. Will be used in the platform URL;
./vm install -l="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" -n="vmmanager.example.com"CODE
--registry-port — TCP port for downloading docker container images. Use this option if the server denies incoming connections on ports 5000/tcp and 443/tcp;
./vm install -l="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" --registry-port=5001CODE
-f — installation on a server with specifications below the required ones;
--ssl-crt-file, --ssl-key-file — path to the files with the public and private key of the SSL certificate. The data will be added to the web server settings;
./vm install -l="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" --ssl-crt-file="/root/example.crt" --ssl-key-file="/root/example.key"CODE
- --proxy — HTTP proxy settings in the format http://<user>:<password>@<address>:<port>:
- <user> — username for authorization. Optional parameter ;
- <password> — password for authorization. Optional parameter ;
- <address> — HTTP proxy IP address;
<port> — HTTP proxy port.
Example command for a proxy with authorization
./vm install -l="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" --proxy="http://admin:email@example.com:3128"CODE
Example command for a proxy without authorization
./vm install -l="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" --proxy="http://192.168.57.1:3128"CODE
The installer will check the server against the minimum system requirements. If the server does not meet the requirements, a warning of the form will appear in the terminal window:
Example of the warning
Checking available resources of the machine ... fail Resources of the machine don't match with minimal requirements RESOURCE | MACHINE | REQUIRED ------------+----------+----------- CPU Speed | 3.60 GHz | 2 GHz CPU Cores | 1 | 2 RAM | 0.47 Gb | 2 Gb Storage | 6.94 Gb | 40 GbCODE
To install the platform on a server with specifications below the required ones, add the -f parameter to the installation command:
./vm install -l="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" -fCODE
After the platform is installed successfully, in the terminal you will see the access link to VMmanager:
The panel has been successfully installed
Link to administrator registration page: https://18.104.22.168/auth/setup?token=C50A0BFA55DEDE3343AABE713022A15FBASH
When you open a link, your browser will display a warning about a possible security threat. This happens if the server uses a self-signed SSL certificate. You can connect a valid SSL certificate to the platform by following the instructions.
- Go to the VMmanager interface using the received link and create the first user:
- Enter the User email.
- Create a Password or click generate to automatically generate a password.
- Click Done.
- Perform the initial setup of the platform.
- If you have a resource package certificate, activate it:
- Go to → System information → Activate package .
Enter the code from your resource package certificate.
- Press Activate.
For more information about resource packs, see the Licensing article.
After installation, VMmanager platform will be available by the IP address or domain name of your server. The installer will be started as the systemd service.
To increase the fault tolerance of the platform, you can move it to the HA cluster. For more information, see the article Migrating a server with VMmanager to a VM in an HA cluster.
Reinstalling the platform
- Create a new Token value for your license. You can do it in your client area at eu.ispsystem.com or contact technical support.
Stop the platform:
Delete the directory /opt/ispsystem/vm :
rm /opt/ispsystem/vm -rfCODE
Restart the vm service:
systemctl restart vmCODE
Install the platform:
vm install -l="<new_token>"CODE
Comments to the command:
<new_token> — new value of the Token parameter for your license.
If you have lost the login link
When VMmanager is installed on the server, but the first user is not created, you can get the unique link to the web-interface:
- Connect through SSH to the server with VMmanager.
Execute the installation command through the systemd service vm:
vm install -l="<token>"CODE
- <token> — the value of the Token parameter of your license. You can find it in the Client area eu.ispsystem.com on the license information page.
- Log in to the interface using the link and specify the credentials of the first user.
The VMmanager installation log is kept in the file /opt/ispsystem/vm/install.log.