Heralax Posts - Answer Overflow

Heralax

•Created by Heralax on 9/7/2024 in #⛅｜pods

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

~ []$ ssh -v [email protected] -p 13399 -i ~/.ssh/id_ed25519
OpenSSH_9.0p1, LibreSSL 3.3.6
debug1: Reading configuration data /Users/evan/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/* matched no files
debug1: /etc/ssh/ssh_config line 54: Applying options for *
debug1: /etc/ssh/ssh_config line 58: Applying options for *
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to 91.199.227.82 [91.199.227.82] port 13399.
debug1: connect to address 91.199.227.82 port 13399: Connection refused
ssh: connect to host 91.199.227.82 port 13399: Connection refused

~ []$ ssh -v [email protected] -p 13399 -i ~/.ssh/id_ed25519
OpenSSH_9.0p1, LibreSSL 3.3.6
debug1: Reading configuration data /Users/evan/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/* matched no files
debug1: /etc/ssh/ssh_config line 54: Applying options for *
debug1: /etc/ssh/ssh_config line 58: Applying options for *
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to 91.199.227.82 [91.199.227.82] port 13399.
debug1: connect to address 91.199.227.82 port 13399: Connection refused
ssh: connect to host 91.199.227.82 port 13399: Connection refused

3 replies

Gaming

Programming