• Resolved hypevent

    (@hypevent)


    The Wordfence Web Application Firewall cannot run. The configuration files are corrupt or inaccessible by the web server, which is preventing the WAF from functioning. Please verify the web server has permission to access the configuration files. You may also try to rebuild the configuration file by clicking here. It will automatically resume normal operation when it is fixed.

    We were unable to write to ~/wp-content/wflogs/ which the WAF uses for storage. Please update permissions on the parent directory so the web server can write to it.

    wflogs has a permission of 0644

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @hypevent, thanks for reaching out to us.

    It’s normally worth having permissions on your WordPress site’s directories set to 755 and that the owner on your WordPress root directory (and all contained directories) is www-data. Web servers such as Apache, Nginx, etc will require www-data to be an owner so that WordPress and plugins can update and run functions required to do so.

    If you have persistent problems with this file/folder, you can bypass this entirely by setting Wordfence to write to the MySQLi storage engine instead of a file if you prefer: https://www.wordfence.com/help/firewall/mysqli-storage-engine/

    Let me know how you get on!

    Peter.

Viewing 1 replies (of 1 total)

The topic ‘Firewall cannot run’ is closed to new replies.