• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

SSH Last failed login: How to Improve security ??

Peter_R

Basic Pleskian
Hello i have a fresh Host Edition Installation and it was runing for about a week.
This is my second time i logged in to my server using SSH this week, and i noticed alarming message.

"Last failed login: Sun Jan 31 22:32:35 EST 2016 from xxx.xxx.142.71 on ssh:notty
There were 42278 failed login attempts since the last successful login."

Looks like there are a lot of hits on my server SSH port.

How can i increase the security to prevent hacking or someone trying to abuse my ssh connection?
Any advise?

I am newbie.
Thanks
 
Thank you for your reply
very helpful

also would be ok to change SSH port under Centos7 ? or not recommende?
i wonder if port change might affect any Plesk Functionality ?

Thanks
 
Hi,
would be ok to change SSH port under Centos7

I've changed the ssh-Port to an unusual port (in /etc/ssh/sshd_config). I closed port 22 in the firewall an opened the "unusual" port.
Additional I add a "special" user with a normal shell (/bin/bash) who is allowed to login. "root" is disabled to login via ssh on default.

fail2ban is a good choice too. ;-)

best regards
Holger
 
Thank you i used fail2ban and seems to be under control , ips get banned and if someone is persistent i am adding their ip to block list on my Zywall :)
 
Back
Top