I strongly encourage you to consider having users authenticate with keys as well.
![host verification failed. host verification failed.](https://www.sneppets.com/wp-content/uploads/2020/04/docker-tutorials.jpg)
Host verification failed. update#
(If the wrong key is in /etc, someone with administrative privileges will have to update the system-wide file.) The reason for this prompt is is no longer in your known_hosts after deleting it and presumably not in the system’s /etc/ssh/ssh_known_hosts, so ssh has no way to know whether the host on the other end of the connection is really. Or, equivalently, let ssh do it for you next time you connect with git fetch, git pull, or git push (or even a plain ol’ ssh ) by answering yes when prompted The authenticity of host ' (a.b.c.d)' can't be established.Īre you sure you want to continue connecting (yes/no)? If this does not seem fishy to you, remove the old key from your local cache by editing $/.ssh/known_hosts to remove the line for or letting an SSH utility do it for you with ssh-keygen -R įrom here, record the updated key either by doing it yourself with ssh-keyscan -t rsa > ~/.ssh/known_hosts Clients remember the host key associated with a particular address and refuse to connect if a host key appears to change. You are connecting via the SSH protocol, as indicated by the ssh:// prefix on your clone URL. We are not using SSH keys to connect to this repository, so I’m not sure why Git is checking for one on this particular machine. However, when running on one of my machines I get the following error: Usually after running this command Git will prompt for the user’s password, and then run the cloning. This has worked fine for most of my team members. I am using the following format for my command: git clone ssh:// /repository.git I am trying to connect to a remote Git repository that resides on my web server and clone it to my machine.