Skip to main content

Qlik

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
nbabu228
Contributor II
Contributor II
‎2023-03-27 01:36 AM

Error Algorithm negotiation fail

Hi All,

 

Plz help on this issue, I need establish sftp connect to put files on remote server.

 

I use tFTPConnection and I'm check "sftp support", authentication method is password.

 

The execute result is:

Exception in component tFTPConnection_1 (FTP)

com.jcraft.jsch.JSchException: Algorithm negotiation fail

at com.jcraft.jsch.Session.receive_kexinit(Session.java:604)

at com.jcraft.jsch.Session.connect(Session.java:334)

at com.jcraft.jsch.Session.connect(Session.java:194)

at pim_integration.ftp_0_1.FTP.tFTPConnection_1Process(FTP.java:818)

at pim_integration.ftp_0_1.FTP.runJobInTOS(FTP.java:5075)

at pim_integration.ftp_0_1.FTP.main(FTP.java:4554)

i tried some solution's but same issue facing...

0695b00000fIRTFAA4.png

Labels (6)
1,123 Views
3 Replies
Anonymous
Not applicable
‎2023-03-27 02:23 AM

Hello @nagendra babu​ ,

Regarding to the error log, the problem is that the algorithm doesn't compatible between the ssh client and server side.

The solution is to upgrade jsch jar by the below steps:

  1. download the jar from https://mvnrepository.com/artifact/com.jcraft/jsch/0.1.55
  2. update the jsch jar by open the Window->show view ->Talend->Modules in the studio, search jsch and click the ... button to update the maven URI with the downloaded jar

see https://help.talend.com/r/en-US/8.0/studio-user-guide/installing-external-modules-manually-using-modules-view0695b00000fIRWsAAO.png 

1,123 Views
0 Likes
Informatique1
Contributor III
Contributor III
‎2023-03-30 02:24 AM

I had the same issue.

Add some parameters in your advanced settings like here:

0695b00000fIovgAAC.png 

You can add more parameters to be sure, just check this link:

https://community.talend.com/s/article/Expanding-your-SFTP-security-algorithms?language=en_US

1,123 Views
0 Likes
Ross4
Contributor
Contributor
‎2023-09-18 06:20 PM

0695b00000oe4EbAAI.jpg 

As @BOBE Thomas​ mentioned above, I just added one line in client configuration and the issue got resolved.

 

If the problem is not resolved, you can dig a little more by changing the log4j to "debug" mode and evaluate how the client and server negotiate. You will see something like this:

 

 

 

[DEBUG] 12:19:41 Connection established

[DEBUG] 12:19:41 Remote version string: SSH-2.0-8.1.0.0_openssh GlobalSCAPE

[DEBUG] 12:19:41 Local version string: SSH-2.0-JSCH_0.2.1

[DEBUG] 12:19:41 CheckCiphers: chacha20-poly1305@openssh.com

[DEBUG] 12:19:41 CheckKexes: curve25519-sha256,curve25519-sha256@libssh.org,curve448-sha512

[DEBUG] 12:19:41 CheckSignatures: ssh-ed25519,ssh-ed448

[DEBUG] 12:19:41 ssh-ed25519 is not available.

[DEBUG] 12:19:41 ssh-ed448 is not available.

[DEBUG] 12:19:41 server_host_key proposal before removing unavailable algos is: ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256

[DEBUG] 12:19:41 server_host_key proposal after removing unavailable algos is: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256

[DEBUG] 12:19:41 server_host_key proposal before known_host reordering is: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256

[DEBUG] 12:19:41 server_host_key proposal after known_host reordering is: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256

[DEBUG] 12:19:41 SSH_MSG_KEXINIT sent

[DEBUG] 12:19:41 SSH_MSG_KEXINIT received

[DEBUG] 12:19:41 kex: server: ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group16-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1

[DEBUG] 12:19:41 kex: server: ssh-rsa

[DEBUG] 12:19:41 kex: server: aes256-gcm@openssh.com,aes256-cbc,rijndael-cbc@lysator.liu.se,aes192-ctr,aes192-cbc,aes128-gcm@openssh.com,aes128-cbc,3des-cbc

[DEBUG] 12:19:41 kex: server: aes256-gcm@openssh.com,aes256-cbc,rijndael-cbc@lysator.liu.se,aes192-ctr,aes192-cbc,aes128-gcm@openssh.com,aes128-cbc,3des-cbc

[DEBUG] 12:19:41 kex: server: hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,hmac-sha1,hmac-md5,hmac-sha1-96,hmac-md5-96

[DEBUG] 12:19:41 kex: server: hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,hmac-sha1,hmac-md5,hmac-sha1-96,hmac-md5-96

[DEBUG] 12:19:41 kex: server: zlib,none

[DEBUG] 12:19:41 kex: server: zlib,none

[DEBUG] 12:19:41 kex: server:

[DEBUG] 12:19:41 kex: server:

[DEBUG] 12:19:41 kex: client: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c

[DEBUG] 12:19:41 kex: client: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256

[DEBUG] 12:19:41 kex: client: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com

[DEBUG] 12:19:41 kex: client: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com

[DEBUG] 12:19:41 kex: client: hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1

[DEBUG] 12:19:41 kex: client: hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1

 

1,123 Views
0 Likes