Administration

This page is for panel administrators. VPS users should use their assigned instance's controls and contact their hosting provider for account or service issues.

Admin Panel Navigation

Open Admin > PteroCloud. Use the Setup Assistant for initial configuration and the Support Center for diagnostics where available in your installed release. Sections and actions vary with release, configured services and administrator permissions. Do not treat a missing control as a reason to bypass permissions or modify data manually.

Admin Overview

Review the information available in your release during routine checks:

• Provider connectivity and the freshness of inventory information.
• Host health and free CPU, memory and storage capacity.
• Available IP addresses for the services you offer.
• Active or failed tasks and customer reports of access problems.
• Backup results and the health of required background services.

A summary dashboard is not a substitute for verifying backups or monitoring guest applications.

Hypervisor Management

Before enabling a host for customer workloads, confirm its location, storage, networking and available capacity. Use the supported refresh or inspection controls when information appears stale; see Proxmox Synchronization.

Do not remove a provider or host while it still has customer dependencies. Coordinate changes with affected customers and follow your release's maintenance guidance.

Tasks View

Use the task view available to your account to follow ongoing or failed operations. Check the affected VPS before retrying; a failed task does not mean no changes occurred. See Tasks for safe progress checks and support details.

Maintenance Mode

Use maintenance controls only where your release supports them, and read the confirmation text for the affected resource. Do not assume maintenance mode moves or stops existing VPSs, or makes a host safe to reboot.

Notify customers, back up affected workloads and arrange shutdowns or other supported maintenance steps separately. Verify service health before resuming normal use.

Reconciliation

If panel information differs from Proxmox, check the provider connection and refresh inventory using the supported synchronization action. Review active tasks before changing anything directly on the virtualization host.

If a VPS, disk or network still appears missing or incorrect, preserve the current resources and collect diagnostics. Do not create replacements until you know the actual state.

Resource Ownership

Confirm the customer and intended use before assigning or importing a VPS. Resources discovered on a provider are not automatically approved for customer access. Follow Import Existing VPS if your release supports it.

Orphaned Resources

Treat resources with an unknown or missing owner as requiring investigation. Do not delete an unfamiliar VM or disk merely because it is absent from the panel. Check backups, customer records and provider information, then contact support if unclear.

Safe Recovery

Prefer preserving customer data over forcing a failed action to appear successful. Do not edit database records, clear shared caches or delete resources as a generic repair. Use Troubleshooting and diagnostics before making changes.

Audit Logs

Where your release provides an activity or audit view, review the actor, time, affected resource and result when investigating changes. Keep exported logs private. Review and redact host and customer details before sharing them with [email protected]; never include credentials.