🚀 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 / Multi-Server & Licensing / Registering and Controlling Remote Servers

Registering and Controlling Remote Servers

If you run more than one dedicated server with Virtlix installed, you don't need to log into each one separately. Under Configuration → Servers, register another install by its URL and an API token generated on that install's own API Credentials page. Once connected, that server's VMs are listed and controllable (start/stop/reboot/destroy) directly from the registering panel, proxied over its API.

Master Configuration → Push to Servers also lets you push a chosen subset of settings out to every registered server at once, so branding or security policy stays consistent across a fleet without visiting each one - IP allowlists and the callback secret are deliberately excluded from this push, since those are meant to stay server-specific.