Wf causes Fatal error

  • Resolved WPwebbouw

    (@wpwebbouw)


    8 years ago

    After installing wf 6.1.3 on 2 sites and optimizing the Firewall I got on both sites a white screen with this error:

    Fatal error: Unknown: Failed opening required ‘/domains/domainname.nl/wordfence-waf.php’ (include_path=’.:/usr/share/php:/domains/include’) in Unknown on line 0

    After manually removing wf through ftp and deleting the database tables I installed wf again. Without optimizing the Firewall says: Extended protection.

    Erik de Vries
    WP Webbouw

    https://wordpress.org/plugins/wordfence/

Viewing 1 replies (of 1 total)
  • Plugin Author WFMattR

    (@wfmattr)

    8 years ago

    Hi,

    Thanks for the report. I haven’t heard of any other cases of this yet, but will watch for it. It sounds like the auto_prepend_file (in .htaccess or .user.ini) may have taken effect before the wordfence-waf.php file was in place. If you use a PHP cache, that may have lead to a longer delay before the file could be read, and would explain how the Extended Protection took effect without setting it up again.

    If you can post any other details about the sites, we can narrow down the cause. (e.g., whether a PHP cache was in use, which web server like Apache, LiteSpeed, etc., and which Server API if you know, such as CGI/Fastcgi, Apache 2.0 handler, lsapi, etc.)

    -Matt R

Viewing 1 replies (of 1 total)
  • The topic ‘Wf causes Fatal error’ is closed to new replies.