Search results

A great improvement on speed indeed! Just one adjustment to help avoiding matching the URL itself in requests: Without this, if you were blocking a bot called "spot" and you had a page with a referer that contained "spotting-birds-in-the-wild" you could accidentally trigger that just by...

As a quick update to this post, the regex above is a bit too greedy since it would effectively match results in the URL itself. For example, a URL such as "/spot/hello-world/ would be picked up and banned if the "spot" bot was included in the definition list. An updated version that fixes this...

No filesystem issues and the manual approach worked without a problem (no extra steps taken or needed) so we're going to hold off on using this for now in production environments.

Are you able to SSH or login to Plesk while the incidents are occurring or is this an "after hours" type of scenario each time?

Changed the failregex to the following otherwise it would never match user agent names with versions, URLs or anything else after them:

You're not entirely incorrect on this - I had to modify the failregex on the default one for it to work correctly.

The GUI tool failed two installs on AlmaLinux 9.3 with the local gpgkey path not found errors; ended up using the manual upgrade approach which pulls it from MariaDB and worked like a charm: [mariadb] name = MariaDB baseurl = https://dlm.mariadb.com/repo/mariadb-server/10.11/yum/rhel/9/x86_64...

Why not use the new MariaDB upgrade tool?

For shared web servers when using DNS externally and mail externally, we used the steps here to enable DKM and signing on all domains: https://support.plesk.com/hc/en-us/articles/12377279341975-How-to-enable-DKIM-signing-for-all-domains-on-Plesk-for-Linux- We then use this step to get the key...

To follow-up on this, running the two commands here https://support.plesk.com/hc/en-us/articles/12377279341975-How-to-enable-DKIM-signing-for-all-domains-on-Plesk-for-Linux- seem to successfully enable DKIM signing for all domains however if "Enable mail management functions in Plesk" is turned...

The article here https://support.plesk.com/hc/en-us/articles/12377279341975-How-to-enable-DKIM-signing-for-all-domains-on-Plesk-for-Linux- seems to suggest that with those two commands, keys would be generated for all domains on the server. Does this apply to mail sent via Postfix and PHP...

In this scenario, the Plesk mail server isn't used (mailboxes are external) so it's turned off via the Plesk GUI and DNS is external with no connection to Plesk. The servers provide shared hosting with hundreds of domains on each. We'd like messages that are sent from server scripts and postfix...

Username: TITLE 18.0.58 Upgrade throws error when directory is absent PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE OS: CentOS Linux 7.9.2009 (Core) Product: Plesk Obsidian 18.0.57 Update #5, PROBLEM DESCRIPTION Upgrade to latest version Plesk release on CentOS 7.9 and...

Try excluding common cache directories and logs from your backup set to help reduce the overall footprint. Consider using a background process that doesn't use a zip approach such as Acronis (works on both Windows and headless Linux).

Your mileage might vary but the upgrade script has been known to cause the Plesk install to get wiped under certain conditions so use it with extreme caution.

Do you have any backups set to run during that time?

This is a recent issue that returns the following:

We've seen issues with the script version but they weren't consistent enough to reproduce so our SOP from now on has been to use the manual approach.

It seems contrary to logic but the TLDR version is that CentOS 8 was very quickly made end of life while CentOS 7's end of life exceeds CentOS 8 and CentOS 7 continues to be supported until June 30, 2024 so because of that oddball situation, you are able to update to the current release on your...

Apart from the one-time issue with the Dr Web Updater (see link above for quick resolution), it sounds like you might have some other issues that are worth looking into which could be caused by repository updates unrelated to Plesk. It might be a good idea to tackle one at a time (for instance...