Connect to a Pod with SSH

Connect to your Pods with SSH to manage long-running processes and critical tasks.

Connecting to a Pod through an SSH (Secure Shell) terminal provides a secure and reliable method for interacting with your instance. Use this to manage long-running processes, critical tasks, and when you need the full capabilities of a shell environment.

Every Pod offers the ability to connect through SSH using the basic proxy method below (which does not support commands like SCP or SFTP), but not all Pods support the full public IP method.

Generate an SSH key and add it to your Runpod account

1. Generate an SSH key using this command on your local terminal:

ssh-keygen -t ed25519 -C "[e-mail]"

This saves your public/private key pair to ~/.ssh/id_ed25519.pub and ~/.ssh/id_ed25519 respectively.

If you are using Command Prompt on Windows instead of the Linux terminal or WSL, your public and private key pair will be saved to C:\Users\YOUR_USER_ACCOUNT\.ssh\id_ed25519.pub and C:\Users\YOUR_USER_ACCOUNT\.ssh\id_ed25519, respectively.

2. Retrieve your public SSH key by running this command:

   cat ~/.ssh/id_ed25519.pub
   

   This will output something similar to this:

   ssh-ed25519 AAAAC4NzaC1lZDI1JTE5AAAAIGP+L8hnjIcBqUb8NRrDiC32FuJBvRA0m8jLShzgq6BQ [e-mail]
   

3. Copy and paste the output into the SSH Public Keys field in your Runpod user account settings.

If you need to add multiple SSH keys to your Runpod account, make sure that each key pair is on its own line in the SSH Public Keys field.

Override public key for a specific Pod

Runpod will attempt to automatically inject the public SSH keys added in your account settings for authentication when connecting using the basic terminal method. If you prefer to use a different public key for a specific Pod, you can override the default by setting the SSH_PUBLIC_KEY environment variable for that Pod.

Basic SSH connection

All Pods provide a basic SSH connection that is proxied through Runpod’s systems. This method does not support commands like SCP (Secure Copy Protocol) or SFTP (SSH File Transfer Protocol).

To connect using this method:

1. Ensure you have an SSH key pair generated on your local machine and added to your Runpod account.

2. Navigate to the Pods page in the Runpod console.

3. Expand your Pod and select Connect.

4. Select the SSH tab. Copy the command listed under SSH. It should look something like this:

   ssh [e-mail] -i ~/.ssh/id_ed25519
   

If you saved your key to a custom location, use that specific path after the -i flag instead.

5. Run the copied command in your local terminal to connect to your Pod.

Full SSH connection via public IP

For full SSH capabilities, including SCP and SFTP for file transfers, you need to rent an instance that supports a public IP address and ensure an SSH daemon is running within your Pod.

If you’re using a Runpod official template such as Runpod PyTorch or Stable Diffusion, no additional setup is required, as full SSH access is already configured for you.

However, if you’re using a custom template, ensure that TCP port 22 is exposed and that the SSH daemon is running inside your Pod. If it isn’t, add the Docker command below to your template (or, if you already have a custom start command, replace sleep infinity at the end of your command with this one):

bash -c 'apt update;DEBIAN_FRONTEND=noninteractive apt-get install openssh-server -y;mkdir -p ~/.ssh;cd $_;chmod 700 ~/.ssh;echo "$PUBLIC_KEY" >> authorized_keys;chmod 700 authorized_keys;service ssh start;sleep infinity'

Once you’re sure that the SSH daemon is running, you can connect to your Pod by following these steps:

1. Ensure you have an SSH key pair generated on your local machine and added to your Runpod account.
2. An SSH daemon must be started in your Pod. Runpod official templates, such as “Runpod PyTorch”, often have this pre-configured. If you’re using a custom template, ensure TCP port 22 is exposed and the SSH daemon is started. Refer to the Use SSH guide for commands to include in your custom Docker template.
3. Navigate to the Pods page in the Runpod console.
4. Expand your Pod and select Connect.
5. Select the SSH tab. Copy the command listed under SSH over exposed TCP. It should look something like this:

ssh root@213.173.108.12 -p 17445 -i ~/.ssh/id_ed25519

If you saved your key to a custom location, use that specific path after the -i flag instead.

6. Run the copied command in your local terminal to connect to your Pod.

The SSH command above has the following structure:

ssh root@[POD_IP_ADDRESS] -p [SSH_PORT] -i [PATH_TO_SSH_KEY]

Where:

• root: Your assigned username for the Pod (typically root).
• [POD_IP_ADDRESS]: The public IP address of your Pod.
• [SSH_PORT]: The designated public SSH port for your Pod.
• [PATH_TO_SSH_KEY]: The local file path to your private SSH key.

Troubleshooting

If you’re asked for a password when connecting to your Pod via SSH, this means something is not set up correctly. Runpod does not require a password for SSH connections, as authentication is handled entirely through your SSH key pair. This prompt usually indicates a problem with your SSH key configuration.

Here are some common reasons why this might happen:

• If you copy and paste the key fingerprint (which starts with SHA256:) into your Runpod user settings instead of the actual public key (the contents of your id_ed25519.pub file), authentication will fail.
• If you omit the encryption type at the beginning of your public key when pasting it into your Runpod user settings (for example, leaving out ssh-ed25519), the key will not be recognized.
• If you add multiple public keys to your Runpod user settings but do not separate them with a newline, only the first key will work. Each key must be on its own line.
• If you specify the wrong file path to your private key when connecting, SSH will not be able to find the correct key (No such file or directory error).
• If your private key file is accessible by other users on your machine, SSH may refuse to use it for security reasons (bad permissions error).
• If your SSH configuration file (~/.ssh/config) points to the wrong private key, you will also be prompted for a password. Make sure the IdentityFile entry in your config file matches the private key that corresponds to the public key you added to your Runpod account.