After Update Blocked

I deleted the folder of IP-Gep-Block now it works again. After re-Install it still blocks me. I don’t know… I can’t reinstall the plugin..

Hi @anluma23,

I’m so sorry about your bad experience. I may overlooked something on updated version.

> After re-Install it still blocks me.

Were you blocked right after re-activation of this plugin? Basically, while you were login as an admin, this plugin would not ban you by design but would make a caution like the following admin notice:

But if you did not see it, I should ask you to help me to investigate the cause. In this case, could you try to enable “Emergent Functionality” in /wp-content/plugins/ip-geo-block/ip-geo-block.php described in “What should I do when I’m locked out?“.

I’d really appreciate your cooperation.
Thanks in advance.

most of the country code says ZZ, even mine.
you might wanna look into that.

Hi @aye-pogi,

Thank you for your information.

most of the country code says ZZ, even mine.

If you configure “Whitelist” as “Matching rule” and your country code in “Whitelist of country code“, then “ZZ” (it means unknown country) will be blocked.

In this case, I’d ask you to add “ZZ” into “Whitelist of country code” like “JP,ZZ” not to block your self. Then we can investigate why “ZZ”.

Anyway, “Emergent Functionality” should be applied in that case.

I should investigate why the country code would be “unknown”. Probably, something was wrong related to the new GeoLite2 API.

you might wanna look into that.

Yes! First of all, I’d like to know the followings in “Plugin settings” section:

• Your settings, e.g. “ip-geo-block-settings.json” file available at “Export settings“
• “Debug information” available at “Show information“

I’d deeply appreciate to send those info to tokkonopapa at yahoo dot com.

Thanks so much!

• This reply was modified 7 years, 1 month ago by tokkonopapa.

sent

All my user in Europe are complaining they can’t get to the website. This used to work in the previous version, just updated today. When I look at the log ZZ is the country of origin. Adding ZZ to the whitelist is a bad practice isn’t it?

• This reply was modified 7 years, 1 month ago by jbailey969.

Dear all,

Please refer to “When you were blocked after upgrading to 3.0.7” to revert using legacy databases until I found the solution.

@aye-pogi : Thank you for sending me your info. I keep dedicating to find the solution.

@jbailey969: Yes, if all the countries were assigned as “ZZ” because all the countries would be passed.

Thank you all for the cooperation.

I just did what you suggested, removed ZZ from the blocked list and now I am blocked out. So it appears the legacy database change of the PHP code did not work for me. I am just going to do a server rewind and get back to the previous version of ip geo block.

Dear @jbailey969,

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 3.0.7.1.

Actually, current GeoLite2 DBs that are 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 got it to work. Actually the sign was when I went on my hotspot which had a different IP address could get in. Then was a little frustrated with the scan country code never updating when I logged into my wifi. It said ZZ (cache). It would be nice when you press scan country code for it to clear it from cache the IP of if it is already in the cache but the country code does not match. Anyway I cleared the cache and it had the right code.

Thanks for your plugin. When I first started my site I had so many attacks it just would not work until I added your plugin and started blocking the normal hacking countries. That reduced it a lot so thank you!

Dear all,

I’m sorry about this issue. I hope you to upgrade to 3.0.8 that I believe the issue had been resolved.

If you still encounter the blocking, please clear the cookies and cache in your browser, and try to login again.

• Clear Cache in IE 11
• Clear cache & cookies in Chrome
• How to clear the Firefox cache
• How to Clear Cache, Cookies or Browsing History on Mac Safari

Once I’d close this topic, but please feel free to post a new topic if you still have some issues in 3.0.8.

Thanks for your cooperation and your kind understanding!