500 Internal + Email Disconnect

  • Resolved twwa

    (@twwa)


    5 years, 1 month ago

    This morning, my site suddenly began showing 500 errors whenever I tried to log in. Everything on the frontend seemed to be fine.

    Error Logs showed this:
    PHP Fatal error: Unknown: Failed opening required ‘/[path]/wordfence-waf.php’ (include_path=’.:/opt/cpanel/ea-php74/root/usr/share/pear’) in Unknown on line 0

    Following a suggestion on another post, I disabled Wordfence via FTP, replaced wordfence-waf.php with a blank file, and removed .user.ini. That seems to have fixed the issue and I was able to login and reactivate Wordfence.

    Unfortunately this hasn’t fixed my other issue which started at the same time and which I assume must be related. My bluehost-provided email account, which is associated with the site, is disconnected in Apple Mail. When I enter password and try reconnecting it says it’s unable to verify login info. I can still access my email account directly through Bluehost’s site so I know that the login information has not changed.

    Any idea what might have caused the original error (nothing was changed/moved recently that I’m aware of) and is there any way that Wordfence might’ve caused the email client disconnect like this?

    Thanks

Viewing 1 replies (of 1 total)
  • Plugin Support WFAdam

    (@wfadam)

    5 years, 1 month ago

    Hello @twwa and thanks for reaching out to us!

    It looks like the path specified with your auto_prepend_file might of been incorrect and cause the site to lockout. Are you able to get Wordfence running again without the site crashing?

    If so, can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    If not, you might need to clear out anything #Wordfence WAF related in your htaccess and user.ini file. I believe blue host runs on a CGI/FastCGI server API, so its most likely in the user.ini file. Once you remove the code, the auto_prepend_file should set to default and will allow you to access the site. Then you can go back through the Wordfence > Scan > Optimize the firewall steps for the Apache + FastCGI.

    As for the Email server issue, Wordfence doesn’t do anything with the email credentials so it might be best to reach out to blue host about your mobile inbox issue.

    Let me know if this helps!

    Thanks!

Viewing 1 replies (of 1 total)

The topic ‘500 Internal + Email Disconnect’ is closed to new replies.