• 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.

Question What information is contained in the .rapid-scan-db folder?

WSNHosting

Regular Pleskian
Server operating system version
Almalinux 9.2
Plesk version and microupdate number
18.0.77 #4
What information is contained in the .rapid-scan-db folder?

Is it related to hardware, or is the information about something else?
 
@WSNHosting, the folder in question typically belongs to Imunify. As far as I can see it is used to store local file metadata and hashes. However, it might be worth to double-check that directly with CloudLinux as the vendor of Imunify. Is there any Plesk-related issue you are experiencing concerning that folder?
 
@WSNHosting, the folder in question typically belongs to Imunify. As far as I can see it is used to store local file metadata and hashes. However, it might be worth to double-check that directly with CloudLinux as the vendor of Imunify. Is there any Plesk-related issue you are experiencing concerning that folder?
It's from Imunify, right? It's not related to hardware RAID.
 
Dear Sebahat,

I find this a 'strange' answer. Immunify was installed earlier after a Plesk update without consent of server admins. Would be more customer friendly
if you would ask yourself what sort of info is in the .rapid-scan-db folder with the persons Plesk dealt with in the past of Cloudlinux in order to install Immunify without consent on of server admins on Plesk servers.....
 
@devnull , I am assuming you are referring to the issue during the Imunify extension replacement that occurred a year ago (June, 2025) when it was installed on servers that did not previously use Imunify. I am sorry if you were affected, but that issue did not affect all Plesk users, and I doubt that this case is related to it. If there's an actual issue I can double-check with CloudLinux, but to me this seems like a genuine question about what data is stored by the software's feature, which is not dependent on Plesk. Hence, it is better to be addressed by the vendor.
 
Back
Top