WordFence config files not working with a Load Balancer and multiple slaves

  • We have an issue with the new way WordFence stores options, where it seems to use the file system instead of the database?

    We have a lot of sites on our network using a stage-publish process, and use a Load Balancer behind Incapsula, with multiple slave machines behind that.

    The problem is when we try save any options, it saves it on whatever slave it is connected to for that request, but not any others.

    So we can’t save or change any options.

    Please can you advise?

Viewing 1 replies (of 1 total)
  • Plugin Author WFMattR

    (@wfmattr)

    Hi,

    Sorry to hear you are having trouble with these options. Currently, this only affects the options related to the web application firewall that was introduced in version 6.1.1, while other options in the Wordfence plugin are still stored in the database.

    The reason is that when the firewall is optimized, these options need to be available before WordPress loads, but the database isn’t available yet at that point. We may have a way for the firewall to work on such a configuration in a future version, but there might not be a current workaround if the servers behind the load balancer don’t share the same storage via a SAN or NFS.

    It may be best to disable the firewall by editing wp-config.php, as described here, for now:
    Disabling the firewall in wp-config.php

    The rest of Wordfence’s features, including login security, rate limiting, scanning, etc., will still work when the web application firewall alone is disabled by this method.

    -Matt R

Viewing 1 replies (of 1 total)
  • The topic ‘WordFence config files not working with a Load Balancer and multiple slaves’ is closed to new replies.