Virtual Machines
Fleet list, VM detail, power actions, console, backups, and snapshots
Manage your fleet at /platform/virtual-machines.
Each VM is provisioned on a provider's infrastructure but owned in your client organization. You control power state, firewall binding, backups, and snapshots from the NodeRings UI.
Fleet list
The list shows all VMs in the active client org with status, region, provider, and primary IPs. Use pagination and filters to navigate large fleets.
Status values include provisioning, running, stopped, and error states. Refresh if a VM was just created: provisioning can take several minutes.
Create a VM
Open /platform/virtual-machines/create from the fleet list or Marketplace.
Authentication method
Choose one bootstrap method at launch:
| Method | When to use |
|---|---|
| SSH keys | Recommended for production: select keys from SSH Keys |
| Password | Root password set via provider cloud-init |
| Cloud-init profile | Saved user-data profile: replaces provider user-data; you supply users, packages, and files |
With a cloud-init profile, password and SSH key pickers are disabled. Your profile must configure login (for example users, ssh_authorized_keys, or hashed_passwd).
Profiles support Jinja for built-ins ({{ vm.hostname }}, {{ vm_network.ipv4_address }}, …) and your org's environment variables and secrets. NodeRings compiles the template at create time.
The deprecated inline user-data paste on the create form still works but saved profiles are preferred.
VM detail page
Open a VM at /platform/virtual-machines/{id}.
| Tab | Purpose |
|---|---|
| Overview | Status, IPs, provider, plan, power actions, provider review |
| Graphs | CPU, memory, network metrics |
| Volumes | Attached storage (read-only view) |
| Images | OS / template info |
| Backups | Backup runs and restore |
| Snapshots | Create, restore, delete snapshots |
| Settings | Hostname, tags, additional IPv4 addresses, delete VM |
Power actions
From Overview:
| Action | Effect |
|---|---|
| Start | Power on |
| Stop | Graceful shutdown |
| Reboot | Restart |
| Delete | Remove VM and release billing (irreversible) |
Actions send orders to the provider's operator; allow a few seconds for Proxmox to reconcile.
Connect to your VM
After the VM is running and cloud-init has finished:
SSH (recommended)
ssh root@<assigned-ipv4>Use the SSH key you selected at launch, or the password if you chose password auth.
Assigned IPs appear on Overview (IPv4 and IPv6 from the provider's IPAM).
VNC console
Browser console: Console button or /platform/virtual-machines/{id}/console.
Traffic is relayed through the provider's vnc-gateway: Proxmox is not exposed on the public internet. Useful for installers or when SSH is not yet available.
If the display is blank, wait for first-boot to finish and reconnect.
Backups and snapshots
Both are per-VM tabs on the detail page (not a separate org-level backup page).
| Feature | Backups | Snapshots |
|---|---|---|
| Typical use | Scheduled vzdump-style backups | Point-in-time rollback |
| Billing | May be tied to backup addons on the plan | Snapshot storage addon on usage plans |
Backup schedule (UTC)
When you enable a Daily or Weekly backup plan on the VM Backups tab, automated runs use these platform defaults (all times UTC):
| Plan | Schedule | How often |
|---|---|---|
| Daily VM Backup | 02:00 UTC every day | 1 backup per day |
| Weekly VM Backup | 03:00 UTC every Sunday | 1 backup per week |
Enabling a backup plan also triggers one immediate backup so you do not have to wait for the next scheduled window. Later runs follow the table above. The Backups tab shows a schedule hint under the plan selector.
Backups use snapshot mode where supported so the VM can keep running during the job. Retention depends on the plan (for example seven days for daily, four weeks for weekly). Older backups are removed automatically when they expire.
Operations run on the provider side through the operator. Failures often indicate provider storage or quota limits: open a ticket if errors persist.
Provider review
Clients can leave one review per VM on the Overview card. Manage all reviews at /tickets/reviews. See Support → Reviews.
Create another VM
Create → /platform/virtual-machines/create. See Marketplace.
To launch a curated application (for example WordPress) instead of a plain OS, use the Instant Apps tab on create and reinstall. See Instant Apps.
Next
- Instant Apps — WordPress and credentials path
- Additional IPv4 addresses: extra IPv4 on a VM
- Marketplace: find plans
- Firewall: attach rulesets
- Troubleshooting → Provisioning