• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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