Bobcares

Plesk Fail2ban: How to Setup

by | Jan 24, 2024

Learn all about using Plesk & Fail2ban to protect your servers. Our Plesk Support team is here to help you with your questions and concerns.

Plesk Fail2ban: How to Setup

Safeguarding our server from brute force attacks has become a norm in today’s digital world.

Fail2Ban is a powerful tool that offers help. It automates monitoring log files for suspicious patterns and taking proactive measures to ban potential threats.

Plesk Fail2ban: How to Setup

Today, we are going to take a look at setting up Fail2Ban on our OVH VPS.

  1. To begin with, we have to log into our Plesk server via the following URL. We have to replace the X’s with our server’s IP address.

    https://XXX.XXX.XXX.XXX:8443

  2. Then, head to “Tools & Settings” and select “Updates & Upgrades”.
  3. Now, click on “Add/Remove Components” and select ‘Fail2Ban’ from the available components. This will start the installation process.
  4. Next, click ‘Continue’ to proceed with the installation process.
  5. Once completed, we can access Fail2Ban via Plesk > Tools & Settings > Address Banning (Fail2Ban).

How to Set Up Fail2Ban for Automatic IP Banning

  1. First, head to “Tools & Settings” and select “IP Address Banning (Fail2Ban)” in the Security group.
  2. Now, we can enable the intrusion detection checkbox to activate the Fail2Ban service.
  3. Furthermore, we have to specify settings like IP address ban period, time interval for detection, and the number of failures before banning an IP.
  4. Finally, click ‘OK’ to apply the configuration.

How to Manage IP Addresses Manually

While Fail2Ban offers a GUI for viewing and whitelisting IP addresses, adding an IP manually requires SSH access.

We can view all Fail2Ban Blacklist IPs with this command:

sudo iptables -nL

We can manually block an IP as seen here:

sudo fail2ban-client set JAILNAME banip IP ADDRESS

Here, we have to replace JAILNAME with the specific jail name and IP ADDRESS` with the IP we wish to ban.

Furthermore, we can view our Jail’s status:

fail2ban-client status

Our experts recommend being cautious to avoid accidentally banning our IP Plesk Supportduring this process.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to set up Fail2ban while using Plesk.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF