@Glisse1 opened this issue on December 18th 2016

Hello.

I have installed the new GEOIP2 provider, with LITE database, activated the plugin and selected it with no problem. But for some reason also I select this provider, on the front-end (i mean, in stats, live plugin, etc) piwik falls back and gives me just the useless DEFAULT provider. Dont know if its plugins fault, but i`ve been waiting for 3 years to get access to the highly enhanced geoip2 which is 3 times bigger than the old geoip1, so this is a blow for me :(

Screenshots with my own IP case.

@tsteur commented on December 18th 2016

Did you install http://plugins.piwik.org/GeoIP2 ?

@Glisse1 commented on December 18th 2016

Yes, of course, that`s the one.. i looked forward to 3.0 rc because this plugin was not for 2.17x

@tsteur commented on December 18th 2016

@Glisse1 do you mind creating the issue on https://github.com/diabl0/piwik-geoip2 ? We can't provide support for third party plugins.

@s1awa commented on December 19th 2016

@tsteur This plugin uses GeoLite2-City.mmdb file format.

When trying to use "Setup automatic updates of GeoIP databases" with this type of database (http://dev.maxmind.com/geoip/geoip2/geolite2/) The updater fails with an error because of the .mmdb file ending. Can it be added to the autoupdater or does the plugin author needs to write his own update function?

To reproduce upload GeoLite2-City.mmdb to misc folder and use the url (http://geolite.maxmind.com/download/geoip/database/GeoLite2-City.mmdb.gz) to autoupdate.

@Glisse1 commented on December 19th 2016

@s1awa i did not manage to make it work, that is make geolite2-city be the one used instead of the default provider as you can see in the posted screenshots, let alone auto-update. Is this working for you?

@tsteur commented on December 19th 2016

I will reopen the issue for now as it sounds like it might be an issue in Piwik @s1awa ?

@s1awa commented on December 20th 2016

@tsteur I think this ticket is about a different issue not auto update. So I made a new ticket: https://github.com/piwik/piwik/issues/11049

But the problem with this plugin also exists for me: Geoip2 plugin set up and detects my VPN IP 103.15.187.53 in Japan

After visiting the website with the same IP "Visitors in Real-time" shows USA using Default Location Provider

I don't know if this is an issue of Piwik or 3rd party plugin. I hope you can reopen the ticket and confirm it is not an issue of Piwik's rather new 3rd party plugin integration for GeoIP. I also made the plugin author aware of this issue.

@s1awa commented on December 20th 2016

Another example with IP in Germany. It is definitely not using the selected plugin for geoip but the browser language of the "Default Location Provider"

@diabl0 commented on December 24th 2016

@Glisse1 Unfortunately i'm on christmas vacation and cannot investigate this in details, but diabl0/piwik-geoip2 it's very simple - it gets IP address from Piwik (https://github.com/diabl0/piwik-geoip2/blob/master/LocationProvider/GeoIP2.php#L141), runs it thru maxmind-db/reader library () and rewrites results to Piwik expected format. There is no checks for browser accepted language and any other logic (except rewriting region/country codes from ISO 3166-2 Code to FIPS 10.2).

@s1awa currently diabl0/piwik-geoip2 doesn't support autoupdating.

In jan/feb i will probably get back to our piwik integration project and will have more time for more extended testing, and then i'm also planing to implement autoupdate.

@Glisse1 commented on December 24th 2016

So, in february well know if its piwiks fault or plugins.

Looking forward to it, thx

@mattab commented on February 28th 2017

@Glisse1 did you maybe find out if it was a bug in Piwik core or in the plugin itself? Thanks!

This issue was closed on February 18th 2017
Powered by GitHub Issue Mirror