GeoIP2 (PHP) not working/could not be found

Question

GeoIP2 (PHP) not working/could not be found

ministry-of-code opened this issue 6 years ago · 16 comments

Using the latest Docker Image. In Settings -> Geolocation is says that GeoIP (Php) is not installed. As far as I understood, this should work (the Docker Image Website states that the Image includes geoip/maxmind). When I look into the running Container, I can see a "GeoIPCity.dat" File in the misc directory.

Has someone a hint for me what I can do to activate GeoIP without building the container image by my-self?

Thanks!

Answer 1 · 2019-01-21T23:26:15.000Z

Fixed in #134

Answer 2 · 2019-01-22T11:21:34.000Z

@J0WI great to know, thanks. When will be an updated Docker container image be available? I would like to use the "official" one instead of building my own for each update.

Answer 3 · 2019-01-22T12:13:23.000Z

This depends on the build pipeline of DockerHub. They should be ready within 12 hours.

Answer 4 · 2019-01-23T09:00:34.000Z

This depends on the build pipeline of DockerHub. They should be ready within 12 hours.

@J0WI

As far as I can see, the last build is 13 days ago(?) Are you sure there will be a new build with this fix within the next hours?

https://hub.docker.com/_/matomo?tab=tags

Answer 5 · 2019-01-23T13:02:56.000Z

The build server is still busy with patching CVE-2019-3462

Answer 6 · 2019-01-23T13:05:30.000Z

The build server is still busy with patching CVE-2019-3462

oh wow. Ok, this could take a while...

Answer 7 · 2019-01-28T13:00:53.000Z

@J0WI still no new image in sight... is the pipeline broken?

Answer 8 · 2019-01-28T16:00:19.000Z

Please see docker-library/official-images#5345

Answer 9 · 2019-01-29T09:36:43.000Z

So I am running v3.8.1 from image: matomo:latest now, but I am still facing this issue :(
There is a file called GeoLite2-City.mmdb in /var/www/html/misc but it's timestamp is Jan 22.

Answer 10 · 2019-01-29T10:00:05.000Z

@mcnesium hmm, Jan 22 2019? Sounds okay to me. The database does not need to be ugraded so often - once every couple of weeks is good enough,

Answer 11 · 2019-01-29T10:27:56.000Z

Ok nevermind then, it just stroke me. Anyway, the GeoIP error still exists over here in v3.8.1, so either I messed something up or this issue is not yet fixed.

Answer 12 · 2019-01-29T10:30:57.000Z

I have not tried the latest image yet. If you say it's still broken, maybe @J0WI can give us a hint?

Answer 13 · 2019-01-29T12:43:34.000Z

You need to select GeoIP2 in your geolocation settings.

Answer 14 · 2019-01-29T17:14:26.000Z

great! i gave it a try and it works like a charm. thanks @J0WI

Answer 15 · 2019-01-31T17:25:26.000Z

@J0WI there is no such selection available at my place:

Answer 16 · 2019-02-04T12:53:13.000Z

Just happened to find out that I needed to actually activate the GeoIP-plugin in the plugins section to be able to select it in the geolocation settings. Now it's in the list, can be selected, and the system check no longer complains about not using GeoIP 👍