• Resolved htz77

    (@tzeldin88)


    On one of my sites, the Sucuri plugin’s Core Integrity scan finds one file — the Wordfence Firewall file (wordfence-waf.php), but the MARK AS FIXED action always fails. After each try, it shows a message at the top of the screen saying “Sucuri: 0 out of 1 files were successfully processed.” And by the way, this message has a GREEN vertical-bar on the left, though it’s clearly a FAILURE message.

    Hosting: GoDaddy cPanel/shared

Viewing 6 replies - 1 through 6 (of 6 total)
  • hjgower

    (@hjgower)

    I am having the same issues on multiple files, won’t fix any of them when I try to mark them as fixed.

    Mediatemple hosting, Plesk

    yorman

    (@yorman)

    The color of the bar in the alert message is irrelevant. The file is not being marked as fixed because the cache file or the directory where the cache file is supposed to be is not writable. The file is usually placed here [1] please be sure that this directory is writable so the plugin can write into that file.

    [1] /wp-content/uploads/sucuri/sucuri-integrity.php

    Thread Starter htz77

    (@tzeldin88)

    Hi yorman, Thanks for writing back on this!

    So, on my server my sucuri-integrity.php is 644 and my /wp-content/uploads/sucuri is 755, so both exist and are writable. However, while checking this, I noticed that Sucuri’s Data Storage Path is wrong — it shows a path for an old server. This means the plugin shows all the settings files as Exists:NO and Writable:NO.

    To update the Data Storage Path, I added a constant to my wp-config as
    define(‘SUCURI_DATA_STORAGE’,’/path/to/my/wp-content/uploads/sucuri’);

    But this did not change the Data Storage Path, as shown on the plugin’s Settings > General screen. It still shows the old path. Is it cached somewhere? How can I update this?

    keysnparrots

    (@keysnparrots)

    I’m having the same problem as tzeldin88 after moving a site. I have also added a setting for SUCURI_DATA_STORAGE in wp-config but it is being ignored.

    It’s a little disappointing to see that tzeldin88 hasn’t received a response to this in over a week.

    keysnparrots

    (@keysnparrots)

    I found the sucuriscan_datastore_path value in wp-content/uploads/sucuri/sucuri-settings.php and changed it manually there. This fixed my problem.

    So there’s obviously a bug, in that the wp-config SUCURI_DATA_STORAGE setting is ignored. Maybe it’s supposed to be SUCURISCAN_DATASTORE_PATH to match the value name in sucuri-settings.php?

    Thread Starter htz77

    (@tzeldin88)

    @keysnparrots — thanks, that worked for me too.
    @sucuri — Seems like a bug here, that the plugin fails to read the SUCURI_DATA_STORAGE constant set in wp-config.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Core Integrity > mark as fixed = FAIL’ is closed to new replies.