Niels,
Digging some deeper. Found this post: http://stackoverflow.com/questions/6263630/jschexception-algorithm-negotiation-fail
There are a couple of places that SSH clients and servers try and agree on a common implementation. Two I know of are encryption and compression. The server and client produce a list of available options and then the best available option in both lists is chosen.
If there is no acceptable option in the lists then it fails with the error you got.
Not yet a sollution though why they are unable to agree on which encryptiion/compression to use.
Regards,
Ronald
[EDIT1]
Found this link http://blog.millard.org/2014/11/repair-synology-dsm51-for-use-as-linux.html Testing now.
[EDIT2] The link of Edit1 works. We now can SFTP again. I suggest you let your client do the steps. Beware the location where to put the text is crucial. Do it exactly as stated.
We have a working connection with our SFTP server on a Synology, but this does include a keypair. To get this to work I can recommend the following tutorial(s):
http://tinyurl.com/lngl8zr
You should SSH into the Synology and change some files (all explained in the tutorials). Only then this SFTP is really S(ecure).
Got confirmation from the other party that they have completed all the steps that you have suggested. There is now a Home folder on the Synology server which has both the known_hosts file and a public key (generated by me with puttygen)
The known hosts file consists of a single line:
192.168.xx.xx ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAkgyBI7tBKmQ+XkuFufUTeYJKiXBHZGZ44s8y3233XswD5JS/p/k+pAxM+fNn127s6hnX7oa/EHtnnMMvFof5MzsQSB7zyg3nDPgbX/IZG3gUMy3L7JzZexZagSRGSxn6LSwljclMx7j/ulSEeLL4ANsoIuDAYBlmkloqk/dLmPx8UvdlG3DPw/hMHtjkAa6ayi6sDDz76r23PI5AOEtawXeUiLD8X+sNUoibiMi8NX7TXBGAfh9gwP/E56B1Jxp0o4folHmiCxY2ZCH0epm+kX6P6JOe0F36xRYXfh8vmyZN4nDC9/UVnUgDjaBmMf3eHO1hjWjbv2PqICemTqhS2w==
I've generated my own private key and use the same known_hosts file in the settings. When trying to connect to the SFTP I get the following error. Is there any error you see in these steps or is there still something wrong in the configuration possibly?
com.jcraft.jsch.JSchException
Algorithm negotiation fail com.mendix.core.CoreRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: JschException occured when opening sftpSession. at com.mendix.core.component.InternalCore.execute(InternalCore.java:274)
Caused by: com.mendix.systemwideinterfaces.MendixRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: JschException occured when opening sftpSession. at com.mendix.core.actionmanagement.ActionManager.executeSync(ActionManager.java:217)
Caused by: com.mendix.systemwideinterfaces.MendixRuntimeException: JschException occured when opening sftpSession. at com.mendix.util.classloading.Runner.doRunUsingClassLoaderOf(Runner.java:43)
Caused by: JschException occured when opening sftpSession. at sftpconnection.helpers.HandleFileSftp.createSFTPChannel(HandleFileSftp.java:42)
jce_policy-8.zip
http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html
Just overwrite the files with the ones in the ZIP file
Tested already!