Hosting a Teleconsole instance on macOS: "500 Internal Server Error: ssh: no key found" #42
Comments
Actually, this might not be exclusive to macOS. This happens when I try to host a teleconsole instance on CentOS 7.2:
Here is what
These are the same keys that I have on the macOS server in the previous post. |
hm... interesting. will take a look, thanks for reporting this |
I hate to bump a super old question, but I'm having the exact same issue (on Linux) Input:
Output:
It just suddenly happened, it's worked before. I thought it was a problem with Github, but I'm able to use the same keys with other services. I also tried using the public keys I have on my device (manually adding keys not through the Github API), which returned I even ran teleconsole on a VM, that way I could be sure that the problem isn't with my machine, and it still persisted. This led me to believe there was something wrong with my keys in particular, so I tried it using various other accounts. This somehow worked, and opened up a teleconsole session.
(This session is not still running of course.) This behavior was also exhibited in the VM. Thinking it was my ssh keys for some reason, I generated multiple new pairs in different formats, none of which worked. I have no idea why this suddenly started happening, but I really would like to try to resolve it. |
Solution (For me):I was using ed25519 keys, which apparently don't work. My solution was to generate new keys with |
I'm trying to play around with secure Teleconsole sessions, using macOS 10.12.6 to host. However, I receive this error when running
teleconsole -vv -i JesseTG
:Giving My GitHub Username
(Note that my username is
Jesse
, with a capital J)Explicitly Giving a Key
If I try explicitly specifying a key, this is what happens:
I don't remember whether or not I'm supposed to give the private or the public key, so I tried both.
SSH Directory
My
~/.ssh
directory looks like this:Both of those keys are associated with my GitHub account.
Unprotected
Unprotected teleconsole works as expected but is not what I'm trying to do:
The text was updated successfully, but these errors were encountered: