Key exchange was not finished, connection is closed.解决办法

已于 2023-11-29 17:43:02 修改
阅读量6.6k 收藏 9
点赞数 3
分类专栏： Java 文章标签： linux ssh 服务器
于 2023-03-24 16:48:37 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_45266856/article/details/129754122
版权

错误

利用java连接Linux服务器中碰到错误：Key exchange was not finished, connection is closed.，导致服务器的连接失败，报错如下
在这里插入图片描述

原因

是ssh中的key交换算法不兼容导致

解决办法

修改配置文件

vi /etc/ssh/sshd_config

添加如下内容

KexAlgorithms diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group-exchange-sha256,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group1-sha1,curve25519-sha256@libssh.org

重启服务

systemctl restart sshd

启动报错

如果重新启动ssh出现错误Start operation timed out. Terminating.Failed to start openbsd secure shell server，可以尝试如下解决办法

关闭由systemctl控制的ssh启动

systemctl stop ssh.service

删除ssh的服务配置文件

rm /lib/systemd/system/ssh.service

重载systemctl和ssh服务

systemctl daemon-reload
systemctl start ssh.service

祝大家好运

毒爪的小新
关注
  • 3
    点赞
  • 踩
  • 9
    收藏
    觉得还不错? 一键收藏
  • 12
    评论
专栏目录
Key exchange was not finished, connection is closed
weixin_38203586的博客
03-07 1214
Caused by: java.io.IOException: Key exchange was not finished, connection is closed.”的解决方案。java代码连接Linux服务器时，报错“There was a problem while connecting to XX.XX.XX.XX。（1）在/etc/ssh/sshd_config文件最后一行加上（文字。（2）重启sshd服务。
Django 报错User.DoesNotExist: User matching query does not exist.解决办法
01-20
username = models.CharField(max_length=20, primary_key=True) password = models.CharField(max_length=20) # 修改在 admin 管理工具中的默认名，返回文章标题 def __str__(self): return self.username ...
Key exchange was not finished,connection is closed近期遇到这个错误sshd更新导致的
热门推荐
lingyudeai的博客
06-10 2万+
Key exchange was not finished,connection is closed cannot negotiate,proposals do not match. 近期遇到这个错误sshd更新导致的问题, 有说jekins的某某， 说虚拟机设置Host Key Verification Strategy选项改选为Non verifying VervificationStrategy就可以解决这个问题了！ 有说github的如下图： 我的是SSH漏洞更新导致的 ..
java.io.IOException: Key exchange was not finished, connection is closed.Cannot negotiate, proposa
最新发布
zhaofuqiangmycomm的博客
12-18 667
【代码】java.io.IOException: Key exchange was not finished, connection is closed.Cannot negotiate, proposa。
ch.ethz.ssh2报错java.io.IOException: Key exchange was not finished, connection is closed.
Python_Billy的博客
07-18 1804
ch.ethz.ssh2连接远程服务器报错java.io.IOException: Key exchange was not finished, connection is closed.
win7上面安装Jenkins.war之后，想要连接Linux服务器但却无法成功的解决方案
wise18146705004的博客
10-21 718
报错异常如下： 错误告警 Key exchange was not finished, connection is closed. java.io.IOException: There was a problem while connecting to 192.168.1.113:22 at com.trilead.ssh2.close 解决方案： 切换成信任的策略 ...
ganymed-ssh2连接服务器出现java.io.IOException: Key exchange was not finished, connection is closed.原因
u014639848的博客
09-29 1万+
java.io.IOException: Key exchange was not finished, connection is closed. at ch.ethz.ssh2.transport.KexManager.getOrWaitForConnectionInfo(KexManager.java:75) ~[ganymed-ssh2-262.jar!/:262] at ch.ethz.ssh2.transport.TransportManager.getConnectionInfo(Transp.
Key exchange was not finished, connection is closed Cannot negotiate, proposals do not match
DynastyTing的专栏
11-28 762
保存后，重启ssh服务 /etc/init.d/ssh restart。ubuntu系统报错。
连接服务器报错：Key exchange was not finished, connection is closed.
JAVA求生之路——博主406766467
10-25 2067
在/etc/ssh/sshd_config最后添加如下行内容解决问题。
ssh Key exchange was not finished sshd
hello
12-09 4524
报错： ssh Key exchange was not finished 则需修改sshd文件 链接：Key exchange was not finished,connection is closed近期遇到这个错误sshd更新导致的 - it610.com 需在 在/etc/ssh/sshd_config最后添加如下行内容解决问题 KexAlgorithms diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-he..
解决jenkins master挂载slave SSH Key Exchange not finished的问题
constant_rain的博客
01-05 2457
1.报错日志 [01/19/15 17:17:13] Opening SSH connection to 192.168.1.108:22. Key exchange was not finished, connection is closed. ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. java.lang.IllegalStateException: Connection is not
详解安装sql2012出现错误could not open key…解决办法
12-14
在安装SQL Server 2012时，可能会遇到“could not open key…”的错误，这通常是由于注册表中与SQL Server相关的键丢失或损坏导致的。这篇文章主要讲述了如何解决这个问题。 首先，问题的起因是由于误删了注册表中...
Could not load type System.ServiceModel.Activation.HttpModule解决办法
01-20
Could not load type ‘System.ServiceModel.Activation.HttpModule’ from assembly ‘System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089’.] 上网搜了下，问题产生的原因...
Could not generate DH keypair处理办法.rar
12-07
"Could not generate DH keypair处理办法.doc"文档很可能包含了详细的步骤来解决这个问题。通常，我们可以采取以下策略： 1. **增加DH密钥长度**：在服务器配置中，增大DH参数的大小，例如设置为2048位或更高。这...
MySQL错误“Specified key was too long; max key length is 1000 bytes”的解决办法
09-11
在MySQL中，当你尝试创建一个索引，特别是唯一索引（Unique Index）时，可能会遇到错误“Specified key was too long; max key length is 1000 bytes”。这个错误意味着你试图创建的索引键（key）超过了MySQL允许的...
Jenkins添加slave节点遇到的问题
Tsunami的博客
12-26 7628
slave节点镜像制作： 先下载带jdk8的镜像，在此基础上安装ssh，git等 dockerfile： 　　FROM 10.19.248.12:30100/library/gongan-jdk8:2.0 　　RUN rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm 　　&&am
安装在win10环境下的Jenkins添加本地虚拟机centos7作为从机遇到的问题，报错：SSH Connection failed with IOException: "Key exchange
wise18146705004的博客
04-16 8308
首先声明我的Jenkins版本是：2.31版。因为不同版本页面有所不一样 安装在win10环境下的Jenkins添加本地虚拟机centos7作为从机遇到的问题，报错情况如下： Searching for 192.168.0.104 in C:\Users\fushaolei\.ssh\known_hosts Searching for 192.168.0.104:22 in C:\Users\...
kex_exchange_identification: Connection closed by remote host
Dablelv 的博客专栏。
06-01 1303
在我的 Macbook 中使用 Github 下载与推送代码时，突然报了如下错误，之前还是好好的，真让人抓狂呀😫 git pull kex_exchange_identification: Connection closed by remote host Connection closed by 100.12.0.163 port 22 fatal: Could not read from remote repository. Please make sure you have
java.io.IOException: There was a problem while connecting to 172.24.16.53:22 at com.trilead.ssh2.Connection.connect(Connection.java:834) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:823) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:425) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:412) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: Key exchange was not finished, connection is closed. at com.trilead.ssh2.transport.KexManager.getOrWaitForConnectionInfo(KexManager.java:95) at com.trilead.ssh2.transport.TransportManager.getConnectionInfo(TransportManager.java:237) at com.trilead.ssh2.Connection.connect(Connection.java:786) ... 7 more Caused by: java.io.IOException: The server hostkey was not accepted by the verifier callback at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:548) at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:790) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:502) ... 1 more [06/03/23 15:31:33] Launch failed - cleaning up connection [06/03/23 15:31:33] [SSH] Connection closed.
06-04
这是在使用SSH连接时出现的错误消息。它指出连接无法建立，因为服务器主机密钥未通过验证。这可能是由于以下原因之一： 1. 服务器主机密钥已更改，但您的SSH客户端尚未更新该密钥。 2. 您的SSH客户端已被中间人攻击，攻击者试图欺骗您连接到一个虚假的服务器。 要解决此问题，您可以尝试以下操作： 1. 您可以尝试手动添加服务器的主机密钥到您的SSH客户端的已知主机列表中。您可以使用以下命令将主机密钥添加到列表中： ``` ssh-keyscan -t rsa <hostname> >> ~/.ssh/known_hosts ``` 其中，`<hostname>` 是您要连接的主机的主机名或IP地址。执行此命令后，再次连接主机时，您应该不会再收到该错误消息。 2. 如果您仍然无法连接到服务器，则可能存在中间人攻击。您可以尝试使用另一个网络连接或SSH客户端，并确保您连接到正确的服务器。另外，您可以尝试联系服务器管理员以确认服务器是否存在问题。
评论 12
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值