Firewall wflogs folder path incorrect

  • Resolved Josh.biz

    (@joshbiz)


    7 years, 3 months ago

    After migrating a website to a new domain I can’t successfully activate the WordFence Firewall.

    I get “We were unable to write to /home/xxxxxxx/public_html/wp-content/wflogs/ which the WAF uses for storage. Please update permissions on the parent directory so the web server can write to it.”

    I don’t think the problem is with the permissions though. The problem is that the path is incorrect and still referring to the old domain. Where I have included x’s in the path shown above, this is not correct for the new domain. But I can’t seem to change this.

    I’ve tried reinstalling the plug-in (and using the ‘Delete Wordfence tables and data on deactivation?’ option) but it still keeps showing the wrong root folder name.

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

  • Hi @joshbiz,

    Could it be that you have the “WFWAF_LOG_PATH“ variable set in wordfence-waf.php?

    Or maybe it is caused by some caching mechanism. Have you checked with your hosting provider?

    Thread Starter Josh.biz

    (@joshbiz)

    I’ve tried amending the paths in wordfence-waf.php to the correct ones but this makes no difference. I still keep getting:

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

    The correct path is /home/ivanfisher/public_html/wp-content/wflogs/ (it seems to be using the path from the domain previously installed under).

    Reinstalling the plug-in (even with the option “Delete Wordfence tables and data on deactivation” makes no difference either.

    This incorrect path is coming from somewhere but not wordfence-waf.php.

    Hi @joshbiz,

    It’s possible that the code in “.user.ini”, “.htaccess”, and/or “php.ini” related to the firewall optimization still mentions the previous path.

    Could you please check if that’s the case?

    Thread Starter Josh.biz

    (@joshbiz)

    Thanks @wfyann – resolved.

    Yes, there was an auto_prepend_file entry still pointing to the old root address in user.ini, probably copied across from the old domain. As soon as this was updated, the firewall activated immediately.

    Many thanks for your help,
    Josh.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Firewall wflogs folder path incorrect’ is closed to new replies.