GitHub Community
SSH Key is not working #23215
-
|
I need help. I’m having problems accesing with my SSH Key. I’ve done all the steps to authenticate with a SSH Key but it didn’t work:
I’m running git 2.25.1 over WSL 2 (Ubuntu) on a Windows 10 machine. |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 3 replies
-
|
It looks as though you have successfully added keys to your account so I think that’s sorted. If you’re having trouble authenticating with your SSH key, we have some steps here for troubleshooting SSH. If that doesn’t work, you can always share what you are trying to do and what kind of errors you’re seeing- that will help folks come up with suggestions. |
Beta Was this translation helpful? Give feedback.
-
|
Even though I have already placed my key correctly, when I try to What can I do? The use of github credentials on the terminal is near to be deprecated. |
Beta Was this translation helpful? Give feedback.
-
|
@jesus1554, here are a couple of things to check You can still choose to use HTTPS, with a personal access token (instead of a password) if you prefer to having to use SSH. Once you have a token, you can enter it instead of your password when performing Git operations over HTTPS. |
Beta Was this translation helpful? Give feedback.
-
|
The problem now is resolved. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I just encountered the same problem from nowhere. The only thing is by accident I typed git push origin mains instead of main, and then when I did correctly, this happened. Please advise! Thanks. And I got the following back in Terminal (excluding sensitive info): WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ The fingerprint for the RSA key sent by the remote host is Please contact your system administrator. Please make sure you have the correct access rights |
Beta Was this translation helpful? Give feedback.
-
|
They changed the SSH RSA key this morning after the private key was accidentally published, see the announcement here: https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/ The fingerprint published in the docs has been updated too: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints The announcement describes how to update your |
Beta Was this translation helpful? Give feedback.
-
|
Just found that out.. They are so "nice" to let everyone know. i had to accidentally come across an article that was just published about this to find out AFTER having tried a million things to fix it. Still can't gain access to my repos which means can do NO WORK. I will look a the links you have provided. But I have to walk away from this for a bit. I won't share the words I am feeling right now about (Microsoft) Github. |
Beta Was this translation helpful? Give feedback.
-
|
I read the post We updated our RSA SSH host key that you shared here.,If i understand them correctly, they are stating that we would have to use THEIR key pair???? ]Because i tried generating a new key pair of my own with the new SSH protocol, and it did not work. Someone has to clarify all this. Something is very fishy about all this. Thanks so much for sharing your information with me. I really appreciate it! |
Beta Was this translation helpful? Give feedback.
-
|
SSH uses mutual authentication: You authenticate to the server using your key pair, and the server authenticates to you using its own key pair (that's the one that got compromised). The authentication from the server is critical so you can be sure you're connecting to the right server. See also: https://en.wikipedia.org/wiki/Public-key_cryptography |
Beta Was this translation helpful? Give feedback.
-
|
Hi @airtower-luna I actually am connected now. I even upgraded to the ed25519 SSH. However, when I check to see whether the fingerprint which is returned to me matches the one that Github has in their post, it does not match it. I have my own. I was not able to add the new key using the curl command. I had to add it manually. What does that mean? I can connect. No problem there so far. |
Beta Was this translation helpful? Give feedback.
-
|
I then tested my SSH connection, and also verified my public key, and everything seems good to go as expected. This was some (long)journey to figure out exactly if one is set up properly for SSH, and if the authentication process is valid. And sometimes confusing if you follow exactly the steps word by word. Thanks again for your help! Much appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
@interglobalmedia I am going through this right now. I was using ED25519 from the beginning so I shouldn't have been affected at all but I did. How did you manage to solve it? |
Beta Was this translation helpful? Give feedback.
-
|
Why is this so unstable? You have the key, I have the key, the signature is good, what is the issue? |
Beta Was this translation helpful? Give feedback.
@jesus1554, here are a couple of things to check
Within your local Git have you configured the correct URL for SSH as opposed to HTTPS protocol
SSH: git@github.com:jesus1554/sotano.git
HTTPS: https://github.com/jesus1554/sotano.git
Some further details here changing-a-remotes-url
You can still choose to use HTTPS, with a personal access token (instead of a password) if you prefer to having to use SSH.
If you use HTTPS you can create a token with the needed repository permissions, see creating-a-personal-access-token
Once you have a token, you can enter it instead of your password when performing Git operations over HTTPS.
For example, on the command line you would enter the following:
$ g…