Skip to main content
Start here when something isn’t working. Each section covers the quick fixes first and links to the detailed guide.

​
Connection issues

  1. Confirm the instance is in the Ready state — SSH is only available once provisioning completes.
  2. Copy the exact SSH command from your Active Instances page rather than constructing it by hand.
  3. Verify you’re using the private key matching the public key on your account, with correct permissions (chmod 600 ~/.ssh/your_key).
  4. Run with ssh -v and include the output if you contact support.
More detail: On-Demand Quickstart — troubleshooting.
  • Use tmux or screen so sessions survive disconnects.
  • Long-running jobs should never depend on an open SSH session — run them under nohup, tmux, or a process manager.

​
Instance issues

Provisioning normally completes in minutes. If an instance is pending for more than 30 minutes, contact support with the instance ID. Instances that never become ready are automatically terminated at the provisioning timeout (~3 hours) and are never charged — see Pricing.
GPU drivers are preinstalled on all instances. Do not install or upgrade drivers yourself — contact support with the instance ID and the nvidia-smi output.
The two common causes:
  • Balance reached zero. Instances are automatically terminated when your account balance is no longer positive. Configure Auto Top-Up to prevent this. Note the 30-day grace period to recover data on storage volumes.
  • Reservation ended. Reserved instances are automatically terminated at the end of the reservation period — see Pricing.
On-machine data is not recoverable after termination; data on attached storage volumes survives.
Run the checks in Verifying Instance Performance — they’ll either identify the bottleneck or give you the outputs support needs to investigate.
See Managing Instances for the full lifecycle of instance states and what each one means.

​
Storage and networking

Check usage with df -h. Onboard NVMe is fixed per configuration; attach a persistent storage volume for more space, or clean caches (~/.cache, old checkpoints, unused Docker images: docker system prune). Details: Storage and Ports.
Confirm the port is exposed in your instance’s port configuration and the service is bound to 0.0.0.0 rather than localhost. See Storage and Ports for port setup and Securing Open Ports before exposing anything publicly.
Attachment, mounting, and performance issues are covered in the storage troubleshooting section.

​
Billing

Balance, deposits, and charge questions are covered in Billing & Payments. The most common surprise: billing starts the moment an instance becomes ready and continues until termination — even when the GPU is idle.

​
Still stuck?

Contact support — include your instance ID, region, timestamps, and the exact error output.