Features
Console, ISO, backups and personal images
Four features that exist only on VMware connections: the browser console, the ISO library and CD mounting, server backups, and saving a server as an image.
On this page
Browser console
The console opens the server's screen in the browser. Customers can open the console of their own servers only; ownership is checked on the server side. The console shows the screen and nothing more: it does not bypass the operating system's login.
This is how the connection is made. The API obtains a single-use ticket from VMware and gives the browser a 60-second, single-use cookie that JavaScript cannot read. The browser connects to the console gateway at the panel's own address, and the gateway connects to the ESXi host. The VMware ticket never reaches the browser, and the ESXi management network is not exposed to it. The host's certificate is verified against the thumbprint VMware reports in the ticket; if the ticket carries no thumbprint, no connection is made.
Signing out of the panel closes the consoles opened in that session at once. An admin can close open consoles from a list. Console tickets issued before a sign-out, a ban or a transfer are refused as well.
Details: docs/console.md (Turkish).
ISO library and CD mounting
An admin connects the stores where ISO files are kept, browses them, and copies a chosen ISO to the datastore of one or more locations. Supported stores:
| Protocol | Note |
|---|---|
| FTP / FTPS | Explicit or implicit TLS |
| SFTP | Password or PEM private key |
| WebDAV | Nextcloud, ownCloud, NAS and other WebDAV servers |
| S3-compatible | MinIO, Ceph, Wasabi, Cloudflare R2, AWS S3 |
| SMB / CIFS | Windows, Samba, NAS |
| HTTP | An address with directory listing, read-only |
Copying is done as a stream; the file is not written to an intermediate disk, and the copy counts as failed if the byte count does not match. From the server page a customer mounts ISOs that are in the server's location and marked "available to customers", can boot from the ISO, and ejects it afterwards.
The limits: there is no direct upload from the browser; nothing can be copied from an HTTP store that does not report the file size; and because the upload goes through vCenter, vCenter's network speed decides how long a large ISO takes.
Backups and restore
A customer takes a backup of a server and restores from it. A server lock blocks restores too. The backups of a transferred server pass to its new owner.
This is a different thing from the backup of the panel's own database: the panel's backup does not contain customer VMs (Install, update and backup).
Personal images
A customer saves a server as an image and creates servers from that image in later orders.
What the README does not say
Where backups are stored, how long they are kept and how personal images are charged is not described in the README, so it is not described here either. Try these in your own environment before relying on them.
Install command
curl -fsSL https://lightningvm.app/install.sh | sudo shUbuntu 22.04 / 24.04 / 26.04. Requirements and options
