-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nginx: [emerg] "modsecurity_rules_file" directive #110
Comments
Apparently the
Logs:
|
Using the default nginx mainline deb-package via apt from http://nginx.org/packages/mainline/debian/ repo. Attached the output of
|
Hi @schadom, Tested with today's version of the connector and libModSec and everything seems to be working fine. You are welcomed to re-open the issue in case you still face the problem in the most recent version. One hypothesis is that the nginx binary was different from the headers used during compilation. Not sure if nginx keep binary compatibility. |
Hi @zimmerle, thank you very much for having a deeper look into the issue. Will try to recompile libModSec and the connector later today and report back if the problem still persists. Regards |
I am working on adding this feature to Kubernetes Ingress-NGINX. I encountered an issue with this particular feature. When applying
|
The build file used can be found here https://github.com/kubernetes/ingress-nginx/blob/master/images/nginx/rootfs/build.sh |
|
Hi @diazjf, Make sure your modsecurity is compiled with support to curl. Your configuration summary should show something like this:
|
@zimmerle I found the issue. If the FQDN or the URL (content) is not valid I just get
without any context about the real issue. |
Reopening this issue for further investigation. We should consider adding more helpful messages for failed SecRemoteRules download if that's the problem that @aledbf is mentioning in the end. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Bug Description
Nginx 1.13.12 emerges and thus fails to start if using one of the following directives
modsecurity_rules_file
ormodsecurity_rules_remote
in http{}, server{} or location{} context.Versions affected
Steps to reproduce
Building modsecurity and modsecurity-nginx dynamic module for nginx:
After the module has been built without errors, configure modsecurity with
modsecurity_rules_file
ormodsecurity_rules_remote
in nginx.conf. Nginx's config-test will fail with both directives, thus nginx won't start anymore:and
Expected result
Nginx should not emerg on
modsecurity_rules_file
ormodsecurity_rules_remote
The text was updated successfully, but these errors were encountered: