Facebook
Twitter-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies! -
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
Resolved fail2ban configuration via CLI?
- Thread starter HostaHost
- Start date
Thanks! I was concerned about using these on a Plesk managed fail2ban instance since we don't know if it keeps its own version of the config in the psa db or elsewhere to facilitate rebuilding it if needed, but the commands on that page lead me to a kb article that had the relevant Plesk commands:
www.plesk.com
plesk bin ip_ban...
How to manage Fail2Ban and its jails in Plesk for Linux - Support Cases from Plesk Knowledge Base
How to manage Fail2Ban and its jails in Plesk for Linux - Support Cases - Plesk Knowledge Base
www.plesk.com
plesk bin ip_ban...
Thanks! I was concerned about using these on a Plesk managed fail2ban instance since we don't know if it keeps its own version of the config in the psa db or elsewhere to facilitate rebuilding it if needed, but the commands on that page lead me to a kb article that had the relevant Plesk commands:
How to manage Fail2Ban and its jails in Plesk for Linux - Support Cases from Plesk Knowledge Base
How to manage Fail2Ban and its jails in Plesk for Linux - Support Cases - Plesk Knowledge Base
plesk bin ip_ban...
Plesk created a nice GUI to manage fail2ban, it reads the plain text files located in /etc/fail2ban/* and shows them in the control panel.
There are some tables in the Plesk database related to ip_ban/fail2ban, but these are not used for config settings, so it's safe to use the original fail2ban commands, which are also a lot easier to remember.
Last edited:
Similar threads
