Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
im having a log prob with fail2ban and im looking for a way to clear all system and all domains logs completely. fail2ban is blocking a cloudflare ip and i cant seam to find where its reading it from.
I'd discourage flushing logs as some software might actually quit working if an expected log file cannot be found. You will also lose a lot of data that might prove as an important resource for solving other issues. Instead of flushing logs, your could rotate them with logrotate. But there is easy way to do it for all the logs on a system in a simple command. You'll have to know all log locations and instruct logrotate what to do with them seperately.
As an alternative: If you know that a cloudflare IP is blocked, you must also know what the IP is. Could you simply add that IP to fail2ban's whitelist?
all banned ip addresses are saved in the fail2ban.sqlite3 file located in /var/lib/fail2ban/fail2ban.sqlite3
Even if you clear all log files - fail2ban will recreate all banned ips out of the database after every sevice restart untill the bantime for the ip runs out! But first of all you need to find out why your cloudflare ip gets banned before doing anything else
I personally use my recidive jail with a bantime = -1 that means every ip in this jail is banned for ever - till the end of time or even if I will unban it manually
If you are using the standard recidive jail settings you only have to wait 7 days untill the ip gets unbanned. Of course you don't need to wait so long!
Here are 3 ways for solving your problem:
1. You are using the standard recidive jail settings? Perfect! Peters solution -using the whitelist option- is the best way for you. Put the ip on the whitelist and after 7 days you can delete it from it again because the bantime is running out.
2. You can clear the whole fail2ban log and also every banned ip from the fail2ban.sqlite3 database with the following steps: I don't prefer this solution in your case because you are resetting every banned ip - but its a good method to reset fail2ban to point zero.
service fail2ban stop
truncate -s 0 /var/log/fail2ban.log
rm /var/lib/fail2ban/fail2ban.sqlite3
service fail2ban restart
done!
don't worry - fail2ban recreates the fail2ban.sqlite3 file after restarting the service
3. You can also manually delete the ip from the database without loosing all other banned ips and if you don't want to use whitelisting: