🚀 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

❓ Troubleshooting & FAQ

Console Shows "Connection Lost" License Shows as Suspended or Expired VPS Won't Start After Creation Common Questions Can't SSH Into a New LXC Container PCI Passthrough Device Not Working NFS Storage Pool Won't Mount OS Template Download Stuck or Failed

Docs / Troubleshooting & FAQ / Console Shows "Connection Lost"

Console Shows "Connection Lost"

If the noVNC console or Server Terminal worked fine over plain HTTP but shows "connection lost" only after switching to HTTPS, this is a known, specific cause: HTTP and HTTPS are served by two independent nginx server blocks, and the WebSocket proxy locations (/vnc-ws/, /internal/terminal-auth, /terminal-ws/) need to exist in both.

Fix: go to Configuration → SSL Settings and reapply your certificate configuration. That regenerates both the HTTP and HTTPS vhosts consistently from the same template, so the WebSocket paths end up in both. Confirm with nginx -t afterward and reload nginx if you're doing this by hand rather than through the panel.