• 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.

Action Log to file?

littlefrog

Regular Pleskian
I have fail2ban running on my server and i want to have it be able to check brute force attacks on the plesk panel login itself.

Action log today recorded 43,000 attempts to log in... would have been nice to ban after the first 4 but the results are in a database from what i can tell and not a physical file.

Does anyone know of a way to get fail2ban to read DB or to get action log into file so i can stop this from happening.
 
hmm... might work if... event handlers worked

according to the documentation

it doesn't work.

1) If you create Shell script EXACTLY as described and choose the event panel user failed login no vars are passed on to the shell script.

2) Because no vars are passed on there is no way to add to auto ban script.
a) No IP passed on
b) No user name passed on
 
file and output

Here is my shell script

#!/bin/bash
COMPDATE=`/bin/date`
echo "$COMPDATE - [${COMP_IP_ADDRESS}] - (${COMP_LOGIN_NAME}) User Authentication Failed" >> /var/log/psa-cp.log

Here is what it outputs

Tue Nov 6 17:37:37 CST 2012 - [] - () User Authentication Failed
 
anyone have any ideas when the Event Viewer will be fixed to work per the documentation?

Its clearly not passing variables on like it states it does.
 
Back
Top