Start here
Run these checks before reporting a problem:
jio --version
jio usage
jio listThen run jio <command> --help and confirm the command matches your installed
release. Rerun the installer to update the CLI; saved credentials and configuration
are preserved.
Common problems
| Symptom | Check |
|---|---|
jio: command not found | Add ~/.local/bin to PATH, then open a new shell |
| Not logged in | Run jio login '<your-api-key>' or set JIO_API_KEY |
| Saved login belongs to another endpoint | Log in with --host or unset the endpoint override |
| Requested size unavailable | Choose an advertised size with jio config |
| Quota exceeded | Destroy unused VMs or contact the operator |
| Creation result uncertain | Reconcile with jio list before creating another VM |
| Cannot connect | Use the original client machine and confirm the VM is ready |
| Stop/start rejected | The session is ephemeral; destroy it when finished |
Public support
For reproducible non-security bugs, open an issue in the Jio client repository. Include the CLI version, platform, redacted command, error text, and session state. Never attach credentials or private workload data.
Private security reports
Email support@jiovanni.sh for suspected vulnerabilities. Do not open a public issue. See Security & Privacy for the required report details.