• Resolved Starhorsepax2

    (@starhorsepax2)


    We manually updated the rules for this and dismissed it and thought that the end of it. But the message keeps coming back. It’s driving us nuts. How do we get rid of it?
    I imagine the reason it had issues updating was we’re battling slow site issues and 503 errors. But surely once we dismissed the notice it should’ve stayed gone at least until the next due scan.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @starhorsepax2, thanks for getting in touch.

    There’s a chance that the error is returning rather than failing to save its dismissed state.

    If you’re not seeing permission failures to either your database or files reported on your Wordfence > Tools > Diagnostics page, I would try navigating to your wp-content/wflogs folder via FTP or file manager. You should be able to delete the wflogs folder or its contents entirely and Wordfence should try to repopulate it within 30 minutes.

    It’s also worth checking that in addition to 755 permissions on your WordPress site’s directories, the process owner is also www-data.

    If you have persistent problems with this file/folder but don’t see connectivity or permissions failures/error messages in your Wordfence > Tools > Diagnostics page, you can bypass this entirely by setting Wordfence to write to the MySQLi storage engine instead of a file: https://www.wordfence.com/help/firewall/mysqli-storage-engine/

    I hope that helps you out!
    Peter.

    Thread Starter Starhorsepax2

    (@starhorsepax2)

    This appears to have worked. I hope it stays gone.

    Plugin Support wfpeter

    (@wfpeter)

    Thanks for the update @starhorsepax2 and I’m pleased to hear that it’s gone. If it does return at a later date, by all means open up a new topic (feel free to link to this one there as a follow-up) and we’ll be glad to look into a possible cause further for you.

    Peter.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘The last rules update failure warning WON’T GO AWAY’ is closed to new replies.