Recent content by SteveL132

The link to the Plesk Deployment Guide given in the original post, https://docs.plesk.com/current/plesk-deployment-guide/, doesn't work - gets a 404. I can't figure out what this link should be.

Well, after several days, there is indeed one ban action in the log! Perhaps I should declare success and move on.

Normally by this time the log would be full of ban/unban actions. Nothing has been added after the initial startup, so something is still not working.

Ok, I found a solution for the missing log. fail2ban's default location for the log is SYSLOG, but I can't find documentation on what that means, exactly. This used to generate fail2ban.log in /var/log - it no longer does. So I created /etc/fail2ban/fail2ban.local with the following content...

Not very nice - that "iptables --flush" locked me out of SSH as it deleted the rule that allowed my IP in. Luckily I figured out how to recover from Plesk Panel. Also, the yum commands are unnecessary (I had done a yum update this morning anyway.) You seem to be under the misconception that I...

I understand it well. Please note that I said that Plesk defined everything - I didn't change it. It was all working great until 12.0.18. Don't be distracted by the definitions of the jails - the bigger problem is that none of the jails seem to be doing anything and the log file is empty. Before...

All of the jails are defined by Plesk - I didn't create any of them. I just selected fail2ban from the available modules Plesk offered and installed it. It was working fine until 12.0.18 - and clearly I am not the only one experiencing this. Plesk's installation of fail2ban creates fifteen...

So you don't think a reading of 25 million percent is a problem? I already noted that the actual CPU usage was low, but Plesk presented an absurd reading and indicated it was a problem.

The problem is that the log is completely empty. loglevel is set at 3 (INFO) which should show everything. I get some warnings if I restart the service from the console: Starting fail2ban: WARNING 'ignoreregex' not defined in 'Definition'. Using default one: '' WARNING 'logpath' not defined in...

Interesting clue - when I restart fail2ban, I get an email about the recidive jail starting but none others.

A few hours later and it's back to normal. My guess is that the CPU monitoring gets confused right after a reboot.

No, I never did solve it and I can't tell if fail2ban is working as I don't see any IPs listed as banned, where I used to see quite a few.

I rebooted my CentOS 6.6 system running Plesk 12.0.18.25 after doing an update that included the kernel. The system seems to be running fine (after an initial scare where Apache wasn't working right, but a service restart fixed that), but Plesk is claiming that the system's CPU usage is 25...

I recently went through the exercise of PCI compliance with Trustwave. First of all, you simply can't have the FTP port open or else you will fail the compliance check. SSH will also trigger complaints, which leaves out SFTP! So my solution was to disable FTP entirely and then to add a firewall...

On the other hand, the Logs tab under Banned IP Addresses is now empty. There used to be bunches of logs here...