Hi all,
(I’ve copied my reply from a similar post, here.)
Sorry for the trouble in updating Wordfence on your sites. Our dev team is looking into this. We’ve found that if you have multiple sites in a single hosting account and the firewall optimization was only completed on some of the sites, and only some of the sites have been updated, that may be the cause.
Specifically, if you have sites in your hosting account folders like this:
/home/user/public_html/ (firewall optimized, still running 6.1.10 or earlier)
/home/user/public_html/site2.com/ (firewall not optimized, updated to 6.1.11)
Then, the site2.com could have this issue because the firewall from the first site in the public_html directory is running before the newer version of Wordfence in the site2.com subdirectory.
If your sites are set up like that:
* Update the Wordfence installation on the first site (in public_html/ in the example above), and the sites in the subdirectories should work normally.
* Alternately, you can temporarily remove the firewall optimization on the first site, so sites in subdirectories will not have part of the older version pre-loaded.
If your sites are not set up like that:
* Create a separate post in this forum instead of replying to this one, so we can work through the details of your site if there is another cause. Please include specifics of the sites, like subdirectory names — you can replace actual domain names with ‘domain1.com’ and similar. (To make a new post, click here and use the form at the bottom of the page.)
-Matt R
