• Resolved typeless

    (@jbalyo)


    One of my sites is getting this error:

    “Unable to open/wp-content/wflogs/ips.php for reading and writing.”

    Thousands of times an hour – it seems to be lagging the site and even once caused the server to overload and crash.

    /wp-content/wflogs/ looks like this:

    -rwxr-wr-x 1 ec2-user www attack-data.php
    -rwxr-wr-x 1 ec2-user www config.php
    -rwxr-xr-x 1 ec2-user www .htaccess
    -rwxrwxr-x 1 ec2-user www ips.php
    -rwxr-xr-x 1 ec2-user www rules.php
    -rwxr-xr-x 1 ec2-user www wafRules.rules

    As you can see, ips.php is set to 775 – any less restrictive and it would be freely editable by the public… what more does Wordfence want?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter typeless

    (@jbalyo)

    For anyone else struggling with this, changing ownership of the files in this directory to the user which is running the apache process solved the issue. After doing this, Wordfence automatically went through and changed permissions on these files to what they should be and the barrage of errors stopped.

    If you’re not sure which user is running the apache process, the following command should help in most cases:

    ps aux | egrep '(apache|httpd)'

    @jbalyo thank you, very helpful

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Unable to open /wp-content/wflogs/ips.php’ is closed to new replies.