scp / exposed TCP ssh is not working
So. I can log in to my server through the normal ssh channel, but I can't scp via it or do other trickery to get files up there.
If I try to do the exposed TCP approach, it asks me for a password even though I have public keys set up (working for non-exposed TCP login). I've tried setting a root password in the pod, using my main account password, tried installing openssh-server in the pod, tried manually creating /etc/ssh/authorized_keys inside the pod, none of those helped, it always just denies whatever password I enter and ignores my public key.
Help? I'm about to upload lots of gigs of data to a random VPS somewhere and then download it from the pod with wget, but it's sort of ridiculous that that seems to be the only approach that works to get data up and onto the pods. Am I missing something here?
scp'ing data from another pod through that approach does seem to work, so maybe it's some kind of firewall issue? My ISP is not blocking the appropriate port, so I'm pretty sure it is not on my end.
2 Replies
The password will always decline as you don't have one set. What our images do is copy the value of $PUBLIC_KEY to the
/root/.ssh/authorized_key directory. That may be what you're missing.Yeah, IDK, it has now been working for me according to the process described in the dialog. Either it was an intermittent issue, or I was doing something wrong, IDK.
Basically what I was saying is that I shouldn't even see a password prompt in the first place (and, indeed, now that it's started working, I do not.) It seems like there was a mismatch preventing the public key auth from working in the first place. But like I said, it's working now; I'm not sure what changed so I'll mark it as solved.