Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi @recepti2k,

    Such issue can happen if you moved the site to a new host or if you unintentionally deleted the wordfence-waf.php file.

    Can you confirm that you removed the “auto_prepend_file” directive from either file mentioned in this article (.htaccess or .user.ini or php.ini)?

    Thread Starter recepti2kcom

    (@recepti2k)

    Please do not expose yourself. I wrote to you, I use NGINX. This is not Apache. I checked php.ini at line 660 auto_prepend_file = and no values were set. I removed the plugin along with the residual entries in the database and the / www / wp-content / wflogs directory. However, the problem remains. Please give an adequate solution to the problem!

    Hi @recepti2k,

    If the error persists then there must be a reference to the wordfence-waf.php file somewhere.

    Have you looked for a .user.ini file?

    Could please:

    • Go to the Wordfence Tools page
    • Click the Diagnostics tab
    • In the Other Tests section (near the bottom of the page), click the link that reads “Click to view your system’s configuration in a new window“. This will open a Wordfence System Info page

    And then check the values associated with the following parameters:

    • Server API
    • Loaded Configuration File –> Is it the php.ini file you checked
    • PHP Version
    • auto_prepend_file
    • user_ini.filename –> Does the file specified there contain the auto_prepend_file directive?

    Hello!

    I hope we were successful in helping you resolve your issue with Wordfence! Since we have not heard back from you in the past 2 weeks I will now be marking this support thread as resolved. However, if we still haven’t resolved your issue please reach out to us as we would be more than happy to further assist you!

    Thanks and have a great day!
    Chloe

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘wordfence-waf.php problem’ is closed to new replies.