我的编程空间,编程开发者的网络收藏夹
学习永远不晚

解决ssh_exchange_identification:read connection reset by peer 原因

短信预约 -IT技能 免费直播动态提醒
省份

北京

  • 北京
  • 上海
  • 天津
  • 重庆
  • 河北
  • 山东
  • 辽宁
  • 黑龙江
  • 吉林
  • 甘肃
  • 青海
  • 河南
  • 江苏
  • 湖北
  • 湖南
  • 江西
  • 浙江
  • 广东
  • 云南
  • 福建
  • 海南
  • 山西
  • 四川
  • 陕西
  • 贵州
  • 安徽
  • 广西
  • 内蒙
  • 西藏
  • 新疆
  • 宁夏
  • 兵团
手机号立即预约

请填写图片验证码后获取短信验证码

看不清楚,换张图片

免费获取短信验证码

解决ssh_exchange_identification:read connection reset by peer 原因

服务器改了密码,试过密码多次后出现:

1
ssh_exchange_identification: read: Connection reset by peer

可以通过ssh -v查看连接时详情

OpenSSH_6.6.1, OpenSSL 1.0.1k-fips 8 Jan 2015
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 56: Applying options for *
debug1: Connecting to xxx [xx] port 22.
debug1: Connection established.
debug1: identity file /home/yanue/.ssh/id_rsa type -1
debug1: identity file /home/yanue/.ssh/id_rsa-cert type -1
debug1: identity file /home/yanue/.ssh/id_dsa type -1
debug1: identity file /home/yanue/.ssh/id_dsa-cert type -1
debug1: identity file /home/yanue/.ssh/id_ecdsa type -1
debug1: identity file /home/yanue/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/yanue/.ssh/id_ed25519 type -1
debug1: identity file /home/yanue/.ssh/id_ed25519-cert type -1

最后找打解决方法:

vi /etc/hosts.allow

追加:

1
sshd: ALL

在这里插入图片描述

重启ssh就ok了

1
service sshd restart

报错信息:
 ssh_exchange_identification: read: Connection reset by peer

[root@test2 ~]# ssh root@192.168.2.128
ssh_exchange_identification: read: Connection reset by peer

报错分析:
 -v:表示查看连接的详细信息

[root@test2 ~]# ssh -v root@192.168.2.128
OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 58: Applying options for *
debug1: Connecting to 192.168.2.128 [192.168.2.128] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.4
ssh_exchange_identification: read: Connection reset by peer

解决方法:
1.在要连接的主机128上修改配置文件

[root@localhost ~]# vim /etc/hosts.allow

sshd:ALL //允许其他所有ip主机连接本机

[root@localhost ~]# systemctl restart sshd

提醒:
 若是要限制只有某些IP地址可以连接该主机,则在/etc/hosts.allow文件中添加允许的主机IP(如:sshd:192.168.2.130:allow),然后再到/etc/hosts.deny文件中添加“sshd:ALL”拒绝所有(除了/etc/hosts.allow文件中允许的IP地址)就可以达到除了设置允许的IP地址可以连接,其他的IP主机都无法连接的效果。

相关博客: 基于Linux下限制指定用户或IP地址通过SSH登录(访问控制)

重新尝试连接128主机

[root@test2 ~]# ssh root@192.168.2.128
Last login: Thu Jun 18 11:42:17 2020 from gateway

[root@localhost ~]# ifconfig ens37
ens37: flags=4163 mtu 1500
inet 192.168.2.128 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::58f3:f0e0:999e:dc3c prefixlen 64 scopeid 0x20
ether 00:0c:29:48:a1:65 txqueuelen 1000 (Ethernet)
RX packets 6671316 bytes 1274253678 (1.1 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7124037 bytes 3235376682 (3.0 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

查看ssh成功连接的详细信息

登录后复制
[root@test2 ~]# ssh -v root@192.168.2.128
OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 58: Applying options for *
debug1: Connecting to 192.168.2.128 [192.168.2.128] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.4
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
debug1: match: OpenSSH_7.4 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.2.128:22 as ‘root’
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: compression: none
debug1: kex: curve25519-sha256 need=64 dh_need=64
debug1: kex: curve25519-sha256 need=64 dh_need=64
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:NPzH2XoAuBsa8cuKFIaVQRxHPXTsq397mZklQiPanAw
debug1: Host ‘192.168.2.128’ is known and matches the ECDSA host key.
debug1: Found key in /root/.ssh/known_hosts:9
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: gssapi-keyex
debug1: No valid Key exchange context
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure. Minor code may provide more information
No Kerberos credentials available (default cache: KEYRING:persistent:0)

debug1: Unspecified GSS failure. Minor code may provide more information
No Kerberos credentials available (default cache: KEYRING:persistent:0)

debug1: Next authentication method: publickey
debug1: Offering RSA public key: /root/.ssh/id_rsa
debug1: Server accepts key: pkalg rsa-sha2-512 blen 279
debug1: Authentication succeeded (publickey).
Authenticated to 192.168.2.128 ([192.168.2.128]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug1: Sending environment.
debug1: Sending env LANG = zh_CN.UTF-8
Last login: Thu Jun 18 13:33:49 2020 from 192.168.2.129

调整SSH配置文件中的连接数限制

出现SSH远程登录服务器失败,也可能是由于SSH连接数被限制了,导致无法连接。通常情况下SSH配置文件中的MaxStartups默认值是10,您可以运行下面命令查看连接数。

$ cat /etc/ssh/sshd_config | grep MaxStartups

增加SSH连接数
在这里插入图片描述

如果默认值不能达到要求,您可以将属性设置为更高的值。

安装缺少的依赖

如果缺少SSH服务所需的依赖项或库时,也会出现SSH远程登录服务器失败。在这种情况下,您可以考虑修复 Ubuntu / Debian 系统上显示的任何损坏的软件包。

$ sudo apt-get upgrade -f

对于 RHEL / CentOS 系统,只需升级系统即可。

$ sudo yum update

来源地址:https://blog.csdn.net/weixin_43214644/article/details/126429486

免责声明:

① 本站未注明“稿件来源”的信息均来自网络整理。其文字、图片和音视频稿件的所属权归原作者所有。本站收集整理出于非商业性的教育和科研之目的,并不意味着本站赞同其观点或证实其内容的真实性。仅作为临时的测试数据,供内部测试之用。本站并未授权任何人以任何方式主动获取本站任何信息。

② 本站未注明“稿件来源”的临时测试数据将在测试完成后最终做删除处理。有问题或投稿请发送至: 邮箱/279061341@qq.com QQ/279061341

解决ssh_exchange_identification:read connection reset by peer 原因

下载Word文档到电脑,方便收藏和打印~

下载Word文档

猜你喜欢

有关HikariPool-1 – Failed to validate connection com.mysql.cj.jdbc.ConnectionImp 错误的产生原因与解决方法

如果长时间静默没有数据库操作就报Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@72b70c61 (No operations allowed after con
2023-08-19

Win8系统发生蓝屏提示reference by pointer错误的故障原因及解决方法

故障原因分析:一般情况下这个蓝屏都是在看视频或者是玩游戏的时候出现的。解决方法:一、安全模式下测试:1、“Win键+R键”——“运行”——输入&
2022-06-04

Linux系统下Found a swap file by the name “xxx.swp“问题出现的原因及解决方法

情景再现 我在一次使用vim编辑文件的时候,习惯性的按了ctrl+s想保存,然后屏幕就卡住了,最后我使直接暴力推出了终端,再次编辑想保存的时候就出了下面的警告提示: E325: ATTENTIONFound a swap file by t
2023-08-25

编程热搜

目录