proxmox-auth

Proxmox cluster authentication uses SSH access to individual nodes and API calls via pvesh. Connect to each node (spacenode1, spacenode2) with SSH credentials, then execute management commands directly or route API requests through the cluster interface to perform operations across all nodes.

Yes. After authenticating to Proxmox, use pct for container commands and qm for VM operations. Both tools work across the cluster when executed on authenticated nodes, letting you manage lifecycle, networking, and configuration for containers and VMs uniformly.

Use predefined troubleshooting patterns: run status and service information queries via pvesh, check node health, verify network diagnostics, and execute diagnostic commands inside containers or VMs. Read configurations and logs to isolate failures, then apply restarts or restores as needed.

GPU passthrough and advanced operations require authenticated cluster access and proper node configuration. Execute cluster commands to allocate resources, configure storage, and manage backup policies across nodes, using SSH and API patterns specific to your hardware topology.

SSH access enables direct command execution, but Proxmox API via pvesh provides centralized backup and storage management across the cluster. You can route backup, restore, and storage operations through a single authenticated session rather than connecting to each node separately.

SSH authentication to the Proxmox node is the primary method for executing internal commands. Once authenticated, use pct and qm tools to access container and VM internals, read their configurations, and perform management actions without additional credential layers.