Renu Fulmali
12/04/2025, 9:57 AMkapa.ai
12/04/2025, 9:57 AMssh-rsa as its host key algorithm (serverProposal="ssh-rsa"). - The client (jsch) is proposing only newer algorithms (ssh-ed25519, ecdsa-*, rsa-sha2-*) and not ssh-rsa (jschProposal=...). As a result, host key algorithm negotiation fails: JSchAlgoNegoFailException: Algorithm negotiation fail: algorithmName="server_host_key". From the Airbyte side: - There is a known issue where SFTP connections fail because of incompatible SSH algorithms stemming from the underlying JSch library, and this was fixed by switching to a more modern fork (mwiede/jsch) in the SFTP connector. [[SFTP algo issue](https://github.com/airbytehq/airbyte/issues/60850)] - That issue describes the reverse situation (server only accepts newer RSA-SHA-* and not ssh-rsa), but the root cause is the same: JSch’s supported host key algorithms and the server’s supported algorithms don’t overlap. [[SFTP algo issue](https://github.com/airbytehq/airbyte/issues/60850)] Given the knowledge sources: 1. The docs and forum posts show that Airbyte’s SSH-based connectors rely on specific key formats/algorithms (e.g., RSA keys in PEM for SSH tunneling or SFTP) and are sensitive to SSH implementation details. [[SingleStore SSH](https://docs.airbyte.com/integrations/sources/singlestore#connecting-with-ssl-or-ssh-tunneling); [SFTP docs](https://docs.airbyte.com/integrations/sources/sftp)] 2. The only explicit algorithm-compatibility fix mentioned is for the SFTP source and was implemented in a specific PR. [[SFTP algo issue](https://github.com/airbytehq/airbyte/issues/60850)] Because the knowledge sources do not show: - Which connector you are using for “iex/sfmc endpoints” (likely an SFTP/SFTP Bulk connector, but it’s not stated). - Whether that connector version already includes the updated SSH library (mwiede/jsch) or any configuration flags for enabling ssh-rsa. I can’t definitively say which exact Airbyte version/connector you need to fix this. Based on what is documented: - Your issue is an SSH host key algorithm compatibility problem between the Airbyte connector (via JSch) and the SFMC SFTP server. - A similar class of problem has been resolved for the SFTP source by updating the SSH library. [[SFTP algo issue](https://github.com/airbytehq/airbyte/issues/60850)] Next steps (within what the docs support): 1. Check your connector and Airbyte versions - If you are using the source-sftp connector, ensure you are on a version at or beyond the one that includes PR [60849], since that is where the SSH library was updated to fix algorithm negotiation issues. [[SFTP algo issue](https://github.com/airbytehq/airbyte/issues/60850)] - The knowledge sources do not list exact version numbers where this is included, so you may need to cross-check the connector version you run with the PR. 2. If upgrading is possible, upgrade Airbyte / the SFTP connector - The only documented fix for SSH algorithm negotiation failures in SFTP is via that library upgrade; there is no documented runtime setting in Airbyte to force ssh-rsa or change the host key algorithm list. [[SFTP algo issue](https://github.com/airbytehq/airbyte/issues/60850)] 3. If the problem persists or you are using a different connector (e.g., a custom SFMC connector over SFTP) - The knowledge sources do not provide further configuration options for SSH algorithms. In that case, you would likely need to: - Confirm in the Airbyte UI which connector you’re using and its exact version. - Open an issue or support ticket referencing the JSchAlgoNegoFailException and the known SFTP/JSch algorithm issue so the Airbyte team can verify if the same fix needs to be applied to that connector as was done for source-sftp. [[SFTP algo issue](https://github.com/airbytehq/airbyte/issues/60850)] Because the knowledge provided stops at the SFTP connector fix and does not mention SFMC‑specific endpoints or configuration toggles for SSH algorithms, I can’t give a more precise, connector-specific remedy beyond upgrading and, if necessary, raising this as a bug with the exact connector name and version.