SSH: client_loop: send disconnect: Broken pipe

При подключении по ssh получаю ошибку:
client_loop: send disconnect: Broken pipe

Началось с того, что поменял впн сервер. Сначала ошибка была с любого устройства: с 3 разных ПК и 2 смартфонов: с локалки, по 4ж и с работы. Почитал советы в интернете и здесь. Менял параметры ssh сервера (keepalive, tcp чего-то там), после чего перезапустил весь сервер. Заработало везде, кроме одной машинки. Она в одной локалке с сервером 192.168.*.* Доступ с этих айпи есть, все что можно было перезапускал.
ssh [email protected]
[email protected]'s password:
client_loop: send disconnect: Broken pipe
Если ввести неверный пароль пишет [Permission denied, please try again.] То есть доступ к серверу есть.

Версии клиента и сервера совпадают, обновлялся в начале ноября. К самому серверу подключаюсь по http без проблем. В чем еще может быть проблема?

Добавлено: на клиенте тоже пробовал менять настройки, чистил .ssh/known_hosts
Клиентский конфиг пустой, все закоментировано. Конфиг сервера

Port 22
AddressFamily inet
ListenAddress 192.168.8.23
ListenAddress 178.205.142.189

AuthorizedKeysFile      .ssh/authorized_keys
UsePAM yes
ClientAliveInterval 300

Subsystem       sftp    /usr/lib/ssh/sftp-server
GatewayPorts no
AllowTcpForwarding yes
LoginGraceTime 30
KeepAlive yes
Protocol 1,2
AllowUsers abc root

PermitEmptyPasswords no
ChallengeResponseAuthentication no
abc
ClientAliveInterval 300
А на клиенте если поставить ServerAliveInterval 100 или 200?
или соединяться
ssh -o TCPKeepAlive=yes -o ServerAliveCountMax=100 -o ServerAliveInterval=50 юзер сервер 
https://wiki.archlinux.org/title/OpenSSH#Keep_alive
To ensure a session is kept alive, only one of either the client or the server needs to send keep alive requests. If ones control both the servers and the clients, a reasonable choice is to only configure the clients that require a persistent session with a positive ServerAliveInterval and leave other clients and servers in their default configuration.

https://wiki.archlinux.org/title/OpenSSH#Connection_refused_or_timeout_problem

https://wiki.archlinux.org/title/OpenSSH#Broken_pipe
If you attempt to create a connection which results in a Broken pipe response for packet_write_wait, you should reattempt the connection in debug mode and see if the output ends in error:
vs220
ssh -o TCPKeepAlive=yes -o ServerAliveCountMax=100 -o ServerAliveInterval=50 юзер сервер
это не повляило

vs220
https://wiki.archlinux.org/title/OpenSSH#Keep_alive
отдельно ни один клиент не настраивал, отсальные как раньше работали "из коробки", так и работают.
vs220
connection in debug mode and see if the output ends in error
В дебаг режиме:
[[email protected] ~]$ ssh [email protected] -v
OpenSSH_8.8p1, OpenSSL 1.1.1l  24 Aug 2021
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 192.168.8.23 [192.168.8.23] port 22.
debug1: Connection established.
debug1: identity file /home/abc/.ssh/id_rsa type -1
debug1: identity file /home/abc/.ssh/id_rsa-cert type -1
debug1: identity file /home/abc/.ssh/id_dsa type -1
debug1: identity file /home/abc/.ssh/id_dsa-cert type -1
debug1: identity file /home/abc/.ssh/id_ecdsa type -1
debug1: identity file /home/abc/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/abc/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/abc/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/abc/.ssh/id_ed25519 type -1
debug1: identity file /home/abc/.ssh/id_ed25519-cert type -1
debug1: identity file /home/abc/.ssh/id_ed25519_sk type -1
debug1: identity file /home/abc/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/abc/.ssh/id_xmss type -1
debug1: identity file /home/abc/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.8
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.8
debug1: compat_banner: match: OpenSSH_8.8 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.8.23:22 as 'abc'
debug1: load_hostkeys: fopen /home/abc/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:XbMKEVZyMLP3nkSNMfKlJKlh1IQywLmJpbkWWQ4907c
debug1: load_hostkeys: fopen /home/abc/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host '192.168.8.23' is known and matches the ED25519 host key.
debug1: Found key in /home/abc/.ssh/known_hosts:5
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /home/abc/.ssh/id_rsa
debug1: Will attempt key: /home/abc/.ssh/id_dsa
debug1: Will attempt key: /home/abc/.ssh/id_ecdsa
debug1: Will attempt key: /home/abc/.ssh/id_ecdsa_sk
debug1: Will attempt key: /home/abc/.ssh/id_ed25519
debug1: Will attempt key: /home/abc/.ssh/id_ed25519_sk
debug1: Will attempt key: /home/abc/.ssh/id_xmss
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,[email protected],ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected]>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/abc/.ssh/id_rsa
debug1: Trying private key: /home/abc/.ssh/id_dsa
debug1: Trying private key: /home/abc/.ssh/id_ecdsa
debug1: Trying private key: /home/abc/.ssh/id_ecdsa_sk
debug1: Trying private key: /home/abc/.ssh/id_ed25519
debug1: Trying private key: /home/abc/.ssh/id_ed25519_sk
debug1: Trying private key: /home/abc/.ssh/id_xmss
debug1: Next authentication method: password
[email protected]'s password:
Authenticated to 192.168.8.23 ([192.168.8.23]:22) using "password".
debug1: channel 0: new [client-session]
debug1: Requesting [email protected]
debug1: Entering interactive session.
debug1: pledge: filesystem full
debug1: client_input_global_request: rtype [email protected] want_reply 0
debug1: client_input_hostkeys: searching /home/abc/.ssh/known_hosts for 192.168.8.23 / (none)
debug1: client_input_hostkeys: searching /home/abc/.ssh/known_hosts2 for 192.168.8.23 / (none)
debug1: client_input_hostkeys: hostkeys file /home/abc/.ssh/known_hosts2 does not exist
debug1: client_input_hostkeys: no new or deprecated keys from server
client_loop: send disconnect: Broken pipe

смущает одна строка:
debug1: pledge: filesystem full
Диски проверил, места много

Подключился с другого ПК, в приветствии пишет, что я все же логинился с того ПК, где сейчас Broken pipe
Last login: Fri Nov 19 21:24:04 2021 from 192.168.8.106
 
Зарегистрироваться или войдите чтобы оставить сообщение.