Fisheye 2.8 svn+ssh connections fail

Just upgraded to fisheye 2.8 and now all the connections to my repositories fail with the following error in the debug log:

Caused by: There was a problem while connecting to

at com.trilead.ssh2.Connection.connect(





... 31 more

Caused by: Key exchange was not finished, connection is closed.

at com.trilead.ssh2.transport.KexManager.getOrWaitForConnectionInfo(

at com.trilead.ssh2.transport.TransportManager.getConnectionInfo(

at com.trilead.ssh2.Connection.connect(

... 35 more

Caused by: The server hostkey was not accepted by the verifier callback.

at com.trilead.ssh2.transport.KexManager.handleMessage(

at com.trilead.ssh2.transport.TransportManager.receiveLoop(

at com.trilead.ssh2.transport.TransportManager$

... 1 more

Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn: E215003: Host key (' <ssh-rsa>') can not be verified.

at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.verifyHostKey(



at com.trilead.ssh2.transport.KexManager.handleMessage(

Anyone else seeing this or have a solution?

2 answers

1 accepted

Accepted Answer
0 votes

I would first check to see if your host key somehow changed based upon the message above since it unclear what fisheye is using for its ssh interface to figure out if incompatabilies exist.

I would next check that all the parameters are being passed as expected. I could not tell which svnkit and ssh versions are supported at the fisheye 2.8 version verses the previous versions. I suspect there was a change there as noted in the following url.

If you setup a new test respository, does that fail as well? If so and you feel it is not your parameters, then contact Altassian support.

Yes a new repository fails ... the URL noted doesn't help either but thanks for trying. The host key has not changed. The parameters being passed by the previous version of FishEye and the new ones are identical ... I double checked.

I was able to get mine working by running the jsvn command indicated in the above confluence link. By running it manually, it showed that my server was untrusted. It allowed me to trust the server permanently and everything started working properly.

The upgrade must have put some additional checks in place (or wiped out the ssh cache).


I have the same problem on my server.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

359 views 0 8
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you