Plugin Author
Pascal
(@iqpascal)
That is sign that you most likely use a caching plugin that is not compatible with the iQ Block Country plugin.
Depending on the solution you use you may be able to clear the cache, although by now it should be cleared automatically.
Thanks for that. But it doesn’t explain why the plugin blocked my country and (let’s say) USA when I didn’t have them on the list. I had the plugin set to not block the admins IP.
Plugin Author
Pascal
(@iqpascal)
The caching plugin was not honoring the headers iQ Block Country sends with each block. It tells any caching solution or browser to not cache this message.
Because a previous visitor was blocked you from an allowed country gets served the blocked message from the cache.
In combination with any caching solution the ideal best case scenario is that all visitors that are allowed will never see a blocked message and that some not allowed countries will sometimes be blocked if a page is not served from cached or are allowed because the page is served from cache.
Which plugin are you using?
W3 Total Cache
and I don’t know if Wordfence cases anything or JetPack
Just and FYI — I had 7 client sites (last night and today) having same issue – all using W3 Total Cache, to correct issue I had to “Empty All Caches”.
The sites were hosted in USA and only blocked a few countries like Russian Fed, etc. But USA (not selected to block) was being blocked?
Also I did note that 5 out of 7 clients GEO files were outdated. So I updated their GEO files.
PASCAL – the only other plugin all sites had in common was JetPack, and had updated hours earlier to WordPress 4.5
I hope that helps to narrow things down if anyone else has issue. But “Empty All Caches” will fix the issue.
Plugin Author
Pascal
(@iqpascal)
If somebody from a blocked country visited your site and that page was not yet or not anymore cached by W3 then W3 will cache the blocked message. Just as it would have cached a normal page if a visitor was from a non blocked country.
That’s the way in this case caching works. As said above the best case scenario if a caching plugin would honor the do not cache headers this would be the best situation:
In combination with any caching solution the ideal best case scenario is that all visitors that are allowed will never see a blocked message and that some not allowed countries will sometimes be blocked if a page is not served from cached or are allowed because the page is served from cache.
