Replies: 3 comments
-
The only way I see this working for now is placing your modsecurity-crs container between nginx-proxy and your application (with modsecurity-crs acting as a second reverse proxy), which mean one modsecurity-crs container you'll have to manually configure for every proxyed app. Placing the modesecurity-crs container on the front is not really feasible as you would lose the tls termination and all the automatic tls configuration provided by docker-gen. |
Beta Was this translation helpful? Give feedback.
-
Hello. I replaced the nginx container with owasp/modsecurity:3.0 image, and still use docker and letsencrypt-nginx-proxy-companion. Here is an except of my docker-compose.yml:
In the file proxy/nginx.tmpl I added the following lines:
All the modsecurity config is in files located in ./proxy/modsecurity.d |
Beta Was this translation helpful? Give feedback.
-
Hi, Please note that if the request flow ends with a |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Dear Community,
is there anyone that has done a modsecurity integration on basis of this nginx container set? I am desperately searching for a way to integrate modsecurity (including crs). Would be amazing if its possible to just include a modsecurity docker within a docker-compose.yml and fire it up.
thanks in advance and best regards
satheras
Beta Was this translation helpful? Give feedback.
All reactions