• Resolved FeralReason

    (@feralreason)


    This is on a staging site on Bluehost. (The previous post on this topic is not relevant to this.)

    I’m trying to migrate my site to another host and getting this fatal error:

    PHP Fatal error:  Failed opening required ‘/home/j6vpqk8n10fz/public_html/wordfence-waf.php’ (include_path=’.:/opt/cpanel/ea-php82/root/usr/share/pear’) in Unknown on line 0

    I have FTP access but no WordPress access yet. To facilitate the migration, I have 1) deleted the Wordfence plugin, 2) renamed “wordfence-waf.php” (to wordfence-waf-OLD.php, 3) renamed the wflogs folder to wflogs-DISABLED. 4) renamed the plugins folder to plugins-OLD (attempt to get rid of a 500 err.) — but still getting this “fatal error” in my error.log.

    Where else could this “required” is coming from? How do I delete or comment it out?

    Thanx much – Glenn

    • This topic was modified 1 year, 2 months ago by FeralReason.
Viewing 1 replies (of 1 total)
  • Thread Starter FeralReason

    (@feralreason)

    Found the answer. There is a file called .user.ini in my public_html folder looks like this:

    ; Wordfence WAF
    auto_prepend_file = ‘/home/xxxxxxxxxx/public_html/wordfence-waf.php’
    ; END Wordfence WAF

    The auto_prepend_file line has to be commented out to eliminate the fatal error (and the 500 error. ) Now that I’ve eliminated this I can access the site and should be able to continue the install.

    The problem was: The staging site’s path starts with /home2/… rather than /home/… Although all these paths could be edited, it is probably better to delete all files relating to Wordfence and then re-install once I migrate to the live site.

    • This reply was modified 1 year, 2 months ago by FeralReason.
    • This reply was modified 1 year, 2 months ago by FeralReason.
Viewing 1 replies (of 1 total)
  • The topic ‘PHP Fatal error:? Failed opening required … wordfence-waf.php’ is closed to new replies.