VIRTLIX LICENSE MANAGER
Home Features Docs Pricing Changelog About Contact Login
🚀 Getting Started
Installing Virtlix on a Fresh Server Server Requirements & Partition Layout Activating Your License Your First VPS
🖥️ VPS Management
Creating and Configuring a VPS Cloning and Rebuilding a VPS Creating a Reusable Template from a VPS Resource Plans and Per-VM Limits Windows Guest Support
🌐 Networking & Firewall
IP Pool and Network Modes VPS Firewall Rules Server-Level Firewall Plans Console Access: noVNC and the Web Terminal
💾 Backups & OS Templates
Automated Backups and Backup Destinations Managing OS Templates Uploading and Using ISOs Media Groups
🔑 Multi-Server & Licensing
Understanding Your License and VPS Limits Master Configuration and Security Settings Registering and Controlling Remote Servers Webhook Callbacks
❓ Troubleshooting & FAQ
Console Shows "Connection Lost" License Shows as Suspended or Expired VPS Won't Start After Creation Common Questions
Docs / Getting Started / Installing Virtlix on a Fresh Server

Installing Virtlix on a Fresh Server

Virtlix installs with a single command run as root on the target server. It sets up PHP, MariaDB, nginx, qemu-kvm and libvirt for you, then downloads and configures the panel itself.

curl -fsSL https://virtlix.com/install.sh -o install.sh
chmod 755 install.sh
./install.sh key=YOUR-LICENSE-KEY

By default the installer assumes NAT networking. If your provider gives you a routed IP block and you want guests to get public IPs directly on a bridge, pass network=bridge and bridge_name=br0 (or whatever your bridge interface is actually called).

The whole run takes 5-10 minutes on a typical KVM-capable box, most of it spent installing packages and cloning the base OS template used for your first VPS. Full output is logged to /var/log/virtlix-install.log - if something goes wrong midway, that log almost always has the real error near the bottom, not at the top.

Once it finishes you'll get the panel URL and a randomly generated admin password printed to the terminal. Log in once and change that password before doing anything else.