Skip to content

Delete Putty Cache Keys (GitLab)

Sometimes you will get this problem when you try to connect into GitLab

The server’s host key is not cached in the registry. You have no guarantee that the server is the computer you think it is. The server’s rsa2 key fingerprint is: ssh-rsa 1024 cc:78:13:a3:68:a6:59:7e:b8:23:2d:13:3e:66:9b:b9 If you trust this host, enter “y” to add the key to PuTTY’s cache and carry on connecting. If you want to carry on connecting just once, without adding the key to the cache, enter “n”. If you do not trust this host, press Return to abandon the connection. Store key in cache? (y/n)

This will be problematic when you use GUI application like GitExtensions where you can’t enter “y” and it will wait until the user enter “y”. When something like this happen to you, you can try to remove the rsa2 key fingerprint from regedit directly. As you can follow this instruction:

  • Open regedit
  • Navigate to HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys
  • Right-click the entry (will have a name like rsa2@<port>:<address>)
  • Delete it

After that, you can try to pull repositories first and it will prompt you correctly then you can continue to what you need to do (pull, push) to GitLab.

You may also like...