If on the other hand, you have been running your Mautic installation for a while, you probably haven’t noticed any problems, that’s because you already have the database on your server, so everything seems to be running fine, however, your database is already old and will get older over time unless you update it again. If you are using the data provided by Maxmind GeoLite2 on your campaigns, for example to filter by country or city, or if you use it in your reports, then it is imperative that you follow this process immediately so your campaigns keep working flawlessly and your reports are kept accurate. This issue is not going to bring your server down or cause any big problems, however, it affects every single Mautic installation out there, so it really is a good idea to fix it ASAP.
This guide will work best with Ubuntu and most Debian derivatives, but non-Ubuntu users might need to adapt here and there. NOTE: This entire blog is dedicated to Mautic and other FOSS Marketing software, however, this particular post should work perfectly fine for any Linux based server using the MaxMind GeoLite2 or GeoIP databases as the provided instructions don’t use any of the Mautic code at all. In this post you’ll find 5 simple steps to fix the Maxmind Geolite2 and GeoIP issue in under 10 minutes, so you can make your Mautic installation compliant with the new process and automate obtaining the Geolite2 database for your Mautic installation.
The difference is simple, now you need to provide your credentials, but it completely changes the process to update your IP database.
That’s because Maxmind has changed the method to obtain the latest updated databases from them. If you just installed Mautic in 2020, you might have noticed the Maxmind IP lookup doesn’t seem to work anymore.
0 kommentar(er)
