• Resolved Ron

    (@donniepeters)


    After the most recent updates to Wordfence 6.3 I am unable to activate the Wordfence Firewall and Extended Protection. The error message I am getting on the Firewall Page is:

    “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.”

    When I look at the Directory permissions they are set at 0755 for both the wp-content and wflogs. Comparing to other sites on other servers I see that this is the same as some and others use 0705. I have tried changing to 0705 and it makes no difference.

    How can I enable the Firewall? I have tried everything to no avail.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi,
    Setting the permissions for “wp-content” as “755” should be fine, could you please check the owner/group for this directory and make sure it’s the same as your web server user? (it should be something like www-data for Apache on Ubuntu for example).

    Thanks.

    Thread Starter Ron

    (@donniepeters)

    I’m sorry, perhaps I am misunderstanding your response but as I stated in my post the directory permissions for wp-content ARE set at 755 and yet the Firewall is not working.
    And yes the owner/group for this directory IS the same as the web server user. I have run Wordfence on the ONE site since last March and the Firewall has worked fine until the last two weeks. Nothing has changed as far as the directory structures and when I compare the directory permission to 4 other sites that I have run Wordfence on for a number of years without problems the permissions are all the same so I am at a loss as to why I am unable to activate the Firewall.

    Please advise me how to fix this issue that has only been a recent issue.

    Try to rename “/wp-content/wflogs/” directory to something else, like “wflogs-backup” for example, and reload the Firewall Settings page, this should force the plugin to re-create this directory again, you can double check that using any FTP client to make sure “wflogs” directory has been created or not.

    Thanks.

    Thread Starter Ron

    (@donniepeters)

    Thank you for your response. I did as you suggested and this did correct the problem.

    I notice that in the wflogs-backup folder there are several files named .nfs… that appeared around the time the Firewall stopped working that do not show in the newly created directory.

    But the problem is resolved so thanks for your help.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Firewall not enabled after update’ is closed to new replies.