Proxmox Setup

Recommended Proxmox layout

VMNexor can work with a standalone Proxmox node or a Proxmox cluster. For hosting providers, a cluster layout is recommended so templates, nodes, IP pools, and customer services can be managed consistently.

Before connecting a node

• Confirm the node is reachable from the VMNexor server
• Confirm Proxmox API access works
• Confirm storage names are correct
• Confirm bridges or routed networking are ready
• Confirm templates are available on the expected storage

API access

Use Proxmox API credentials with only the permissions VMNexor needs. Avoid using root password authentication for production automation where a scoped API token can be used instead.

Node requirements

• Working Proxmox API endpoint
• QEMU Guest Agent support enabled for templates
• Storage available for VM disks
• Consistent bridge or routed networking
• Correct firewall rules between VMNexor and Proxmox
• Enough CPU, memory, and disk capacity for the assigned plans

Storage guidance

• Use consistent storage names across nodes where possible
• Keep templates on storage visible to the nodes that will provision from them
• Use shared storage if you want easier multi-node template access
• Validate disk clone and disk move behaviour before selling plans publicly

Networking guidance

• Bridged networking is the simplest model when customers receive normal subnet/gateway assignments
• Routed /32 networking requires OS-specific guest configuration
• DNS should be tested inside the guest after every template change
• IP pools should match the real routing design on the target node

Guest agent guidance

The QEMU Guest Agent should be installed inside templates and enabled in Proxmox VM options. VMNexor can use guest-aware actions more reliably when the agent is present and running.

Basic node checks

pvesh get /nodes\npvesh get /nodes/<node>/qemu\npvesm status

Template visibility check

qm list\nqm config <template-vmid>

Firewall checks

• VMNexor must reach the Proxmox API port
• Console relay traffic must be allowed according to your deployment design
• Cluster/internal Proxmox traffic should remain restricted to trusted networks
• Do not expose unnecessary Proxmox management services publicly

Pre-flight test flow

• Add one Proxmox node to VMNexor
• Confirm node health appears correctly
• Add one disposable template
• Create one small test plan
• Provision a disposable VM
• Test start, stop, reboot, console, and reinstall
• Only then connect billing automation