Hi. As Iain has noted as a comment to the ip2nation documentation, installing 2.52 deletes any current ip2nation database. I only discovered it because I noted my database sql backup had suddenly shrunk by 3-400KB, and diffed to investigate.
So, I tried the button to update, in the ip2nation module. Actually, there are two buttons.
- The upper right medium grey one, labelled Update IP Database, appears to do nothing - even if I monitor the ip2nation cache.
- The lower left red button, Update, gives screen progress action, saying it’s downloading, and then unpacking the data. However, then nothing happens, and there are no more notifications. The EE ip2nation table remains empty.
Since I noticed that the files then present in the ip2nation cache looked very small (under 1Kb) I tried manually downloading the GeoIPCountryCSV.zip and GeoIPv6.csv.gz files, which were healthily each over 500KB, and then ftping them to the website ip2nation cache, with following results:
- refresh ip2nation module page. Nothing happened.
- tried Update IP Database button. Nothing happened.
- tried red Update button. My uploaded files were replaced with under-1kb files, as before.
I had saved downloads of these small zip/gzip files, and looking in them with a text editor, found they had html which summarized, says 403 forbidden, rate limit exceeded, please try again in 24 hours.
Summary:
- apparently my host location has used the ip2nation service too often; not a surprise as it’s an active shared hosting for EE.
- there doesn’t seem to be a manual workaround, though some previous support conversations have seemed to hint that there’s a way to proceed by downloading your own files as I did.
This isn’t critical to me, but I imagine it is to others. What do you propose as a way to proceed manually?
Obviously the ‘wait 24 hours’ is potentially much looser than that, while ip2nation evidently could fail at a critical moment for a site, when someone just tries to update the database, and loses their data.
Regards,
Clive