-
Notifications
You must be signed in to change notification settings - Fork 63
Received an unexpected HTTP status code of 401 while using free GeoLite2 Databases #95
Comments
I am unable to reproduce this on 2.5.0. Would you be able to update and try again? If it still happens, please attach the full |
Now I'm using
Since I don't have an account I'm using the provided I upgrade with PPA. On the process dpkg warn me about a change on GeoIP.conf. I choose install the package maintainer's version. Now everything seems to work fine. I compare both uncommented lines and the only difference I've found was
I then remove PPA and downgrade to 2.2.1 (without touching GeoIP.conf) and have same http 401 error. |
If you read the comment on the document, it says:
You need to do this to use the configuration file you linked to in 2.2.1 |
Sorry, I didn't see that. I suggest to add this warning on the above paragraph. Maybe the server could handle this particular case. |
Hello, i have this same problem, I cant see where is error. It is geoipupdate from Centos repo. Can you hint me, please? Thank you `
` |
@rajcz you have to remove the legacy databases from your list as those aren't supported and provided anymore. |
@root360-AndreasUlm is correct. The GeoLite Legacy databases are no longer available from |
Steps to reproduce the bug:
GeoIP.conf
file for free GeoLite2 Databases.This return
Using geoipupdate 2.2.1 over Ubuntu 16.04.4 LTS.
The text was updated successfully, but these errors were encountered: