🚀 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
Rescue Mode: Recovering a Broken VPS
📦 LXC Containers
LXC Containers: What They Are and When to Use Them
Creating and Managing an LXC Container
LXC Container Limitations vs KVM
🌐 Networking & Firewall
IP Pool and Network Modes
VPS Firewall Rules
Server-Level Firewall Plans
Console Access: noVNC and the Web Terminal
Network Filtering: Anti-Spoofing and Rogue RA Protection
IPv6 Dual-Stack Networking
Power DNS Integration and Reverse DNS Zones
Adding Multiple IPs and Per-IP MAC Overrides
💽 Storage & Hardware
Storage Pools: Local Disk and Remote NFS
PCI and USB Device Passthrough
Attaching Extra Volumes to a VPS
💾 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
Selling VPS Hosting Through WHMCS
🔐 Account & Security
Two-Factor Authentication
Docs /
VPS Management /
Creating a Reusable Template from a VPS
Creating a Reusable Template from a VPS
If you've got a VPS set up exactly how you want - packages installed, configs in place - you can turn it into a reusable OS template instead of starting from a stock cloud image every time.
From a stopped VPS's page, choose Create Template. Virtlix snapshots its disk into /var/lib/virtlix/templates and lists it alongside the stock templates on the Create VPS form, tagged so you can tell your own templates apart from the built-in ones.
A couple of things worth knowing: the source VPS keeps running fine afterward (this doesn't consume or move its disk, it copies it), and templates created this way don't auto-update - if you change the source VPS later, you'll need to create a new template to capture those changes.