Search results

Never mind, we've now added a surveillance routine for the /etc/fail2ban/filter.d/apache-badbots.conf file. If it is replaced or modified, we'll automatically replace it with our master copy again and reload Fail2Ban. Problem solved.

It seems that it gets overwritten with a "wrong" timestamp, too. I am sure I had an updated apache-badbots.conf from Aug 27 on one machine where today an update was done. After the update to 18.0.63 #3 the timestamp was Aug 19, and the content was again the version from the article I once wrote...

I can positively say that the update overwrites a customized apache-badbots.conf file. When I realized I updated all these files yesterday with our custom setup. On one server that updated to 18.0.63 #3 today I again see this content: # Fail2Ban configuration file # # Regexp to catch known...

Nope, that's not possible, because the "thesis..." bot in the custom section is an example that is not part of the official file. It's not a big problem, the file is fine in general. There are some things that can be improved such as the regex that @Kaspar@Plesk once suggested ( failregex =...

Ouch, yes, it seems at least one of the recent updates has replaced the file. The new version is "ok", but it seems someone used the version form my article How to Avoid High CPU Load & Block Bad Bots with Plesk - Plesk . This is valid, but we, too, have customizations in addition to what's...

You cannot import components of a backup set separately.

What kind of help is required? https://support.plesk.com/hc/en-us/articles/12377673252759-How-to-rerun-daily-maintenance-tasks-separately-for-Plesk-on-Linux https://support.plesk.com/hc/en-us/articles/12377063217431-What-is-the-Plesk-Daily-Maintenance-script

Please check Postfix Configuration Parameters "bounce_queue_lifetime" parameter in your Postfix configuration. It defines how Postfix treats mails. 4 or 5 days are industry standard, because sometimes receiving servers are unavailable, hence it makes sense to retry delivery for some while.

The relevant lines are: ... but I have not encountered the exact issue before. I believe that this is not about RAM, but about a disk access issue or disk space issue. Potential further steps: Verify that SELinux allows access to the MariaDB files. If it set to "enforcing" test to change it to...

Let's have a look at what's been logged during the start attempt of the MariaDB service, e.g. # journalctl -u mariadb.service --since today

I think it is questionable if this is really a bug. It may be a deficiency that stats are not included in migration, but maybe rather a feature request to include them than a bug. There will also be users who want it exactly the way that on a new server traffic statistics start counting from...

Not being able to start Fail2Ban can have all kinds of reasons. When you run # service fail2ban start it will normally tell you why it won't start. If you don't see anything, run # service fail2ban status afterwards, then you can normally see an error message line in the output why it does not...

That's not the same. Even if no issues are found, the port link and configuration between Apache and Nginx might be broken. It normally helps to run # plesk repair web all (without -n, so that it really reconfigures all necessary files). I first observed this necessity after migration from...

In that case: # plesk repair web all

This means that Apache is not running. Nginx might, but your Apache is not online. For that reason sites not using proxy mode work, because there Apache is not needed. So check this: # service httpd status and restart with # service httpd restart it will also show you why it doesn't start. If...

Cloudflare does not use Google IP ranges, but Google does. If you want your website indexed in Google, do not block the Google IP ranges.

Could you please provide a log excerpt of the 403 error where it states the rule ID? Please also show which IDs were excluded.

As the error indicates a JavaScript issue, it might be caused by cached data. Clearing the browser cache could be enough to solve it.

Does the subscription have permissions to manage mail accounts?

@ksa616 The website can continue to work, but there won't be updates to PHP, Apache, Nginx etc. Mail can continue to work, but if something doesn't, you'll be on your own on the operating system level. No statistics either. SSL will continue to work until a renewal is up. Backup: No it will not...