New answers tagged sshd
You can set the option UseDNS no in the file /etc/ssh/sshd_config on your server to tell sshd(8) not to do DNS lookups.
Sshd doesn't care where the connection is coming from, if it's configured to do a reverse DNS lookup, it does.
What's inhibiting SSH from shutting down is that there is someone actively using it. You can't stop the inhibition while still allowing people to login via SSH. If you want to override SSH blocking shutdown, but still have the OS check for other possible inhibitions, you can simply shutdown SSH manually first, and then continue with the the reboot: ...
I'm an idiot. I had some wacky iptables rules set up on my server. After clearing all those out, everything works fine. Sorry for the fuss.
If you can SSH to localhost, but you can't SSH from another machine, then either you changed the SSH configuration to forbid SSH from other machines, or there's a firewall that blocks incoming SSH connections. The firewall could be on the same machine, or on any hop between the client you're testing from and that server. If SSH works on the default port but ...
Server log says sshd: /etc/ssh/sshd_config: No such file or directory This means the the server is unable to open the file for some reason. Check if the file exists and if it has appropriate permissions (including SELinux labels) ls -lZ /etc/ssh/sshd_config should give you enough information to figure this out (restorecon /etc/ssh/sshd_config should ...
It's because of ip conflict, I have same kind of issue, you should not use the same ip for other vm's. Even if you delete it, ip won't be released. try with another ip in the same network it should work.
Once I faced some weird errors because commented lines were without space between the character # and the text. correct: # no default banner path incorrect: #no default banner path
It sounds like you have 2 devices with the same subnet. This generally works badly/unexpectedly. You need to have different subnets, or you have to disable ARP. eg. To disable ARP: echo 1 > /proc/sys/net/ipv4/conf/eth0/arp_ignore echo 2 > /proc/sys/net/ipv4/conf/eth0/arp_announce But I'm sure there's a better approach to whatever problem you have. ...
Update your client software version to support reasonable kex suite. It does not look like openssh, isn't it? The diffie-hellman-group1-sha1 is potentially vulnerable to Logjam attack and you should not use that. If you really need to, update server config /etc/ssh/sshd_config and add KexAlgorithms +diffie-hellman-group1-sha1 (for openssh-7.0+) or ...
Top 50 recent answers are included