• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Input Howto secure a standard Postgres Port with Fail2Ban

hschneider

New Pleskian
This article describes how to add a Fail2Ban Jail for PostgreSQL:

Here the short version in english:

Create the filter file in
/etc/fail2ban/filter.d/custom-postgres.conf

with this content:

[Definition]
failregex = ^<HOST>.+FATAL: password authentication failed for user.+$
^<HOST>.+FATAL: no pg_hba.conf entry for host .+$
ignoreregex = duration:#
ignoreregex =

Save and restart Fail2Ban.

Add the Host ID to the Postgres Log by editing this file:
/etc/postgresql/10/main/postgresql.conf

Change log_line_prefix to
log_line_prefix = '%h %m [%p] %q%u@%d '

Save and restart Postgres.

Now go to Plesk's Fail2Ban Setup and create a new jail with this action:
iptables[chain="INPUT", name="PostgreSQL-Server", port="5432", protocol="tcp", returntype="RETURN", lockingopt="-w"]

Full config here:
plesk-fail2ban-postgres-jail.jpg

That'S it :)

-- Harald
 
Last edited:
Back
Top