Some machines on US-NC-1 cannot be SSH'ed in | Runpod | Page 1

remote shadow Jan 20, 2026, 8:23 PM

#

This only started being an issue since about a week ago, but on the US-NC-1 cluster a lot of H200 machines cannot be SSH'ed in.

When I try to connect to it in VSCode, it gives me the error

Error: Your SSH client doesn't support PTY

So I cannot install the VSCode server there.

In addition when I try to ssh in my terminal

ssh [email protected] -i ~/.ssh/id_ed25519

I get the output

-- RUNPOD.IO --
Enjoy your Pod #i9ahkmpqwsup78 ^_^

Error response from daemon: container f7e7dca56686bb8d648a9cad96efe67e99cbc641a2fe5941ea7a2238466551a1 is not running
Connection to 100.65.28.75 closed.
Connection to ssh.runpod.io closed.

I attached 2 screenshots of the UI: pic 1 is what I see for a machine that doesn't support TCP; pic 2 is one that does.

I don't know if there are similar issues for other clusters. Is there a way for me to circumvent this?

idle ploverBOT Jan 20, 2026, 8:24 PM

#

tiny axle Jan 23, 2026, 10:36 AM

#

are those two using the same template?

remote shadow Jan 23, 2026, 7:31 PM

#

Yes

remote shadow Jan 23, 2026, 9:34 PM

#

If it helps, the same issue happens for the A40s on US-NC-1

remote jackal Jan 23, 2026, 10:43 PM

#

I'm also having this problem and it hasn't been resolved yet

meager flicker Jan 24, 2026, 3:14 AM

#

remote shadow This only started being an issue since about a week ago, but on the US-NC-1 clus...

is TCP port 22 exposed in your template? Also. have you tried logging in using web terminal?

tiny axle Jan 24, 2026, 4:18 AM

#

Maybe the ssh isn't running inside the pod, try checking for service, and your ash keys inside the pod using web terminal, btw the links in the screenshot and url seems different

#Some machines on US-NC-1 cannot be SSH'ed in