How to Resolve "com.sshtools.j2ssh" errorsIssue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> How to Resolve "com.sshtools.j2ssh" Errors Description When checking MID logs for issues related to SSH troubleshooting you may observe errors such as the following: Exception from SSH: java.io.IOException; The socket is EOF java.io.IOException: The socket is EOF at com.sshtools.j2ssh.transport.TransportProtocolInputStream.readBufferedData(TransportProtocolInputStream.java:187) at com.sshtools.j2ssh.transport.TransportProtocolInputStream.readMessage(TransportProtocolInputStream.java:234) at com.sshtools.j2ssh.transport.TransportProtocolCommon.readMessage(TransportProtocolCommon.java:1340) at com.sshtools.j2ssh.transport.kex.SshKeyExchangeFixedGroupDh.performClientExchange(SshKeyExchangeFixedGroupDh.java:162) at com.sshtools.j2ssh.transport.TransportProtocolClient.performKeyExchange(TransportProtocolClient.java:353) at com.sshtools.j2ssh.transport.TransportProtocolCommon.beginKeyExchange(TransportProtocolCommon.java:711) at com.sshtools.j2ssh.transport.TransportProtocolCommon.onMsgKexInit(TransportProtocolCommon.java:1295) at com.sshtools.j2ssh.transport.TransportProtocolCommon.startBinaryPacketProtocol(TransportProtocolCommon.java:1032) at com.sshtools.j2ssh.transport.TransportProtocolCommon.run(TransportProtocolCommon.java:388) at java.lang.Thread.run(Thread.java:748) Cause This is caused by the deprecated j2ssh library, which may still be in use by clients who existed pre-Eureka and never manually added the necessary property to switch to the new SNC SSH library. All clients are encouraged to switch to the SNC library. Solution The property can be added at the MID level or SSHProbe level. It's recommended to add the property at the probe level to prevent MID servers from somehow missing the property and causing issues. Add the use_snc_ssh parameter to the SSHProbe. Supporting documentation: https://docs.servicenow.com/csh?topicname=r_Parameters.html&version=latest Applicable Versions Any, if upgraded from a pre-Eureka instance. Additional Information Community article explaining some of the differences between the j2ssh and sncssh: https://community.servicenow.com/community?id=community_question&sys_id=04ec0b29db9cdbc01dcaf3231f9619eb