Proxmox VE Provider

This guide is for panel administrators. VPS users manage their assigned services through the customer panel and do not need Proxmox credentials. Use the compatibility list and setup instructions supplied with your release; available controls depend on the release and your administrative permissions.

Before You Start

• Confirm that your Proxmox version is supported by the installed release.
• Check that the panel server can reach the intended Proxmox HTTPS endpoint.
• Prepare suitable nodes, storage, network bridges and OS templates.
• Back up existing VMs before importing them or changing their configuration.

Setup

Open Admin > PteroCloud > Providers, or use the Setup Assistant in your release. Add a connection using the fields shown by that interface:

• A recognizable provider name and the intended location, where offered.
• The Proxmox hostname and HTTPS port, commonly 8006.
• The dedicated API token user, token name or ID, and secret as requested by the form.
• The certificate trust settings required for your endpoint.

For example, an endpoint may be https://pve.example.com:8006. If the form separates hostname and port, enter pve.example.com and 8006 in their respective fields.

API Tokens vs Passwords

Create a dedicated Proxmox API token rather than supplying a normal account password. Use the release's permissions guidance for the operations you intend to allow. Keep access limited to the necessary resources; do not grant unrestricted access just to silence a warning. Store the token secret privately and enter it only in the approved provider configuration form.

TLS

Use a valid, trusted certificate. For private certificates, use only the custom CA or pinning options supported and documented for your release. Confirm certificate details through a trusted channel before accepting them, including after renewal. Do not disable verification to work around a connection error.

Test Connection

Use the provider's connection test where available. Alternatively, from the panel directory with the configured PHP executable and service account, run:

php artisan pterocloud:proxmox:test PROVIDER_UUID

Replace PROVIDER_UUID with the provider reference shown by the admin interface, not a VM identifier. Review connectivity, authentication, discovery results and permission warnings. A successful connection alone does not prove that every VPS action is permitted. Resolve relevant warnings before testing a workload.

Synchronization

Use the synchronization action offered by your release, or run from the panel directory:

php artisan pterocloud:proxmox:sync PROVIDER_UUID

This updates the panel's inventory and recorded status from Proxmox, including node, instance, storage, network and template information. It is not a read-only diagnostic of the panel and is not a backup. Review the results and any warnings. Discovery does not automatically assign existing VMs to customers.

Import Existing VPS

Import an existing VM only if your release offers an import action for it. Confirm its backups, intended customer, location, resources and supported settings before proceeding. Import any required host first, following the Setup Assistant.

Review ownership, network and storage selections before confirming the import. Afterward, verify that the correct customer can see the VPS and that its displayed resources and connectivity are correct. Do not assume importing changes the guest OS or resizes its disks. If ownership is uncertain, stop and consult Resource Ownership.

For failures, see Provider Offline. Diagnostic output may contain private host or customer details; review it and share only what is needed privately with support, never credentials.