Locked out after scan

  • Hi,

    Recently, we got advised to install WordFence to enhance the security on our website. We have a standard method when it comes to testing new plugins; having our website running locally via XAMPP.

    So, I installed WordFence locally to test it. I followed the tour and started the first scan. The result was that a couple of plugins were out-dated. When I wanted to go to update these plugins, I went to the plugins page, but instead of the plugins page I saw this: https://gyazo.com/69d168fea3e12bbc9947ae0e6c3656f2

    After renaming the wordfence folder to wordfans, I gained access again.

    Everytime I execute a scan this happens. As you can imagine, I’m not really eager to install the plugin on the live website after having these issues.

    Is this some kind of known issue?

    I would like to hear from you.

    Sincerely,
    Guido Visser

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter guidovisser

    (@guidovisser)

    I noticed that after some time, the local site is reachable again after a scan.

    Hi,

    Double check the system requirements. The memory requirement is very important for scans. How close does the XAMMP environment mirror your live site specs-wise?

    https://docs.wordfence.com/en/Wordfence_system_requirements

    Also, you could try setting”Maximum execution time for each scan stage” option to 20 under Options.

    -Brian

    It could be even simpler issue. Make sure your IP is listed on whitelist. I had this issue where security plugins will block me after certain time because my theme was calling for .js that didn’t exist. And each time it does, I’m logged as looking for nonexistant file user and get blocked eventually.

    If you’re whitelisted, you’ll have time to look into logs.
    Good luck!

    Thread Starter guidovisser

    (@guidovisser)

    It seems that it’s fixed, I did what you said WFBrian and upped the memory_limit value in the php.ini within XAMPP since we have 1GB of RAM. However I did not get any memory_exeeded message in the logs. I also added our external ip adress to the whitelist. Now if I run a scan, I don’t get locked out.

    It’s a really weird issue though, why would I get locked out in the first place? The only thing I do is a scan, plus I run it locally and the software clearly states that it automatically whitelists private ip addresses like 192.168.x.x.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Locked out after scan’ is closed to new replies.