Dear MaxMind customer,We’re writing to follow up on our email from August. Between September 1 and 18, we saw GeoIP download requests from your account that are not being sent with HTTPS (see details below). To improve our server infrastructure and allow for better performance and efficiency, MaxMind will begin requiring HTTPS for GeoIP download requests in March 2024. To help customers get ready for this change, we will have a planned, temporary enforcement of this policy on October 17, 2023.What is the policy?
What do I need to do? To ensure that you can continue to download GeoIP databases, please make the change(s) listed below prior to October 17, 2023. The policies will be permanently enforced in March 2024: You sent 3 GeoIP database download queries to the endpoint http://download.maxmind.com/app/geoip_download. Note that these queries were sent without using the more secure HTTPS protocol. Update your integration to send these GeoIP database download queries to https://download.maxmind.com/app/geoip_download. Note that you should be using the more secure HTTPS protocol. What if I need more help? If you need more help or have additional questions, please contact us at [email protected]. What’s next? On October 17, 2023 we will conduct a planned, temporary enforcement of our API policies. If you have not made the requested changes before this date, you may experience a period in which database download requests fail. We will post additional details about the planned enforcement to our release notes. Thanks for your attention. Sincerely, The Team at MaxMind |
$config{cc_country} = "http://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-Country-CSV&suffix=zip&license_key=$config{MM_LICENSE_KEY}";
$config{cc_city} = "http://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-City-CSV&suffix=zip&license_key=$config{MM_LICENSE_KEY}";
$config{cc_asn} = "http://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-ASN-CSV&suffix=zip&license_key=$config{MM_LICENSE_KEY}";
$config{cc_country} = "https://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-Country-CSV&suffix=zip&license_key=$config{MM_LICENSE_KEY}";
$config{cc_city} = "https://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-City-CSV&suffix=zip&license_key=$config{MM_LICENSE_KEY}";
$config{cc_asn} = "https://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-ASN-CSV&suffix=zip&license_key=$config{MM_LICENSE_KEY}";
systemctl restart lfd
Yes, that's what the CSF team said.Is this going to be fixed before 10/17/2023?
Yes the fix was pushed automatically last week.It's now one week until deadline. Has this been fixed?
No there is nothing that you need to do. CSF updates automatically by default so you already have the fix.That's awesome. Thank you so much. Will Juggernaut take this update automatically, or is there anything we need to do?
You can search for the IP address in the IPtables search on the dashboard. If it's being blocked by one of the firewall country blocks then it should tell you. You can also use the following command on the command line:What is the best way to view GEO action reports? We have some challenges where at times a client will timeout, and we need a way to verify that they are not being blocked by GEO. When I use a VPN to go to a forbidden GEO location, and then try to access our sites, it gets blocked, but I can't find the IP I was using in the Juggernaut logs.
Thanks in advance
csf --grep <ip_address>
# csf --grep 205.210.31.156
Table Chain num pkts bytes target prot opt in out source destination
No matches found for 205.210.31.156 in iptables
IPSET: Set:bl_DSHIELD Match:205.210.31.156 Setting:DSHIELD file:/etc/csf/csf.blocklists
IPSET: Set:chain_DENY Match:205.210.31.156 Setting: File:/etc/csf/csf.deny
ip6tables:
Table Chain num pkts bytes target prot opt in out source destination
No matches found for 205.210.31.156 in ip6tables
ipset list | more