Facebook
TwitterHello all,
i'm running 12.0.18#34 on PCS dedicated server.
i recently discovered that some of the default jails on fail2ban that is shipped with Plesk 12 were not working correctly.
Let me explain what i mean.
For instance, the plesk-panel jail. The logs were parsed correctly, the command was successfully appended in iptables list, the fail2ban log was updated. Still, the intruder was not blocked. I kept reading "already banned" on the fail2ban.log but actually there was no blocking.
After some checks, i found out that fail2ban default configuration states SSH as default blocking port.
that means, the block was working but only for ssh hits. thus the plesk-panel admin page hits were passing through.
since i added port=http,https on jail.local > plesk-panel and did it a restart on fail2ban service, only then did it start to actually block incoming hits.
I think this should be verified by programmers group and maybe include a fix in some future minor update.
Hope this helps someone.
Regards,
Paul T
i'm running 12.0.18#34 on PCS dedicated server.
i recently discovered that some of the default jails on fail2ban that is shipped with Plesk 12 were not working correctly.
Let me explain what i mean.
For instance, the plesk-panel jail. The logs were parsed correctly, the command was successfully appended in iptables list, the fail2ban log was updated. Still, the intruder was not blocked. I kept reading "already banned" on the fail2ban.log but actually there was no blocking.
After some checks, i found out that fail2ban default configuration states SSH as default blocking port.
that means, the block was working but only for ssh hits. thus the plesk-panel admin page hits were passing through.
since i added port=http,https on jail.local > plesk-panel and did it a restart on fail2ban service, only then did it start to actually block incoming hits.
I think this should be verified by programmers group and maybe include a fix in some future minor update.
Hope this helps someone.
Regards,
Paul T
