Problems SSH-ing into instances suddenly
Around yesterday I suddenly started getting Connection Refused errors whenever attempting a direct SSH connect to Runpod pods, which has left me unable to copy files back or forth. I did not change anything about my ssh keys or setup on my end, and this is the exact same workflow I have used in the past, so something must've changed on Runpod's side?
Anyone else having this problem?
Here's some verbose SSH logging
1 Reply
did you actually create a key in that path?, have you ever put the public key on runpod
and created the pod after you put it?