Steven Maas
My feedback
1 result found
-
1 vote
Most ISO codes of rogue nations are well known. We think that changes to geo IP blocking are rarely needed. To keep development costs reasonably low, perfect comfort for rarely used features is not a priority. In a server's lifetime it may occur twice that this is changed, so we wonder how often this feature is used in your daily routine that the added comfort is required? Please comment how you determine the countries to be blocked and why you change countries often so that we understand your routine better and can provide a better product while trying to keep license prices low.
An error occurred while saving the comment Steven Maas shared this idea ·
First of all thank you for this long overdue feature. Our plesk server receives numerous daily attacks from all over the world.
As our server is attacked I have to look up the ip address to see which country they originate from. Sadly plesk does not automate this procedure. Why you have not over the years is perplexing. So after I locate the country associated with the ip address I add them add to the firewall. I noticed that I added the same country twice because it was on separate logs on separate days. Since the country abbreviations do not sort alphabetically it was not easy to determine if I already added it.
Since country codes don’t change why not allocate the lookup of each county for all of your users?
Honestly these are all easy common sense feature requests that will save time for all your users. Plus add a quick lookup of an ip address to see which country they are coming from. I host Wordpress sites and use word fence which automates the procedure of whois lookup. Why do you not have this feature built in to plesk?