![]() I started digging into them by the proposals at the previous question mentioned above.ĭenyHosts uses ny to deny the access based on /etc/nf configuration file and the /var/log/auth.log log file analysis it does. Anyways, supposedly the programs that prevent access are the the prime suspects. Server was upgraded couple of days ago and this problem has started to occur after that. It has also DenyHosts as well as Fail2Ban to handle the flood of unauthorized login attempts. Quite often server is exposed to Internet so it has firewall to keep only selected ports open. Server has lot of webserver stuff and experiments. The server is Ubuntu 18.04.5 LTS was in a local network. I can login from other IP addresses as many times I like. The same limitation did not apply to other IP addresses. Whenever I deleted the entry row from the ny file (using different IP address on the client), I could login typically once from the originally failing host IP address. So, I found that the host was being added to /etc/ny. As the error message suggests, the connection was reset, so there is no connectivity issue and the connection was established ssh service is running on the server just fine. Ssh -v does not give any relevant additional information. Ssh_exchange_identification: read: Connection reset by peer The error message is the the same as in above question (ssh_exchange_identification: read: Connection reset by peer), when attempting to ssh the server. Below is the case description and the aswer. My reputation is too low to comment or provide answer suggestion. How to fix "ssh_exchange_identification: read: Connection reset by peer" error? Related very closely to question and answers like:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |