RunPod•2mo ago

Not able to ssh via "Overexposed SSH"

I am able to login with the basic SSH but Over exposed asks me for password. This is not working

⬢ ❯ ssh root@xxx -p 13776 -i ~/.ssh/id_ed25519
root@xxx's password:
Permission denied, please try again.
root@xxx's password:

⬢ ❯ ssh root@xxx -p 13776 -i ~/.ssh/id_ed25519
root@xxx's password:
Permission denied, please try again.
root@xxx's password:

This works

⬢ ❯ ssh xxx-xxx@ssh.runpod.io -i ~/.ssh/id_ed25519

⬢ ❯ ssh xxx-xxx@ssh.runpod.io -i ~/.ssh/id_ed25519

Solution:

You can use OhMyRunPod

Jump to solution

31 Replies

nerdylive•2mo ago

whats over exposed is it an ssh software? i cant find it anywhere It's using Key as authentication

GokulaKrishna•2mo ago

I mean Over exposed tcp option in dashboard

nerdylive•2mo ago

ohh i get that now

nerdylive•2mo ago

Check your ssh did you setup that yet?

GokulaKrishna•2mo ago

yes and basic SSH works

nerdylive•2mo ago

ohh so you got your keys setup already Hmm what template are you using then?

GokulaKrishna•2mo ago

RunPod Pytorch 2.0.1

nerdylive•2mo ago

alright let me try it first on my side

digigoblin•2mo ago

Do you have more than 1 public key in your profile?

nerdylive•2mo ago

even tho their profile has more than 1 key it will still be exported to the container right?

digigoblin•2mo ago

No not necessarily

nerdylive•2mo ago

Hmm so it will only export only one of them?

digigoblin•2mo ago

This is wrong:

digigoblin•2mo ago

https://github.com/runpod/containers/blob/main/container-template/start.sh#L29

GitHub

containers/container-template/start.sh at main · runpod/containers

🐳 | Dockerfiles for the RunPod container images used for our official templates. - runpod/containers

nerdylive•2mo ago

Ohh yea ic

digigoblin•2mo ago

Should be like this to include them all:

    if [[ ${PUBLIC_KEY} ]]; then
        echo -e "${PUBLIC_KEY}\n" >> ~/.ssh/authorized_keys
    fi

    if [[ ${PUBLIC_KEY} ]]; then
        echo -e "${PUBLIC_KEY}\n" >> ~/.ssh/authorized_keys
    fi

Otherwise it includes only one of them

nerdylive•2mo ago

I'll put it on feedbacks yeah thank you

GokulaKrishna•2mo ago

Do you have more than 1 public key in your profile?

you mean in my SSH agent?

digigoblin•2mo ago

In your RunPod profile on the runpod web console, how many ssh public keys did you save there?

nerdylive•2mo ago

In here*

GokulaKrishna•2mo ago

I have only one

digigoblin•2mo ago

Did you add it here before or after you created the pod?

nerdylive•2mo ago

Oh it works for me: 1. i ran ssh-keygen -t ed25519 -C "your_email@example.com"( generates using default settings ) 2. then added it to: https://docs.runpod.io/assets/images/c340553-image-5834fe29a2179e6bb7fb75f5aa664037.png 3. created a new pod 4. press connect then use that line that you pointed at for connecting via TCP, it works!

nerdylive•2mo ago

But when i tried to add it to the ssh public keys ( web ) after i created my pods, it isnt updated, so you can create new one, or rerun this

echo "$PUBLIC_KEY\n" >> ~/.ssh/authorized_keys

echo "$PUBLIC_KEY\n" >> ~/.ssh/authorized_keys

with $PUBLIC_KEY replaced with your ssh public key's content as text

GokulaKrishna•2mo ago

before the creation

nerdylive•2mo ago

But if the normal ssh only works, the tcp should work too. maybe you should contact support with your pod id

Solution

digigoblin•2mo ago

You can use OhMyRunPod

digigoblin•2mo ago

pip install OhMyRunPod
OhMyRunPod --setup_ssh

pip install OhMyRunPod
OhMyRunPod --setup_ssh

nerdylive•2mo ago

how does it works? it outputs new keys?

GokulaKrishna•2mo ago

i ran this command and it generated password. i use that to login

nerdylive•2mo ago

Oh alright thanks

Gaming

Programming

Not able to ssh via "Overexposed SSH"