• Resolved deehunt

    (@deehunt)


    This:

    Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0

    Fatal error: Unknown: Failed opening required ‘D:\Hosting30504\html/wordfence-waf.php’ (include_path=’.;C:\php\pear’) in Unknown on line 0

    comes up when I try to go to my site or logon after I had installed the Wordfence firewall.

    Please help,

    I’ve been looking for possible fixes but so far I haven’t found anything or anything that has worked.

    -Dee

    https://www.ads-software.com/plugins/wordfence/

Viewing 10 replies - 1 through 10 (of 10 total)
  • Hello Dee,
    to quickly get rid of the error check your /html/ root folder for either a .user.ini file containing “; Wordfence WAF” definitions or “# Wordfence WAF” definitions in your .htaccess. Remove those pieces of code.

    Let me know if that works and we can take it from there.

    Thread Starter deehunt

    (@deehunt)

    https://chapiescomics.com/ryzom/Dee1.jpg

    No such files in the main folder…

    Hello again DeeHunt,
    check in the file called php5.ini.

    Where are your WordPress folders? Did you crop them out of the picture or do you have them in a different location?

    hi

    please i am in urgent need of help. my site was recently hacked, and my ISP reloaded my one back ups. once they did that i still could not access my site at all.

    I even uninstalled wp and reinstalled but im still getting the following error:

    Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0

    Fatal error: Unknown: Failed opening required ‘/home/ssnrfqdr/public_html/wordfence-waf.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in Unknown on line 0

    I’ve followed your steps mentioned above, but i am having no such luck in finding the files that were mentioned.

    if anyone can assist me i would appreciate a lot.

    thanks

    Hello icestorm22,
    can you see a “wordfence-waf.php” file in the root directory of your site (in public_html)? If you configured Wordfence Firewall via Wordfence automatic configuration procedure without making any manual edits to files, the “auto_prepend_file” directive which is causing that error will be located in .htaccess, .user.ini or possibly php.ini in the root of your site.

    Thread Starter deehunt

    (@deehunt)

    I deleted the php5.ini file because all it had was this in it:
    ; Wordfence WAF
    auto_prepend_file = ‘D:\Hosting30504\html/wordfence-waf.php’
    ; END Wordfence WAF

    and now it seems as though my site is back up.

    Thanks,

    -Dee

    Thread Starter deehunt

    (@deehunt)

    Okay,
    so when i click to configure the firewall is when it happens. I clicked to configure it again and it happened again. so I deleted the files it created again and my site is back up.

    -Dee

    FYI – .htaccess also references that file!

    hi

    @wfasa thank you for your info. i must confess though i have not had any luck with finding those files that you have mentioned. I’ve searched for them, but nothing is appearing.

    if i try and access the site, https://www.elhockeyacademy.co.za its just brings up a white page with some writing on.

    i cant access the wp control panel at all. i have even uninstalled wp from my main cpanel and reinstalled but still having the same problem.

    if you have any tips or advise please let me know.

    thanks

    icestorm22,
    you need to contact your host and ask them for help about this right away. Clues as to why your site is inaccessible should be available in the servers error logs. Oftentimes these are made available via the web hosts administration tool but if they are not, as your host to look for them.

    If you can find the error logs yourself feel free to share them with me and I can help you interpret them. Email them as plaintext to [email protected]. Include your WordPress username in the email so I know who the email is coming from.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Fatal Error’ is closed to new replies.