Viewing 10 replies - 1 through 10 (of 10 total)
  • I am running wordpress 3.4.2 on localhost (xampp pack) on a windows machine and Comodo firewall.

    I have the same problem, the plugin is not able to fetch API key from your server. Comodo Firewall active connection window shows the connection between my comp and your servers.

    Another Usage Question :

    As you specify that your plugin has a firewall. Can the firewall be configured (or any other way in the plugin) to actually block wordpress core/ theme files from sending /receiving data to a particular IP just like as we can do with a desktop firewall (in my case comodo internet security).

    I downloaded some themes which may be having base64 encoded code embedded in them. I checked it with TAC plugin and it did show theme files containing encoded data.

    I could try removing the encoded code but that might break the theme altogether and then there might be other way to link or code some functions or modules that might make a call to the hacker’s servers and on top of that I am not that good with PHP so I thought it would be better to provide a kind of environment where the file is not able to make a call to the IP address altogether.

    Thanks & regards,
    appu.

    Thread Starter Sonja London

    (@summit)

    @cartpauj
    Thanks, but we had already read the post. We did not see when you expect it to be working. We just saw “we’ll be back shortly”.

    Do you have anything more specific yet?

    This has been going on for ages now (check the plugin forum).

    Maybe this is a ploy to get punters to upgrade to premium? After all, you are kinda left out in the cold…

    @tonyfrost
    Really? Free scanning went down one week ago. A new update was released today and free scanning is back and faster than ever. The developers have worked hard to keep most of the features of this plugin free. Perhaps a thank you to them would be more appropriate than unsubstantiated criticism.

    not quite. tried to initiate a scan right now =>

    [Oct 15 18:31:09] Scan terminated with error: WordFence API error: Due to high load, scanning is temporarily unavailable for our non-paid members. Please see our support forum for an update on this issue at: http://www.wordfence.com/forums/ and click the top forum.

    Old version 3.2.7 will not work. In order to initiate a successful scan you will need to update to latest version.

    UPDATED VERSION 3.3.2 A complete rearchitecture of Wordfence scanning to massively improve performance. Free customers are now 100% back in business ( – after they upgrade to latest version).

    @CedarPointConcepts
    I agree. Asking questions is okay. Complaining about something free like it is an inalienable right is very spoiled.

    Plugin Author Wordfence Security

    (@mmaunder)

    Thanks for being ahead of me on this guys. We worked our tails off the entire week and over the weekend to get the rearchitected Wordfence release out. It went out yesterday and the redesign will allow us to continue to provide an excellent high performance product to the free community without interruption for the foreseeable future.

    As mentioned we were forced to give our paying customers priority during the delay while we rearchitected, so my sincere apologies to the free folks for that interruption. I value both the free community and our paying customers and it’s important to note that many of our free users have contributed to helping out on our forums at http://www.wordfence.com and have sent us valuable feedback on the product – so much appreciated guys and this new release is completely dedicated to getting you back in business.

    So thanks all for sticking with us and know that Wordfence is now able to scale from the current tens of thousands of users well into 7 figures now without interruption.

    Regards,

    Mark Maunder
    Wordfence Founder.

    Thanks Mark for getting back.

    Time to eat my hat!

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘[Plugin: Wordfence Security] scanning unavailable for our non-paid members?’ is closed to new replies.