Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Still including the update utility in the example conf - utility is now defunct
See original GitHub issue_Issue originally created by user JeffCleverley on date 2019-02-09 11:00:56. Link to original issue: https://github.com/SpiderLabs/owasp-modsecurity-crs/issues/1303._
Type of Issue
Error upgrading geoip database using modsec 3 and nginx
Description
In this ticket #1277
Seems to suggest that the only problem is with older versions of ModSec, 2.9x etc and not 3.0
Your Environment
CRS version v3.1 ModSecurity v3.0.3 (libmodsecurity.so.3.0.3) (https://github.com/SpiderLabs/ModSecurity) Nginx 1.15.8 ModSec v3 Nginx Connector (https://github.com/SpiderLabs/ModSecurity-nginx) Ubuntu 18.04
Confirmation
[x ] I have removed any personal data (email addresses, IP addresses, passwords, domain names) from any logs posted.
Console output
geoip: HTTP Error 404: Not Found
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
User dune73 commented on date 2019-02-09 14:22:15:
Yes it does. Many other things are unstable with ModSec3, but this seems to be OK.
User dune73 commented on date 2019-02-09 14:09:42:
Thanks for the hint about the example conf.
CRS is just fine with the format. It’s with ModSec where the problem lies. ModSec 2 does not support the new format. However, there is now a conversion script by emphazer, that allows you to continue to use the GeoIP DB with ModSec2.