Blocks the server where the site itself is located

Can you tell me a bit more about your server situation.

Was it doing this since you started using it, if not then what has changed recently.

Feel free to email if you want ([email protected]) I would love to get to the bottom of this.

A DOS attack was carried out on the server where my sites were, the support service corrected the situation and the sites started working, except for 2 out of 7, I note that I have this plugin installed on all 7 sites.

2 the site displayed a 403 error, I turned to the hosting, they found in .htaccess blocking the IP of their server, they informed me that they deleted the ip of the server and the site is working, it really worked for another 10-15 minutes and then error 403 again.

Hosting was informed that it was necessary to add the server IP to the whitelist, I chose Set Advanced Mode in the plugin settings, and entered this IP there, after a while an error occurred again, and looked at it again.htaccess I found the IP of the blocked server.

Later, the same thing started on the other sites, as a result, I removed the IP blocking in .htaccess and disabled the plugin.

The plugin is very good and helps with bots, I hope this information will be useful to you.

“the support service corrected the situation”

My thinking is that they have changed some settings to put in place flood protection. And that is triggering this plugin to capture the wrong server IP address. I would love to know more about what your server’s $_SERVER global is reporting, if you have an idea what that is feel free to email me on the above email. It would help.

However if that is not possible, I am about to upload an update, that while it may address your situation, in the event that it does not, there is an *option* now in this next update of Pareto Security to disable writing to the htaccess altogether, and rather depending solely on blocking bad requests.

I have just posted an update, can you let me know if this solved the issues you are having, and if not, did disabling the writing of ip addresses to the htaccess (now available in settings) then work as a workaround for now?