Plugin / IP Geo Block

tokkonopapa
Download from WordPress

Frequently Asked Questions (FAQ)

This plugin is designed based on the principle of “Privacy by design” so that you can compliantly run it to GDPR. As guarding against personal data breach, IP addresses in this plugin are encrypted and also can be anonymized by default. It also provides some functions not only to manually erase them but also to automatically remove them when those are exceeded a certain amount/time. However, these are the part of GDPR requirements and do not guarantee that the site is compliant with GDPR. Refer to 3.0.11 release note for details.
Yes. You can synchronize the settings with all the sites on the network when you activate on network and enable “Network wide settings” in “Plugin settings” section.
The short answer is YES, especially for the purpose of security e.g. blocking malicious access both on the back-end and on the front-end. You can find the long answer and the compatibility list of cache plugins at “Compatibility with cache plugins“.
Absolutely, YES. Sometimes, a Wordfence Security user would report this type of claim when he/she found some accesses in its Live traffic view. But please don’t worry. Before WordPress runs, Wordfence cleverly filters out malicious requests to your site using auto_prepend_file directive to include PHP based Web Application Firewall. Then this plugin validates the rest of the requests that pass over Wordfence because those were not in WAF rules, especially you enables “Prevent Zero-day Exploit“. It would also possibly be caused by the accuracy of country code in the geolocation databases. Actually, there is a case that a same IP address has different country code. For more detail, please refer to “I still have access from blacklisted country.“.
The easiest way is to use free proxy browser addon. Another one is to use http header browser addon. You can add an IP address to the X-Forwarded-For header to emulate the access behind the proxy. In this case, you should add HTTP_X_FORWARDED_FOR into the “$_SERVER keys for extra IPs” on “Settings” tab. See more details at “How to test prevention of attacks“.
Please find the solution in Quick recovery from blocking on your login page at first. You can also find another solution by editing “Emergent Functionality” code section near the bottom of ip-geo-block.php. This code block can be activated by replacing /* (opening multi-line comment) at the top of the line to // (single line comment), or * at the end of the line to */ (closing multi-line comment). /** * Invalidate blocking behavior in case yourself is locked out. * * How to use: Activate the following code and upload this file via FTP. */ /* -- ADD '/' TO THE TOP OR END OF THIS LINE TO ACTIVATE THE FOLLOWINGS -- */ function ip_geo_block_emergency( $validate, $settings ) { $validate['result'] = 'passed'; return $validate; } add_filter( 'ip-geo-block-login', 'ip_geo_block_emergency', 1, 2 ); add_filter( 'ip-geo-block-admin', 'ip_geo_block_emergency', 1, 2 ); // */ Please not that you have to use an appropriate editor. After saving and uploading it to /wp-content/plugins/ip-geo-block/ on your server via FTP, you become to be able to login again as an admin. Remember that you should upload the original one after re-configuration to deactivate this feature. This document can also help you.
Yes. Roughly speaking, the strategy of this plugin has been constructed as follows: Block by country It blocks malicious requests from outside your country. Prevent Zero-day Exploit It blocks malicious requests from your country. Force to load WP core It blocks the request which has not been covered in the above two. Bad signatures in query It blocks the request which has not been covered in the above three. Please try “Best for Back-end” button at the bottom of this plugin’s setting page for easy setup. And also see more details in “The best practice of target settings“.
Unfortunately, no. This plugin can’t handle the requests that are not parsed by WordPress. In other words, a standalone file (PHP, CGI or something excutable) that is unrelated to WordPress can’t be validated by this plugin even if it is in the WordPress install directory. But there’re exceptions: When you enable “Force to load WP core” for Plugins area or Themes area, a standalone PHP file becomes to be able to be blocked. Sometimes this kind of file has some vulnerabilities. This function protects your site against such a case.
If you encounter this message, please refer to this document to resolve your blocking issue. If you can’t solve your issue, please let me know about it on the support forum. Your logs in this plugin and “Installation information” at “Plugin settings” will be a great help to resolve the issue.
When you enable “Force to load WP core” options, this plugin will try to configure .htaccess in your /wp-content/plugins/ and /wp-content/themes/ directory in order to protect your site against the malicous attacks to the OMG plugins and themes. But some servers doesn’t give read / write permission against .htaccess to WordPress. In this case, you can configure .htaccess files by your own hand instead of enabling “Force to load WP core” options. Please refer to “How can I fix permission troubles?” in order to fix this error.

Ratings

4.4
85 reviews

Rating breakdown

Details Information

Version

3.0.17.4

First Released

05 Jan, 2014

Total Downloads

724,523

Wordpress Version

3.7 or higher

Tested up to:

5.0.7

Require PHP Version:

-

Tags

Brute Force firewall login security vulnerability

Contributors

tokkonopapa

Languages

English (Canada) English (US)

DIRECTORY DISCLAIMER

The information provided in this THEME/PLUGIN DIRECTORY is made available for information purposes only, and intended to serve as a resource to enable visitors to select a relevant theme or plugin. wpSocket gives no warranty of any kind, express or implied with regard to the information, including without limitation any warranty that the particular theme or plugin that you select is qualified on your situation.

The information in the individual theme or plugin displayed in the Directory is provided by the owners and contributors themselves. wpSocket gives no warranty as to the accuracy of the information and will not be liable to you for any loss or damage suffered by you as a consequence of your reliance on the information.

Links to respective sites are offered to assist in accessing additional information. The links may be outdated or broken. Connect to outside sites at your own risk. The Theme/Plugin Directory does not endorse the content or accuracy of any listing or external website.

While information is made available, no guarantee is given that the details provided are correct, complete or up-to-date.

wpSocket is not related to the theme or plugin, and also not responsible and expressly disclaims all liability for, damages of any kind, arising out of the use, reference to, or reliance on, any information or business listed throughout our site.

Keep Leading Your Followers!
Share it for them.