Troubleshooting

This page lists common issues and how to resolve them. If you can't resolve an issue yourself, see Getting help at the bottom of the page.

VM provisioning and state

VM is stuck in provisioning or never reaches running

The Cloud has no free capacity to place the VM, or the requested instance type cannot be placed on any of the Cloud's Nodes.

• Add a Node to the Cloud to increase capacity — see Scaling Nodes.

• Confirm the instance type is available in your Cloud.

• If the VM stays in provisioning after capacity is available, contact support.

VM is in the failed state

The VM hit an error during provisioning or operation. A failed VM cannot be recovered.

• Delete the VM and create a new one.

• If VMs repeatedly enter failed, contact support.

See VM Lifecycle and States for the full list of states.

Connectivity and access

Cannot SSH into a running VM

• SSH key wrong or missing — keys are set at creation and cannot be changed afterwards. Recreate the VM with the correct public key.

• VM not ready — confirm the VM is running, not still starting.

• Client IP not whitelisted — verify your IP whitelisting.

• Network reachability — VMs are reachable only within your Tenant VLAN. Connect from within that network. See Network Configuration.

GPU or NVMe device not visible inside the VM

Passthrough devices require the appropriate drivers in the guest OS.

• Install and verify the GPU/NVMe drivers inside the VM.

• Confirm you used an image compatible with the passthrough hardware.

Cloud and Node management

409 Conflict when creating a Cloud

A Cloud with the same name already exists. Choose a unique name.

Cannot delete a Node (node_has_vms / node_not_running)

• node_has_vms — the Node still hosts active VMs. Move or delete those VMs first.

• node_not_running — the Node is in a transitional state (e.g. still provisioning or already being removed). Wait until it settles.

Cannot delete a Cloud

The Cloud still has active VMs. Delete all VMs in the Cloud first.

API errors

401 / 403 on API calls

• The PRIVATE-TOKEN header is missing or invalid — check your API token.

• The calling IP is not whitelisted — add it to your whitelist.

See API v3 Authentication.

A list endpoint returns only 25 results

This is the default page size. Use the RANGED-DATA header to page through larger result sets — see Getting started with FlexVM.

Getting help

If you can't resolve an issue — especially anything related to networking, which is configured by i3D.net internal teams — contact i3D.net support. Include your Tenant (K#), the Cloud UUID, and the VM UUID so we can locate the resources quickly.