Most likely your server is listening in a different port, not the default 22
|
Note: The protection software "denyhosts" in the server put you to blacklist if you use more than three times wrong keys/password.
|
network closed remotely
Jerks!
Remove /etc/nologin if any -GM |
When using SSH this error may show it's ugly head on occasion. Many searches for the issues point to funny TCP connection tweaks or that sshd needs to be re-configured. This is not the case.
Symptoms Connecting to SSH servers gives this message: $ ssh atom@example.comOr maybe this if using verbose mode. $ ssh -v atom@example.comSolutions This can be caused by a number of issues, steps to test are as follows. Check /etc/hosts.deny and /etc/hosts.allow Many have reported configuring these to values properly has helped. However, we've seen this issue even when hosts.* files were not a factor. root@host # grep sshd /etc/hosts.allowMissing Dependencies This one typically happens after a glibc or openssl upgrade. Many distros can install updates to glibc or openssl libs and not require a restart to sshd. On any distro you can recognize it when after an update, then use lsof to see where sshd has open files. Some will be pointed to DEL, because those libs were deleted on update. ~ # lsof -n | grep ssh | grep DELWhen an SSH connection comes in the sshd daemon forks and attempts to attach (ld) these lib files, and fails resulting in this error. Corrupted Fingerprint / Keys Some how one or the other of the fingerprints or keys has become corrupted (did you manually edit one of these files?). Remove the server-side fingerprint in the clients ~/.ssh/known_hosts and try again. When you re-connect you will be prompted to accept the host identity again. If you are able to access the machine another way you may want to back-out and re-create the server-side ~/.ssh/authorized_keys. Along the same lines as this issue, if the files /etc/ssh/*key* are removed and sshd is not restarted then this error will show up too. Check for the key files in the sshd configuration directory. Heavy Server Load Have also seen this happen when server was under heavy load from for example, brute force attack. Increase the amount of connections sshd can run. root@host # grep MaxStartups /etc/ssh/sshd_config~~~~~~~~~~~~~~~~~~~~~~~~~ Brayan Sneider Vargas Lozada COL - CR |
another solution...
if ↑ the post doesnt help u......just restart your server.! It will work.
|
I had a same issue (below) and fixed by adding the releavant network address in /etc/hosts.allow
I had a same issue (below) and fixed by adding the releavant network address in /etc/hosts.allow
[abc@host1~]$ ssh host2 ssh_exchange_identification: Connection closed by remote host Fix: Added entry as below in host2 /etc/hosts.allow file ALL: 10.48.0.0/13 |
All times are GMT -5. The time now is 09:36 AM. |