Connecting and working

Connect over SSH

The instance page shows the SSH command for your machine. You connect as root with the key you added.

# Host and port are on the instance page
ssh root@HOST -p PORT

# If your key is not the default one
ssh -i ~/.ssh/my_key root@HOST -p PORT

Once connected, check the GPUs and start a tmux session so long jobs keep running if your connection drops.

nvidia-smi          # list the GPUs
tmux new -s work    # start a session
tmux attach -t work # reattach after reconnecting

Keep your work on /data

If you added a data disk, it is mounted at /data. Keep code, datasets and results there. It is kept when you restart the same machine.

df -h /data
cd /data && git clone YOUR_REPO_URL

Copy results out

Run these on your own computer, not on the machine. Note the capital -P for the port in scp.

# One file
scp -P PORT root@HOST:/data/results/model.pt ./

# A whole folder, resumable
rsync -avP -e "ssh -p PORT" root@HOST:/data/results/ ./results/

Release when you are done

Release the machine from the console and confirm its ID. Releasing deletes the machine and its data, unless the order offered kept disks and you chose to keep them.

Unused whole hours go back to your balance. See Billing.

If you cannot connect

• Permission denied (publickey): the key you are using is not on the machine. Check that it was added under SSH keys before you rented, and point ssh at the matching private key with -i.
• REMOTE HOST IDENTIFICATION HAS CHANGED: an earlier machine used the same host and port. Remove the old entry with ssh-keygen -R "[HOST]:PORT" and connect again.
• Still stuck? Email [email protected] with the instance ID. See Support.

Something missing or unclear? Email [email protected].