Proxmox VE

Resell KVM virtual machines from Proxmox VE on WemX. Packages clone cloud-init templates, and customers manage the server from the order page.

Features

• Clone a template on create, then resize CPU, memory, and disk
• Cloud-init hostname, user, password, SSH keys, and DNS
• IPv4 by DHCP, a static address, or the next free address from a pool
• Place VMs on a chosen node, or on the node with the most free memory
• Full or linked clones
• Suspend, unsuspend, terminate, upgrade, and password changes
• Client panel with live CPU, memory, disk, and network usage
• Start, shutdown, reboot, and force stop
• noVNC console
• Reinstall from an OS template
• Customer snapshots, with a configurable limit
• Admin sidebar with the VMID, node, address, and usage

Install

Install from the WemX marketplace, or download Proxmox.zip from a GitHub release and place the Proxmox folder at extensions/Servers/Proxmox. Then enable Proxmox VE.

Publishing a release builds Proxmox.zip. Unzipping it creates a folder named Proxmox. GitHub’s own “Source code” archive still unpacks to server-proxmox-<tag>. Use Proxmox.zip.

Connection

Add a server connection with the Proxmox URL, a user such as root@pam or wemx@pve, and that user’s password. Include the port when needed, for example https://pve.example.com:8006. Turn SSL verification off for a self-signed certificate.

Optional connection defaults:

• Node. Leave empty to pick the node with the most free memory.
• Storage, usually local-lvm
• Bridge, usually vmbr0
• Fallback IPv4 pool, one address or range per line

Packages

OS templates are one per line:

ubuntu-24.04|Ubuntu 24.04 LTS|9000
debian-12|Debian 12 Bookworm|9002

The third field is the Proxmox template VMID. Templates should have cloud-init installed. Mark CPU, memory, disk, OS, and hostname as configurable when customers should choose them at checkout.