tokkonopapa

Hi @mikapan,

I’m afraid I misunderstood your situation.

When the following message is shown on dashboard:

How does “Local database settings” look like?

If you see it like below (e.g. “Download now” button is disabled), then the real path and the internal path to the Geolocation API libraries might be mismatched.

In this case, please try deactivate this plugin once and re-activate again. Right after the activation, you’ll see the same warning. But after for a while, you can find the updating success message like this:

And you can also find “Geolocation API settings” like this:

• This reply was modified 6 years, 4 months ago by tokkonopapa.

Hi @mikapan,

I’m so sorry about your issue.

I can not say certainly about the cause, but I guess that the original version was less than 3.0.14 and the update of the geolocation API libraries failed.

So would you confirm the existence of ip-geo-api directory? It must be placed at one of the followings:

1. /wp-content/ip-geo-api/
2. /wp-content/uploads/ip-geo-api/

If you do not find it, please try deactivate this plugin once and activate again to install it.

If ip-geo-api is not installed even after activation, I have to ask you to download it from https://github.com/tokkonopapa/WordPress-IP-Geo-API (zip file is here: https://github.com/tokkonopapa/WordPress-IP-Geo-API/archive/master.zip) and manually install it like 1. or 2.

Again, I’d apologize the inconvenience. If you have something unclear, please do not hesitate to ask me.

c.f. The document about geolocation API libraries is here.

• This reply was modified 6 years, 4 months ago by tokkonopapa.

Hi again billyf,

Did you find the blocked requests that you want to accept?

As for Jetpack for example, Automattic has variety of IPs: https://ipinfo.io/AS2635

Hi @kradblatt,

I’m sorry about your situation. But all the warnings and errors you reported here are related to the fallback functions for PHP 5.x.

PHP 5.x support for random_bytes() and random_int()

Those will not be executed on PHP 7.0+. And I have confirmed that this plugin will work with PHP 5.2 through 7.2.

So you don’t have to uninstall this plugin.

WP core also includes the same functions (but a little bit old). So I will adopt them instead of new ones in this plugin to prevent users from worrying about.

Thanks for your reporting!

• This reply was modified 6 years, 5 months ago by tokkonopapa.

Hi @mrpeteh,

I’m sorry about poor wording and documentation.

I think you are pointing about the “Disable” on settings tab:

The the answer is:

a) Disable GeoBlock for this type of activity

For example, “Disable” at “XML-RPC” means “This plugin will do nothing about XML-RPC”.

In the past, I was asked about the same thing. So I’ll make it clear in the help pages.

Thank you for the heads up!

Glad to hear that!

Any time, you’ll be welcome!!

Hello again @nesoor,

The url you reported seems to be mixed

https://www.domeinnaamhier.nl/wp-content/plugins

with

/home/domeinnaamhier/domains/domeinnaamhier.nl/public_html/wp-content/themes/swup/custom-script.js?ver=258ba23fb244c7e14faf197b3a67df9f&ip-geo-block-auth-nonce=2405ea2333.

The former part may be a url of some plugin and the later part may be an absolute path to your theme.

So I think you should check the configurations of your plugin and your theme at first. In such a case, the best way to identify the cause is to activate plugins one by one, OR switch your theme to default.

If you let me know about your plugins and theme, I gladly investigate the cause.

• This reply was modified 6 years, 5 months ago by tokkonopapa.

Hi @daro2013,

Thank you for the feedback!

Hi @preacher413,

The URL of RSS feed is handled as public facing page aka front-end in this plugin. So you can manage it by “UA string and Qualification“.

Please find *:FEED in “UA string and qualification” at “Front-end target settings” section:

It means that every user agent can access your feed url. If you don’t find it, please add *:FEED into the above text box.

Thanks for asking.

Hi @dancetolearn,

I’m sorry about this issue.

To confirm the issue, I removed all the Geolocation database files in /wp-content/ip-geo-api/. You might got followings:

I think your site failed to download the DB files from Maxmind and IP2Location, or failed to write them under /wp-content/ip-geo-api/.

So first of all, please execute “Download now” at the bottom of “Local database settings” section.

If downloading is failed, then the error message will appear at each row of DB. If it is successed, then you will find the message like “Last update: October 9, 2018 9:57 pm“.

Again, sorry for the kindless message and the inconvenience.

Hi @starapple,

This plugin can block by countries for both back-end and front-end.

Please find the docs “Back-end target settings” and “Front-end target settings“.

Hi @justbruno and all,

I’m sorry but I mistook the cause of this issue. I believe “500 Internal server error” was caused by the same reason as “Collision with other Plugin” and it had been fixed in 3.0.14 and up.

I hope you another try.

I’d appreciate you to report this issue.
Thanks.

close.

close.

close.