Once your deployment reaches the Running state, you can connect via SSH. The connection details are displayed in the Deployments page.

​
Connection details

Each running deployment shows:
  • Host — The IP address to connect to
  • Port — The SSH port (22)
  • User — The SSH user, ubuntu

​
Connecting

Use your SSH key to connect:
Replace <port> and <host> with the values from your deployment details. The user is always ubuntu, not root.
You can add this to your ~/.ssh/config for convenience:
Then just run ssh mygpu.

​
Which key to use

  • Managed key — A default key pair is created for your account at signup and is pre-selected when you deploy. Its private key can be downloaded only once, as a .pem file; use that file.
  • Generated key — If you generated a key pair in SSH Keys, the private key was downloaded as a .pem file when you created it.
  • Your own key — If you uploaded your own public key (Ed25519 or RSA) in SSH Keys, use the corresponding private key. ECDSA keys are not installed on instances.
Make sure to use the key that was selected during deployment.

​
Browser apps

If you deployed an app template (PyTorch + Jupyter, Open WebUI + Ollama, ComfyUI), an Open button named after the app is displayed alongside the SSH connection details, and the Deployments table has an Open Application button. It opens the app at a private *.app.quantacloud.net URL after a QuantaCloud login, and only the account that owns the deployment can open it. Open WebUI also has its own sign-in; see Templates. You still have SSH access to the same instance.

​
Transfer files

Use scp or rsync to move files to and from your instance:
The instance disk is deleted when you stop the deployment, so download anything you want to keep first.

​
Port forwarding

Forward remote ports to your local machine for accessing web UIs like TensorBoard:
Then open http://localhost:6006 in your browser.

​
VS Code Remote SSH

You can use VS Code’s Remote - SSH extension to develop directly on your GPU instance:
  1. Install the Remote - SSH extension in VS Code
  2. Add your instance to ~/.ssh/config (see the config example above)
  3. Open the Command Palette (Ctrl+Shift+P) → Remote-SSH: Connect to Host → select your instance
  4. VS Code opens a new window connected to your GPU instance — edit files, run terminals, and debug as if it were local

​
Troubleshooting

The instance may still be booting. Wait 1–2 minutes after the status shows Running and try again.
  • Verify you’re using the correct private key (the one matching the public key selected during deployment).
  • Check file permissions: chmod 600 ~/.ssh/your_key
  • Ensure you’re connecting as ubuntu, not root.
  • Confirm the host and port from your deployment details.
  • Check that your local firewall or network allows outbound connections on the specified port.
The private key for a managed or generated SSH key is only available for download once. If you’ve lost it, generate a new key pair in SSH Keys or upload your own public key, then use that key for future deployments.