• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved File Check scans every domain separately instead of checking unique vhost directories

Azurel

Silver Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
18.0.80#1
I noticed that the (Repair) File Check feature scans every single domain individually, even if multiple domains point to the same vhost directory.

For example, I have several domains configured to use the same document root/vhost folder. The File Check runs the same scan multiple times for the identical files. Instead of taking a few minutes, the process can take several hours depending on the number of domains.

Example:

domain.com => /var/www/vhosts/domain.com
domain.de => /var/www/vhosts/domain.com
domain.es => /var/www/vhosts/domain.com
domain.fr => /var/www/vhosts/domain.com
and so on.

It would be much more efficient if File Check would detect identical document roots and scan each unique vhost directory only once, then associate the results with all domains using that directory.
 
I would really appreciate this optimization being considered. In my case, the affected vhost contains several million files, so running the File Check once per domain makes the process extremely slow. Scanning each unique vhost directory only once would make a huge difference.
 
Hi, @Azurel . The Repair File Check currently performs the check on a per-domain basis, rather than treating the document root itself. So, that's somehow expected behavior. Nevertheless, your point sounds legit to me, and I will double-check with our team if there's ground for improvement, how complicated that change will be, and whether it is justifiable. I will update you as soon as I get more details.
 
@Azurel , I just wanted to inform you that our team agreed that the behavior could be improved and we created internal task (PPP-72696). I cannot provide any ETA as of the moment, but I will follow up as soon as there's any update.
 
@Azurel , I am glad to inform you that the fix for this behavior is ready and will be published soon (likely in 18.0.81). Once released, the checks related to the document root will be run once in case several domains reuse the same document root The information related to the checks will be displayed only once for the first domain which uses the document root.
Thank you for bringing our attention to the issue and helping our team improve Plesk.
 
@Azurel , just to confirm the improvement in the directory scan behavior was introduced in Plesk Obsidian 18.0.81. Thank you once again. :)
Please let us know if you face any further issues.
 
Back
Top