Preventing of self-blocking of the host server

Many thanks for your great plugin! I have now successfully achieved what I wanted for several months on various websites.

Here is a suggestion/hint for a future version:

I run my own web servers with Plesk and WordPress toolkit and block the backend via IQ block. So far everything is working as expected!

For websites that are managed in a different country code, only the country code of the login area is open, everything else is blocked. However, this then leads to an effect ( possibly triggered by the WP-Toolkit). The IP of the web server is shown in the log file on a daily basis.

I have manually prevented this by adding the IPs of the web server to the white list of the backend in the relevant WordPress installations. This must be corrected manually when moving servers and taken into account for new installations.

My idea: If the web server has an NL IP, for example, and the backend is blocked for NL, the IP of the server is added to the whitelist. Or in general… as I don’t see it as a security risk.

I find it more difficult to customize after the server move. But a visit to the corresponding options page in the plugin and a button would be a simple mode. Or when activating the plugin – so that deactivating and activating via WP-Toolkit from Plesk would simplify the re-setting of the IP to the whitelist.

I would be happy to provide further details or – if not available myself – access to a Plesk account!

Kind regards