BPS Pro flagging RunCloud-related entries

Home Forums BulletProof Security Pro BPS Pro flagging RunCloud-related entries

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #46068
    Syxguns
    Participant

    Hi,

    I’m trying to get BPS Pro to stop flagging RunCloud‑related entries in the PHP Error Log, but I’ve run into a problem.

    According to the documentation, there should be a PHP Error Log Whitelist option where I can add strings to ignore. However, in my installation, that whitelist field does not appear anywhere in the PHP Error Log page or in the BPS Pro menus.

    Here’s what I’m trying to accomplish:

    RunCloud writes several informational/debug lines into the PHP error log

    BPS Pro detects these entries and displays warnings

    I want BPS Pro to ignore these RunCloud entries

    But the whitelist option shown in the documentation does not exist in my UI

    Environment details:

    WordPress version: 7.0

    BPS Pro version: 17.6

    PHP version: 8.3

    Hosting stack: RunCloud (NGINX/Apache hybrid)

    Example RunCloud log entries:

    [19-Jun-2026 22:49:31 UTC] [RunCache] Using cache handler: runcloud-native
    [19-Jun-2026 22:50:01 UTC] [RunCache] === ENTRY === advanced-cache.php loaded for:
    [19-Jun-2026 22:50:01 UTC] [RunCache] Using cache handler: runcloud-native
    [19-Jun-2026 22:51:49 UTC] [RunCache] === ENTRY === advanced-cache.php loaded for: /wp-login.php

    My question:

    Is the PHP Error Log Whitelist feature located somewhere else in the current version, or has it been removed/relocated? And what is the correct way to prevent BPS Pro from flagging RunCloud’s debug entries?

    Thanks for your help — just trying to make sure BPS Pro and RunCloud play nicely together.

    #46069
    AITpro Admin
    Keymaster

    The PHP error_log() function does not have whitelisting/filtering capability. error_log — Send an error message to the defined error handling routines. RunCloud is writing to your server’s default PHP error log using the PHP error_log() function. A PHP error log file should not be used as a log file, especially when log entries are being written continuously.

    Your only options would be:
    Turn off logging in RunCloud or if RunCloud has another option setting to change where log entries are sent, use that option setting instead.
    Turn off BPS Pro Dashboard Alerts. So that you do not see constant PHP Error Log Dashboard Alerts. BPS Pro menu > Display & Alert Options page > PHP Error Log: New Errors in The PHP Error Log Alerts option > change to: Display Alerts in BPS Only or Turn Off Displayed Alerts

    #46070
    Syxguns
    Participant

    Thanks again for the clarification earlier. I wanted to follow up with a bit more detail about my environment, since I’ve now confirmed what’s happening.

    I’m using RunCloud, but my server is not on the newer RunCloud stack that includes the RunCache Debug Mode or the additional logging controls. Because of that, I don’t have any UI options to disable or redirect the system‑level log entries that RunCloud writes to the default PHP error log.

    These entries aren’t actual PHP errors — they’re just routine system messages — but since they’re written continuously, the PHP error log is always active. Even after clearing the log and adjusting the alert settings, BPS Pro still detects these as “new errors.”

    The only way to prevent the persistent dashboard alert box from appearing was to set:

    PHP Error Log: New Errors in The PHP Error Log Alerts to Turn Off Displayed Alerts

    Everything else is working correctly; I just wanted to confirm that this is the expected behavior when the server environment is constantly writing to the PHP error log and the hosting panel doesn’t provide controls to disable that logging.

    Thanks again for your help.

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