Skip to content

Troubleshooting: Proxmox

Authentication failure

Symptom: PROVIDER_AUTH_FAILED (PC-PVE-003). The provider rejected the configured token or user. The token is never shown in diagnostics or bundles.

  • Confirm the API token still exists and is not expired.
  • Confirm the token user has the privileges the operation needs (see permissions).
  • Rotate the credential in Admin → PteroCloud → Providers → Rotate Credentials.

Permission denied

Symptom: PROVIDER_PERMISSION_DENIED. The token is valid but lacks a required privilege. Grant the missing privilege; do not switch to root@pam unless that is your policy.

TLS failure

Symptom: TLS_UNTRUSTED, TLS_FINGERPRINT_MISMATCH or TLS_VALIDATION_FAILED.

  • Install the correct CA certificate, or pin the expected fingerprint.
  • Never disable TLS verification. That is not a supported remediation.

Connection timeout / unavailable

Symptom: PROVIDER_TIMEOUT, PROVIDER_UNAVAILABLE.

  • Check the management network path to the Proxmox API (tcp/8006).
  • Check Proxmox is not in maintenance.
  • Re-enable a disabled connection.

Proxmox task failed

Symptom: PROXMOX_TASK_FAILED (PC-PVE-005). Read the task log in Proxmox; the panel records the UPID. Common causes are storage errors and configuration conflicts.

SSRF guard rejected the endpoint

Symptom: PROVIDER_INVALID_CONFIG. Non-HTTPS scheme, 0.0.0.0, link-local/ metadata IPs, ::1 or a bad hostname. Use an https endpoint with a routable address; private LAN ranges are allowed by default.