Plesk secutiy

[Rick-moma]

Hello, I have plesk 11.30 Update # 28 installed on CentOS 6.5. Today the mysql server has stopped on its own. I went into ssh and I rebooted from the terminal and now it seems to work.
In the system log I could not find useful information. I only see when it stopped.

Someone happened to this problem? Given that I recently upgraded from CentOS 6.4 to 6.5.

From the log I noticed that I have many attempts login as admin, attempts are made to ssh. I want to protect myself from this and searching the internet I find posts that say they protect themselves through the "IP access restriction management." I wanted to try but I'm not sure that "Add New Network" intends to enter the ip enabled to login.

In fact, I found many posts that say that after enabling "Restricted IP managment" no longer able to get into plesk.

How can I protect myself safely?

ty
r

 

[Lloyd_mcse]

Hi Rick,
I use the Restrict Admin Access, but then I have dedicated IP addresses for my ADSL/Fibre, and my server is just running my company websites (no Plesk customers).
I'd turn off password authentication for SSH and use authorized_keys, much safer.
I believe Parallels are adding a Fail2Ban module to Plesk soon, which will be a nice addition.
Regards

Lloyd

 

[IgorG]

Hi Rick,
I believe Parallels are adding a Fail2Ban module to Plesk soon, which will be a nice addition.

Yes, we are working on it.

 

[IgorG]

Fail2ban support is implemented already in Plesk 12.0 Preview. More details in Release Notes.