GitHub Community
Cannot push files because key fingerprint doesn't match my saved SSH key #48086
-
|
Problem with SSH key I created a new SSH key and saved it to my account, deleting my old one. Now when I try to push my files to a repo, I'm getting this error: The authenticity of host 'github.com (140.82.112.4)' can't be established. Please make sure you have the correct access rights The key fingerprint shown above does not match the SSH key I saved. How do I fix this? |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 12 replies
-
|
Hi @hmkonz, The GitHub Community on Discussions is a space for all GitHub users to come and discuss ideas and projects. Your duplicate post was removed because it contained content that violates our Community Code of Conduct, including posting the same comment in multiple places. As a result, we have removed the duplicate post, and we ask that you no longer cross-post. For additional guidance, please review our Community on Discussions Code of Conduct and GitHub’s Terms of Service. |
Beta Was this translation helpful? Give feedback.
-
|
I'm so sorry! I didn't mean to post my question somewhere else and not sure how that happened. This is my first time posting to the community so I apologize! |
Beta Was this translation helpful? Give feedback.
-
|
No worries, an apology is unnecessary 😄. Welcome to the community 🎉 we're glad you're here. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks so much! I'm a student doing Springboard's software engineering bootcamp and use Github frequently to upload exercises and projects but I'm still a newbie and have lots to learn! I appreciate the support! |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
That message is not about your key, it's about the key used to identify the GitHub server. SSH uses authentication with the host key to ensure no-one can trick you into connecting to an attacker's server instead. But SSH can't know if the host key is the right one for that server by itself, so it's asking you to check if that key is correct for GitHub publishes their key fingerprints here: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints Make sure the fingerprint you're seeing is one of those (depending on the key type), and accept if it is. SSH will remember that for future connection. If the key fingerprint you see is not on the list, figure out who's messing with your network. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much for your reply! I don't remember having to accept a fingerprint before when I set up an SSH key, but anyway, the fingerprint I'm getting is on the list so I will accept it and hopefully be able to push my files to my repo. Thanks so much again! |
Beta Was this translation helpful? Give feedback.
-
|
Glad I could help! Please don't forget to mark the answer. 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for letting me know I had to do that! I assume I just click on the 'Mark as answer" button so the green checkmark shows? |
Beta Was this translation helpful? Give feedback.
-
|
Yep, that's what I meant, thank you! 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
-
|
not publish my project |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as off-topic.
This comment was marked as off-topic.
That message is not about your key, it's about the key used to identify the GitHub server. SSH uses authentication with the host key to ensure no-one can trick you into connecting to an attacker's server instead. But SSH can't know if the host key is the right one for that server by itself, so it's asking you to check if that key is correct for
github.com(or whichever other server you're connecting to).GitHub publishes their key fingerprints here: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints
Make sure the fingerprint you're seeing is one of those (depending on the key type), and accept if it is. SSH will remember that for fu…