red scan error (error HTTP response: 100)

  • Resolved private183

    (@private183)


    11 years ago

    So i do receive an scan error after the Plugins and Themes are detected.

    First error (solved)
    [Feb 08 20:13:55:1391883235.843357:1:error] <br /> <font size='1'><table class='xdebug-error xe-fatal-error' dir='ltr' border='1' cellspacing='0' cellpadding='1'> <tr><th align='left' bgcolor='#f57900' colspan="5"><span style='background-color: #cc0000; color: #fce94f; font-size: x-large;'>( ! )</s

    Btw. this error corrupts the “Scan” page (everything below – that is “Docs: …” and “Issues” tabs – has/have been moved inside to “Scan Detailed Activity”)

    Of course i checked FAQ: Red Error, Not completing, aren’t of any help cause there is no file referenced or any error indicator given. On
    scan won’t finish – well i tried to set it to 15 and 24 as 30 is my current limit.
    Problematic Plugins are not installed.
    Feature not working So i have disabled all other plugins. Further i don’t got any other security plugin installed on this wp-install (details see below; .htaccess just has permalinks setting). Java Script Console doesn’t show errors, nor does the site show any problem.
    I also checked wordfence’s option to delete tables etc. on deactivation and de/reactivted it to reinitiallize all (and have a working scan page till first scan and refresh page).

    What i first thought of – i read windows server is not officially supported/might cause problems, well acually i am testing things out – offline with wampserver on win7. That’s where i thought to take a look in the error logs – and found one at php_error.log. Time Exceeded either i tried “15” resp. “24” at option “Maximum execution time for each scan stage”. I changed the setting to 120 at wampservers php.ini and that works now.

    Second Error (open)
    [Feb 09 09:29:39:1391930979.019494:2:error] Scan terminated with error: We received an error HTTP response when trying to fetch binary data from the Wordfence scanning server: [100]

    And this is where i can’t do much anymore as it’s probably not on my side (other logs look fine). Ah – forgott above: all tests pass on “Wordfence connectivity tester”

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

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

    (@mmaunder)

    Hi,

    Thanks for the detailed report. Looks like you’re getting an HTTP 100 response which means “CONTINUE”.

    I’ve examined the source code for Wordfence and it looks like your machine is configured to use Curl, and what’s happening here is you’re getting a non ‘200’ response which isn’t actually an error. It’s just telling Curl to continue with the request.

    So my guess is that a proxy is sitting between your windows server and our server noc1.wordfence.com and is sending you that response for some reason and perhaps expecting you to resend the request.

    I’d recommend either logging a call with your hosting provider and asking them about this or if you’re running your own network, check your proxy settings.

    Regards,

    Mark.

    Thread Starter private183

    (@private183)

    Thank you, for your answer. Well that sound’s as it wouldn’t be too hard to manage.

    So first i thought to use an vpn (paid one using openvpn) – i mean if i am already connected to america either it’s the east instead near washington (tested 2 available servers + 2 outside of US so at least 1 connection should have made it moreless direct/not routed somewhere “cheaper”) – at least no proxy inbetween vpn should interfere? Then i thought of my anti virus that uses a local proxy to check connections. Temporary disabling (while still in vpn) also didn’t help.

    Finally i decided to tracert noc1.wordfence.com – and of ~30 routs just ~12 managed to stay in the timelimit, yet i changed it to 500. And no matter from where (VPN) i have sent the request – it stopped after “rtr3.te7-5.lw.netriver.net [69.46.33.213]”. So, what now?

    Plugin Author Wordfence Security

    (@mmaunder)

    Yup, that looks like our default gateway and we filter out traceroute packets, so that’s to be expected.

    Again, looks like it’s a proxy between your server and us and you have to figure out where it is.

    Regards,

    Mark.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘red scan error (error HTTP response: 100)’ is closed to new replies.

Tags