Support » Plugin: IP Geo Block » When you were blocked after upgrading to 3.0.7

  • ResolvedPlugin Author tokkonopapa

    (@tokkonopapa)


    Dear my customers,

    When you encountered unexpected blocking after upgrading to 3.0.7, please follow the steps:

    1. Rename this plugin’s folder from ip-geo-block to ip-geo-block- or something in your /wp-content/plugins/ to deactivate this plugin.
    2. Enable “Emergent Functionality” in ip-geo-block-/ip-geo-block.php described in “What should I do when I’m locked out?“. You can upload the updated file using FTP or cPanel tool.
    3. Rename ip-geo-block- as the original name.
    4. Activate this plugin again.
    5. Check your country code at “Your IP address / Country” at the top of “Validation rule settings” section.
    6. If the country code is shown as “ZZ” and selected “Whitelist” as “Matching rule“, please add “ZZ” into “Whitelist of country code” followed by “,” like “JP,ZZ”.
    7. Disable “Emergent Functionality”. It will be done by restoring ip-geo-block.php back to the original.

    In version 3.0.7, the Maxmind GeoLite2 databases will be installed because GeoLite Legacy databases in the previous version will be discontinued. But GeoLite2 requires PHP 5.4.0+ and downloading DBs requires PECL phar 2.0.0+ extension which should be available on PHP 5.4.0+.

    When your PHP is under 5.4.0, then GeoLite Legacy will be still applied.

    I had tested the upgrading process for both cases on PHP version 5.3.29 and 7.1.8 on test bed, and 7.1.8 on my real site.

    But something would be incompatible with some environment. So I’d appreciate you if you help me to resolve this issue when you encounter unexpected blocking.

    Related topics:

    Thank you for your cooperation.

    • This topic was modified 1 year, 8 months ago by  tokkonopapa. Reason: Added related topics
    • This topic was modified 1 year, 8 months ago by  tokkonopapa.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author tokkonopapa

    (@tokkonopapa)

    Dear all,

    For the time being until I found the solution, please replace class-maxmind.php in your Geolocation API library to the special crafted one described in “Force to use legacy databases“.

    Thanks for your cooperation.

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Dear all,

    I deeply apologize to compromise. I found the solution and already release the new version 3.0.7.1. So I hope you to upgrade to 3.0.7.1.

    Actually, current GeoLite2 DBs that have been adopted to 3.0.7+ seems not to be equivalent to the Legacy DBs, so that IP2Location DBs may works more frequently as a fallback.

    But Maxmind announced that Legacy DBs would not be updated since Apr. 2018. So we should change the DBs.

    I hope you to keep using my plugin.

    Thanks a lot for your cooperation!

    I just wanted to notify that I have found a similar problem, both with the old and the just-updated versions (just minutes ago). Maxmind thinks Spain is “ZZ” in your plugin (though country is correctly reported at their website), and your plugin warns that I will be locked out if I log off and try to log in again. I can send a screenshot if requested. I am using WP with no active cache plugin, latest versions of everything. Hope this helps.

    • This reply was modified 1 year, 8 months ago by  lobogc.

    What is the status of this? I still have US,ZZ in my whitelist.

    Plugin Author tokkonopapa

    (@tokkonopapa)

    Hi @wyclef and all,

    I’m sorry about the issues in 3.0.7.x. Please upgrade to 3.0.8 and remove ZZ in your whitelist.

    If you still have some troubles, please clear browser’s cache and login again.

    Thanks for your cooperation!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘When you were blocked after upgrading to 3.0.7’ is closed to new replies.