Plex thinks a user’s ip has a location in Brusssels but it’s actually Boston and all ip geolocation providers (maxmind, db-ip, ip-api, etc) have it correct. What do I do such that plex fixes it? this doesn’t cause any ‘issues’ per se’, but I’d like it to be correct.
Where exactly are you seeing this?
Hi, thanks for replying - it manifests itself with tautulli, but I confirmed curling plex.tv that it gives the wrong answer:
curl “https://plex.tv/api/v2/geoip?ip_address=199.94.94.1&X-Plex-Token=mytoken”
<location code="BE" european_union_member="1" continent_code="EU" country="Belgium" city="Brussels" time_zone="Etc/UTC" postal_code="1210" in_privacy_restricted_country="1" in_privacy_restricted_region="1" subdivisions="Brussels Hoofdstedelijk Gewest" coordinates="50.85084915161133, 4.348780155181885"/>
yet:
http://ip-api.com/json/199.94.94.1
and
and others give the right answer of Boston.
{"status":"success","country":"United States","countryCode":"US","region":"MA","regionName":"Massachusetts","city":"Boston","zip":"02116","lat":42.3498,"lon":-71.0765,"timezone":"America/New_York","isp":"Emerson College","org":"Level 3","as":"AS13838 Emerson College","query":"199.94.94.1"}
AFAIR, Tautulli uses its own geoIP database. Nothing to do with Plex.
Incorrect.
Tautulli uses Plex’s GeoIP database at https://plex.tv/api/v2/geoip.
Thanks, I’ve reported the issue.
Thank you- should this happen again in the future, is this the best way to report it or is there a self service way?
Is it possible to replace the Plex geolocation database with IP2Location LITE or other free database which is more accurate?
Hi - I have another set to report:
From Plex (says it’s New Jersey)
128.4.33.6
<?xml version="1.0" encoding="UTF-8"?>
<location code="US" european_union_member="0" continent_code="NA" country="United States" city="Greenwich" time_zone="Etc/UTC" postal_code="08323" in_privacy_restricted_country="0" in_privacy_restricted_region="0" subdivisions="New Jersey" coordinates="39.389671325683594, -75.33890533447266"/>
But it’s delaware:
http://ip-api.com/json/128.4.33.6
{"status":"success","country":"United States","countryCode":"US","region":"DE","regionName":"Delaware","city":"Newark","zip":"19711","lat":39.7007,"lon":-75.7419,"timezone":"America/New_York","isp":"University of Delaware","org":"University of Delaware","as":"AS2 University of Delaware","query":"128.4.33.6"}
This should be resolved now.
You should use https://www.ip2location.com/ to confirm any mismatches.
the 1st one is resolved, the 2nd one is not. Presumably because ip2location is wrong on the 2nd one.
But also, speaking of your suggestion - would it not make sense for plex itself to either 1) use that site itself or 2) somehow sync/update it from that site. why should users have to handle/report this?
That’s exactly what we do. Our update had just not processed properly for this month, it’s an automated process but it just was not configured correctly.
