kex_exchange_identification: read: Connection reset by peer
APC UPS Data Center & Enterprise Solutions Forum
Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-09-1404:25 PM
kex_exchange_identification: read: Connection reset by peer
Recently, I installed 0G-9354A-01 cards in our Modular PDUs (PDPM288G6H). They are running MB 4.1.0 and PF 7.0.4
- AOS 7.0.4
- xRDP2g 7.0.4
Worked great.
However, over time, they have started to reject https sessions. I find that if I delete the X.509 certificate, and reboot (thus regenerating the cert), that I can then successfully connect via https. [http access continues to work fine through all this]
But I haven't found a similar trick for fixing ssh. [Teknet access continues to work fine.]
Has anyone found a work-around for this?
linux:~$ ssh -vvv sea-row2-a-pdu OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022 debug1: Reading configuration data /home/bsmith/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: /etc/ssh/ssh_config line 62: Applying options for * debug3: kex names ok: [diffie-hellman-group1-sha1,diffie-hellman-group14-sha1] debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/bsmith/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/bsmith/.ssh/known_hosts2' debug2: resolving "sea-row2-a-pdu" port 22 debug3: resolve_host: lookup sea-row2-a-pdu:22 debug3: ssh_connect_direct: entering debug1: Connecting to sea-row2-a-pdu [10.128.100.200] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0x10 debug1: Connection established. debug1: identity file /home/bsmith/.ssh/id_rsa type 0 debug1: identity file /home/bsmith/.ssh/id_rsa-cert type -1 debug1: identity file /home/bsmith/.ssh/id_ecdsa type -1 debug1: identity file /home/bsmith/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/bsmith/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/bsmith/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/bsmith/.ssh/id_ed25519 type -1 debug1: identity file /home/bsmith/.ssh/id_ed25519-cert type -1 debug1: identity file /home/bsmith/.ssh/id_ed25519_sk type -1 debug1: identity file /home/bsmith/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/bsmith/.ssh/id_xmss type -1 debug1: identity file /home/bsmith/.ssh/id_xmss-cert type -1 debug1: identity file /home/bsmith/.ssh/id_dsa type -1 debug1: identity file /home/bsmith/.ssh/id_dsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3 kex_exchange_identification: read: Connection reset by peer Connection reset by 10.23.49.102 port 22 linux:~$