wordfence fatal error took my site down for 6 hours today

  • Resolved myroxie

    (@myroxie)


    9 years, 1 month ago

    My site was knocked out today. According to my host, they found the following error:
    “thrown in /home/xxxxxxx/public_html/wp-content/plugins/wordfence/lib/wfAPI.php on line 89
    [07-Sep-2015 23:07:29 UTC] PHP Fatal error: Uncaught exception ‘Exception’ with message ‘There was an error connecting to the the Wordfence scanning servers: Unknown SSL protocol error in connection to noc1.wordfence.com:443 ‘ in /home/goodwo7/public_html/wp-content/plugins/wordfence/lib/wfAPI.php:81
    Stack trace:
    #0 /home/goodwo7/public_html/wp-content/plugins/wordfence/lib/wfAPI.php(32): wfAPI->getURL(‘https://noc1.wo…’, Array)
    #1 /home/xxxxxxx/public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(149): wfAPI->call(‘ping_api_key’)
    #2 [internal function]: wordfence::dailyCron()
    #3 /home/xxxxxxx/public_html/wp-includes/plugin.php(579): call_user_func_array(‘wordfence::dail…’, Array)
    #4 /home/xxxxxxx/public_html/wp-cron.php(117): do_action_ref_array(‘wordfence_daily…’, Array)
    #5 {main}
    thrown in /home/xxxxxxx/public_html/wp-content/plugins/wordfence/lib/wfAPI.php on line 81″

    My host disabled Wordfence. Now I don’t know what to do.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author WFMattR

    (@wfmattr)

    Sorry to hear about the outage — this type of error generally means that something is wrong with “cURL” on the server, or possibly DNS. The error message above might have been a side effect of a larger problem on the server, though — normally that alone wouldn’t stop the site from working.

    If you can get the full error log from the outage, there would likely be errors at different times too, and some of them may have different information. On most sites you can get it by FTP or through your host’s control panel, but if not, the host could give it to you.

    If there are only a few errors, you can post them here, but otherwise, you can email the log to me at mattr (at) wordfence.com

    Do you know the approximate time of day that the outage started, and when it ended? (Please include the time zone the times were in, too.)

    -Matt R

    Thread Starter myroxie

    (@myroxie)

    I sent in the only error log my host shared with me. According to pingdom, the site was down 10/07/2015 12:37:21PM 10/07/2015 06:17:21PM

    Plugin Author WFMattR

    (@wfmattr)

    Ok. I’m not sure what timezone pingdom measures in (or if it’s adjusted for your time zone), but I’m guessing the error that the host sent was near the end of the outage.

    If you can ask the host to send a complete error log (and an access log too if possible), we may be able to help figure out what happened — we would need to see the errors and visits that were logged shortly before outage began.

    We haven’t had any similar reports, so there was most likely a problem on the host or their network, but the logs are the only way we may be able to determine if Wordfence had some specific trouble, or if the error above was a side-effect of a network or DNS issue on the server.

    Hope this helps — if you do get the logs, you can send them to me at:
    mattr (at) wordfence.com

    -Matt R

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘wordfence fatal error took my site down for 6 hours today’ is closed to new replies.