OpenParable
Skip to content
← Back to skills

Vastai Common Errors

Testing & Quality
vastai-common-errors

Vastai Common Errors is an Agent Skill for testing & quality published in the jeremylongshore/claude-code-plugins-plus-skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Diagnose and fix Vast.ai common errors and exceptions. Use when encountering Vast.ai errors, debugging failed instances, or troubleshooting GPU rental issues. Trigger with phrases like "vastai error", "fix vastai", "vastai not working", "debug vastai", "vastai instance failed".

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/HEAD/plugins/saas-packs/vastai-pack/skills/vastai-common-errors/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/vastai-common-errors, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Vast.ai Common Errors

Overview

Quick reference for the most common Vast.ai errors across CLI, REST API, and instance operations. Vast.ai uses HTTP status codes for API errors and instance status strings for machine-level issues.

Prerequisites

  • Vast.ai CLI installed (pip install vastai)
  • API key configured

Instructions

API Errors

HTTP CodeErrorCauseFix
401UnauthorizedInvalid or missing API keyVerify with vastai show user; regenerate at cloud.vast.ai
403ForbiddenInsufficient balance or permissionsAdd credits; check account restrictions
404Not FoundInstance or offer ID does not existRe-search offers; instance may have been destroyed
409ConflictOffer already rented by someone elseSearch again and pick another offer
429Rate LimitedToo many API requestsWait 60s and retry with backoff
500Server ErrorVast.ai platform issueCheck status.vast.ai; retry after 5 minutes

Instance Status Errors

StatusMeaningAction
loadingDocker image downloadingWait; large images can take 5-10 min
runningInstance readyConnect via SSH
exitedContainer stoppedCheck logs: vastai logs INSTANCE_ID
errorProvisioning failedDestroy and try a different offer
offlineHost machine went downDestroy; provision on a different host

Common CLI Errors

# Error: "No offers found"
# Cause: Filters too restrictive
# Fix: Relax filters
vastai search offers 'num_gpus=1 rentable=true' --limit 5  # broader search

# Error: "Insufficient funds"
# Fix: Check balance and add credits
vastai show user --raw | python3 -c "import sys,json; d=json.load(sys.stdin); print(f'Balance: \${d[\"balance\"]:.2f}')"

# Error: "Instance creation failed"
# Fix: Try a different offer or smaller disk
vastai create instance OFFER_ID --image ubuntu --disk 10

Docker Image Errors

# Error: Instance stuck in "loading" for >10 minutes
# Cause: Very large Docker image or slow host internet
# Fix: Use smaller base images or pre-cached templates
# Good: pytorch/pytorch:2.2.0-cuda12.1-cudnn8-runtime (4GB)
# Bad:  custom-image-with-everything:latest (30GB)

# Error: "Container exited immediately"
# Cause: Bad entrypoint or missing dependencies
# Fix: Check logs
vastai logs INSTANCE_ID --tail 50

SSH Connection Errors

# Error: "Connection refused" after instance shows "running"
# Cause: SSH server not yet started inside container
# Fix: Wait 30-60 seconds after status changes to running

# Error: "Permission denied (publickey)"
# Cause: SSH key not uploaded to Vast.ai
# Fix: Upload at cloud.vast.ai > Account > SSH Keys

# Error: "Host key verification failed"
# Fix: Use -o StrictHostKeyChecking=no for ephemeral instances
ssh -p PORT -o StrictHostKeyChecking=no root@HOST

GPU/CUDA Errors

# Error: "CUDA not available" inside container
# Cause: Docker image missing CUDA or driver mismatch
# Fix: Use NVIDIA-provided images with matching CUDA version
# Check host CUDA: vastai show instance ID --raw | jq '.cuda_max_good'

# Error: "CUDA out of memory"
# Cause: Model too large for GPU VRAM
# Fix: Search for more VRAM or reduce batch size
vastai search offers 'gpu_ram>=48 num_gpus=1' --order dph_total

Output

  • Identified error with matching resolution
  • Corrected configuration or command
  • Verification that the fix resolves the issue

Error Handling

CategoryDiagnostic Command
Auth issuesvastai show user
Instance statusvastai show instances
Instance logsvastai logs INSTANCE_ID
Offer availabilityvastai search offers 'rentable=true' --limit 5
Balance checkvastai show user --raw | jq '.balance'

Resources

Next Steps

For comprehensive debugging, see vastai-debug-bundle.

Examples

Instance won't start: Run vastai show instance ID --raw | jq '{actual_status, status_msg}' to get the status message. If error, destroy and reprovision on a different host.

Billing surprise: Run vastai show instances to check for forgotten running instances. Destroy any you're not using to stop charges.