Installation
Post-install checklist
Tick every item before the first paid product. A save that succeeds with an empty catalog is the usual reason Create fails later.
Modules and access
-
modules/addons/SrvProxmoxSuite/is present -
modules/servers/SrvProxmoxSuite/is present - Addon Proxmox Suite is activated and admin roles are granted
- Encoded build:
srvprox.licis in both folders - Addons → Proxmox Suite → Info accepts the license key
- Nodes → Clusters List opens without a PHP fatal
Farm connectivity
- At least one cluster is saved under Nodes → Clusters List and Health succeeds
- System cron is installed
- Configuration → Cron Scheduler has been run for Farm catalog cache
- Nodes → Nodes List shows online nodes
Placement and addressing
- At least one Active policy under Nodes → Policy Manager, with a cluster, a load-balance rule, and IP pools
- An IPv4 block under Resource → Network → IPv4 Addresses (IPv6 or IPv6 Subnets only if you sell them)
- Those pools still have free addresses
Media and packages
- KVM and/or LXC templates imported, or the ISO library populated
- Optional: OS families, groups, firewall templates, backup templates
- Products → VM Plan → VM Plan: package saved and Active, with a policy selected
- WHMCS product module is Proxmox Suite, with Guest Type and Hardware Package set
Client experience
- Configuration → Client Area Features reviewed. This page is what VPS clients actually get.
- Console left in direct mode, or the proxy helper is running if you enabled it
- Test order: the guest exists on Proxmox and the service is linked on VM List → VMs List
Note
Switches on the VM Plan Client area features tab are stored. They are not applied to VPS services. Use Client Area Features under Configuration.
Operations
- Operations → Task History shows the test job, and any failed row has been retried or cancelled
- Error Log was checked after the first provision
Next step
Walk first steps if any box above is still empty.