Operations

Troubleshooting

“Scheduled scans may not be running.”

WP-Cron only runs when the site has visitors. Set up a server cron job as described in Settings → Tools. See Running scans from the server cron.

“The site could not be reached for the external check”

Some hosts block requests from the server to itself (loopback). Previous results are kept and an informational finding is shown. Ask your host to allow loopback requests, or disable the external checks.

“Modified file” findings after a deployment

Run a scan after the deployment, then approve the new state. See Approving the baseline after a deployment.

“Directory could not be read”

The path is outside open_basedir, does not exist, or is not readable by PHP. Files in this directory were not checked. Check the path, permissions and the open_basedir setting.

“File limit reached”

Scanning of the target stopped at “Maximum files per target”. Add exclude patterns for generated or vendor directories, or raise the limit under Settings → Checks.

“A check could not finish”

A check stopped with an error. Run the scan again. If the error persists, disable the check and report the problem.

My plugins are not listed under Plugins to scan

Until WordPress has checked plugin updates, plugins from WordPress.org cannot be told apart. Open Dashboard → Updates once and reload the settings page. Single-file plugins placed directly in the plugins folder are not listed.

Finding titles are in another language

Titles and descriptions of findings are saved in the language that was active when the scan ran. Scans from WP-Cron and WP-CLI use the site language, so they can differ from the language of your profile.