Before you start
Add your SSH public key in the console before deployment. Keep the matching private key on your own computer; never upload it to the console.
Steps
- Open Connections on the GPU Instance page and copy its current SSH command.
- Use the exact username, port, and gateway information displayed. Certified images commonly use the non-root gpu user; custom images may differ.
- Pass the matching private key with ssh -i if your SSH agent does not already offer it. Verify host fingerprints through a trusted source when connecting for the first time.
- If you receive Permission denied (publickey), confirm that the selected public key matches the private key offered by your client.
- For custom images, verify that the SSH daemon is running, the user exists, authorized_keys is installed, and file ownership and permissions are correct.
Check the result
An authenticated SSH session opens inside the correct rental container.
Troubleshooting
The console API key is not an SSH password. Gateway and container authentication can fail separately. A rebuild or replaced container can change host keys; investigate instead of disabling host-key checking.