The server's host key is not cached in the registry
Asked by Richard Kuechler:

Hello everybody,

I'm trying to fetch the commits list from the server via the GUI. After the click on a Fetch button, I get the "Fetching All" progress bar, which seems to work, but not too efficient.

Full output says I'm supposed to add the key fingerprint to cache; to do that, I need to type "y" to console window. But for obvious reasons, I cannot enter "y" into console window, since there is no console.

Here's the screenshot:

asdasd.png

Installed SourceTree version: 1.8.3.0

Thanks for the help in advance!

[](https://community.atlassian.com/t5/Sourcetree-questions/The-server-s-host-key-is-not-cached-in-the-registry/qaq-p/138931?attachment-id=1362){#link_11691a096ceeaa}  
[](/tnckb94959/attachments/tnckb94959/sourcetree-questions/4125/1/asdasd.png){#display_11691a096ceeaa_0}


Answers:
author: Damien Braz
body: **Hi Richard,**

**[Solution here](https://confluence.atlassian.com/sourcetreekb/trust-a-server-s-host-key-when-no-button-is-available-to-trust-it-788731545.html):**

The workaround is simple: just get SourceTree to use Embedded Git and get it to trust the host:

![](https://confluence.atlassian.com/sourcetreekb/files/788731545/788731544/1/1447126412598/trusthost1.png)  

And then change it back to System Git.

This should resolve the issue.

<br />

Best regards, Damien.

comments: author: Richard Kuechler
body: For some reason it doesn't help; I cannot see this window during the "Fetch" procedure. The situation is the same.


author: Damien Braz
body: Hmm... And, with this: <http://screencast.com/t/uOsYnPwdL>


author: Damien Braz
body: This is a known issue with SourceTree, refering to <https://jira.atlassian.com/browse/SRCTREEWIN-140>, here is the solution:

Solution:

* Open Command Prompt
* "C:\\Program Files (x86)\\Atlassian\\SourceTree\\tools\\putty\\plink.exe" [bitbucket.org](http://bitbucket.org)

Computer:

* Fresh install of Windows 10 Pro 64bit
* SourceTree 1.8.2.11
* Embedded git

I hope it will resolve your issue Richard! :smile:


author: Seth
body: You can also just launch SourceTree's Terminal, and run "ssh \<hostname\>".

You don't need to actually have the ability to connect via SSH - the ssh software will check the key first, so you can accept it before the server decides whether you're allowed to connect.


author: Luka Bu?i?
body: Latest Damien Braz solution with running plink.exe worked for me.  
I used plink.exe in my installed version of SourceTree folder and instead of "bitbucket.org" I connected to my problematic server and was able to finally allow it.  
After that all worked smoothly.


author: Heiko Guckes
body: For me, the trick was to switch from putty to open ssh in the general options.

comments: author: SDVISION
body: Hero! This fixed it for us after hours of frustration!


author: Robert Mellberg
body: Worked for me too!


author: Jens Petter Abrahamsen
body: Worked for me. Plink wasn't even installed (or could not be found).


author: Michael Kwak
body: This worked for me. Thank you for posting the answer.


author: Christopher Blanks
body: Thanks, this worked for me too, running version 3.1.3 on Windows 10.


author: alpereira7
body: Nice, thanks!


author: jmorenomarti
body: Worked for me too!!! Thanks!!!!!


author: meirav rath
body: Worked for me, SourceTree 3.3.8 on windows


author: William Haack
body: I am also stuck as Jeffery Brewster is.

Trying the command line (with a different, correct, path to plink) asks me to "login as:" after which it tells me that there are no supported authentication methods.(FATAL).

???

Not sure what to do.


author: jeffbrewster
body: Not solved. None of this works.   
Trying embedded git, gets me the same result. (No prompt). (makes me question the integrity of this software; why would it work differently on different systems of the SAME OS?? :: ( ))

<br />

Trying the command line (with a different, correct, path to plink) asks me to "login as:" after which it tells me that there are no supported authentication methods.(FATAL).  

Glad it is so painful to get this working on a brand-new, clean Win10 install....(great product! \<-sarcasm intended)


author: T
body: I did this (with embedded Git on) and it solved it for me:

1. copy the Git command from the message  
2. Actions --\> Open in Terminal  
3. insert the Git command  
4. the original message appears in the terminal and you can answer it