Failed to open stream

  • Resolved shanacorbin

    (@shanacorbin)


    4 years, 7 months ago

    Our site is down. Can’t access it at all other than this error:

    Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0 Fatal error: Unknown: Failed opening required ‘/hermes/walnaweb12a/b2175/moo.lrcmediacom/wordfence-waf.php’ (include_path=’.:/usr/local/lib/php-7.1.1-precise/lib/php’) in Unknown on line 0

    • This topic was modified 4 years, 7 months ago by shanacorbin.

    The page I need help with: [log in to see the link]

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

  • Hi @shanacorbin,

    This is usually caused when the update process for Wordfence is interrupted. Can you go into .htaccess or .user.ini and delete anything related to Wordfence?

    For example, it might look like:

    auto_prepend_file = ‘/hermes/walnaweb12a/b2175/moo.lrcmediacom/wordfence-waf.php’

    Dave

    Thread Starter shanacorbin

    (@shanacorbin)

    Oh my goodness, that worked perfectly! Thank you for the quick, confident reply.

    Glad it worked!

    If your host is running on LiteSpeed – here’s a follow up to help you avoid these issues in the future: https://www.wordfence.com/help/advanced/system-requirements/litespeed/

    What might’ve happened is that when Wordfence was updating, the server killed the update process, leaving some files missing or damaged on your host. The article I linked provides you a way to stop LiteSpeed from killing Wordfence’s update.

    If you’re not on LiteSpeed, check if someone accidentally deleted or moved the file at /hermes/walnaweb12a/b2175/moo.lrcmediacom/wordfence-waf.php.

    Dave

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Failed to open stream’ is closed to new replies.