Hi, I noticed some problems with fail2ban version 0.8.13 that is installed after following the perfect server installation documents. One of the problems was for creating a jail for sshd as apparently openssh have the nasty ability to change the way the write to the logfiles. The solution for that was actuall installing fail2ban 0.10 from source and i have it running perfectly now after some tweaking. This newer version of fail2ban also has the ability to check on multiple log files/log paths for applications. By default for nginx and apache2 it checks for *error.log and *access.log in the main log folder (in my case /var/log/nginx). Currently all vhost log files are written to their respective client folders, which is a good solution as clients can check their own logs. However it's not a so good solution if i want to use fail2ban to check for script bots, URL_fopen() and that kind of stuff. What i would like to see in a future release is that all the log files get symlinked into /var/log/nginx/ or /var/log/apache2/ in the form of something like [domain_name]-error.log and [domain_name]-access.log. Even for sysadmins that don't use fail2ban this would be a good solution for easier check of multiple logs against unwanted activities.