Install VMNexor on Proxmox VE

Recommended deployment model

VMNexor is designed to run on a dedicated VM or server separate from the Proxmox hypervisor itself.

• Dedicated Ubuntu server or VM
• Public HTTPS access
• MariaDB database
• PHP 8.4
• Nginx reverse proxy
• Outbound access to Proxmox API endpoints

What the installer configures

• Shared release directories
• Laravel environment configuration
• Database migrations
• Queue and scheduler services
• Console relay service
• Nginx configuration
• License activation
• Application optimisation caches

Typical installation layout

Current release pointer
Release history
Persistent application data
Environment configuration
Application storage

Installer workflow

• Upload VMNexor package
• Run install-package.sh
• Enter database credentials
• Configure application domain
• Enter license details
• Create initial admin account
• Validate services
• Connect Proxmox infrastructure

Core services

Current VMNexor deployments use queue workers, scheduled tasks and a dedicated console relay service.

• vmnexor-queue.service
• vmnexor-scheduler.service
• proxmox-console-relay.service
• php8.4-fpm
• nginx

Connecting Proxmox

After installation, add your Proxmox node or cluster information inside VMNexor using API-driven authentication.

• Create Proxmox API credentials
• Restrict API permissions appropriately
• Add node hostname or IP
• Validate API communication
• Test VM lifecycle operations

Recommended next steps

• Build Linux templates
• Build Windows templates
• Configure provisioning plans
• Configure WHMCS integration
• Test OS reinstall workflows
• Validate console access

Production validation

• HTTPS works correctly
• Queue worker remains active
• Scheduler runs repeatedly
• Console relay works externally
• Provisioning succeeds repeatedly
• Reinstall workflows succeed repeatedly