Issue with Geolocation for Internal IPs in Self-Hosted Plausible Analytics

[joaoaxerb]

Hi everyone,

I'm encountering an issue with my self-hosted instance of Plausible Analytics. I've deployed Plausible within an internal network, and I'm monitoring applications that are also on my company's internal network. These applications are only accessible via VPN.

The problem arises when users connect through the VPN. They are assigned internal IP addresses, which Plausible Analytics cannot geolocate since these IPs are internal to our network. This results in a lack of geolocation data for our analytics.

I know I can get the information on the internal IP ranges and figure out the location of each of them. Is it possible to use a custom IP range location database that Plausible can consume? This way, we could map internal IP addresses to their respective locations within our network.

Has anyone else faced a similar issue or found a workaround for geolocating internal IP addresses? Any suggestions or solutions would be greatly appreciated!

Thanks in advance for your help!

[ruslandoga]

👋 @joaoaxerb

Yes, it is possible to use a custom MMDB file. Please see https://github.com/plausible/community-edition/wiki/Configuration#ip_geolocation_db

[joaoaxerb]

@ruslandoga Thank you very much for the quick response!

Also should I remove the MAXMIND_LICENSE_KEY since it takes precedence over IP_GEOLOCATION_DB?

Thanks!

[ruslandoga]

Ah, right. Yes, MaxMind env vars should be removed.