IP Blacklisted from wrong country

This IP is being blocked. 70.28.11.95 IP search tool does identify it as Canada, but it is blocked. hmm

70.28.11.95 CA Toronto,
Ontario,
Canada,
North America 43.6667,
-79.4167 Bell Canada Bell Canada bell.ca

It is indeed registered to Canada. So I assume Canada was blocked from either the backend or the frontend or both.

Or perhaps an old database was used where this IP address was assigned to a different country.

I checked it with the tool and it came up Canada but was blocked. So I think you have a bug. I double checked the blocked Countries — Russia, China, Romania for admin and front.

If I use the search tool and it does identifies as Canada, then that is the DB it is using for blocking I assume. It wouldn’t be searching another DB then block using something else?

If that is the case then you definitely have a problem.

Are their any known conflicts with caching or cloudflare?

If your client uses caching that could as well be the problem yes.

The plugin tries it best to stop caching software from caching the denied message however if the caching software is configured to ignore or overwrite the caching headers the plugin sends a legitimate user may receive the cached result from a previous user that received the denied message.

I would recommend against using the plugin for blocking users from the frontend in combination with caching unless you fully understand the caching software. Using the plugin in combination with blocking the backend should not be a problem as caching should not be used for the backend.

If you use the IP check from within the plugin it should also indicate if the user is blocked from either frontend or backend as well. For instance:

IP Adress 70.28.11.95 belongs to Canada.
This country is not permitted to visit the backend of this website.

I’ll assume this problem was caused in combination with a caching solution?

A lot of WP sites use caching. I suggest you find a way to prevent the blocked messages from being cached.

The plugin is already as compatible with caching as it can be. If caching software chooses to ignore or is configured to override the do not cache headers the plugin sends there is nothing I could do more.

Caching software should either respect the do not cache headers (as pages can also contain personal information that should not be cached) or have an administrator that knows what it is doing when it chooses to overrule (some) do not cache headers and cache anyway.