HTAccess not found in plugins folder, pre-install filter causing resource limits usage

Home Forums BulletProof Security Pro HTAccess not found in plugins folder, pre-install filter causing resource limits usage

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #44018
    Iris
    Participant

    I have two questions I would greatly appreciate help on please.

    Today I/O Resource limits were reached for my site in cpanel.  At the same time the BPS Pro Security Logged the following:

    [Internal Usage: upgrader_pre_install Filter: Triggered | 12 Jul 2024 – 10:59 am]
    [Internal Usage: upgrader_pre_install Filter: Prior ARQ Cron Status: On | 12 Jul 2024 – 10:59 am]
    [Internal Usage: upgrader_pre_install Filter: ARQ Cron was turned Off | 12 Jul 2024 – 10:59 am]
    [Internal Usage: upgrader_post_install Filter: Triggered | 12 Jul 2024 – 10:59 am]
    [Internal Usage: upgrader_post_install Filter: Backup performed | 12 Jul 2024 – 10:59 am]

    What is the upgrader pre/post install about?  No plugins or themes required an update at this time?  Or is this some kind of update that happens normally in the background from WordPress/

    If so how can I prevent future hits on resources, ie what is it that I need to have whitelisted?

    Second, I have this message in the htaccess file editing box: “ERROR: An htaccess file was NOT found in your plugins folder”.  Deactivating/reactivating made no change.  I have deactivated the Plugin Firewall BP Mode WAF, then reactivated but no change.

    What can I do to fix?

    Thank you in advance.
    <h3></h3>
     

    #44019
    AITpro Admin
    Keymaster

    Those log entries occur when a WordPress, Plugin or Theme update occurs.  You can disregard the I/O resource limit tool unless your web host says this is actually a problem.  If they do say it is a problem then there is a problem with your host server configuration that your web host needs to fix and not a problem with BPS. BPS is performance optimized and uses very little resources.

    The Plugin Firewall problem sounds like another ModSecurity problem that is breaking the Plugin Firewall form. Contact your web host and ask them to fix this ModSecurity problem on your host server.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.