← Directory

GeoIP Update

GeoIP Update is a command-line tool by MaxMind that automatically refreshes GeoIP2 and GeoIP Legacy binary databases, eliminating manual database maintenance…

  • Other
  • Tools & Utilities
GeoIP Update is a command-line tool by MaxMind that automatically refreshes GeoIP2 and GeoIP Legacy binary databases, eliminating manual database maintenance for geolocation services.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

73/100 Good

Maintained
100last commit 9 days ago
Popular
60971 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 17 days ago

GitHub stars
971
Open issues
14
Last commit
2026-10-05
Latest release
v8.0.0
License
Apache-2.0
Activity
declining

Checked 8 days ago - source: GitHub (maxmind/geoipupdate)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Enter your MaxMind account details Before starting, set AccountID, LicenseKey, and EditionIDs (the database names you want, like GeoLite2-Country) in the geoipupdate config or container env vars. Without valid credentials and database names, geoipupdate stops and your app has no IP location data. source
  • Save the IP files in a safe folder Set DatabaseDirectory to a folder that survives updates or container restarts, such as /var/lib/GeoIP or a mounted volume in Docker. If that folder is wiped, the downloaded IP database files are gone and geoipupdate will need to fetch them again. source
  • Keep license keys out of visible files If you run it in Docker, put the MaxMind account ID and license key in Docker secrets or env files instead of writing them directly in the compose file. That keeps your paid-license credentials from leaking if you share or back up your setup. source

Fetched 17 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What configuration values are required before running geoipupdate?

Set AccountID, LicenseKey, and EditionIDs, such as GeoLite2-Country, in the geoipupdate config or container env vars. Without valid credentials and database names, geoipupdate stops and your app has no IP location data.

Where should the downloaded GeoIP database files be stored?

Set DatabaseDirectory to a folder that survives updates or container restarts, such as /var/lib/GeoIP or a mounted Docker volume. If that folder is wiped, the downloaded IP database files are gone and geoipupdate will need to fetch them again.

What should I check if geoipupdate reports an invalid account ID or license key?

The source says the download from the server to MaxMind may have been blocked. Once the server was authorized to perform downloads, the update worked.

Is it a problem if the geoipupdate container exits right after starting?

In the Sentry self-hosted geoipupdate deployment, it is normal for the geoipupdate container to exit soon after startup because the update is a one-off batch process and not a long-running job.

Answers sourced from github.com, github.com, stackoverflow.com

Community

Collected 16 days ago - public community threads