-
Notifications
You must be signed in to change notification settings - Fork 80
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
Latest nginx build not working #201
Comments
It seems that the difference between the image that works and the one that does not is that the latest one executes the entrypoint as nginx, so probably that is why it is failing. If I start with --user root, the latest image works too.
|
Thanks for the report, I'll take a look soon. |
We were also hit by this after our image caches were flushed. We worked around it by using non-standard ports. env:
- name: PORT
value: "8080"
name: SSL_PORT
value: "8443"
|
Should be fixed by #202, we are going to release probably tomorrow with CRS v4.0 🎉 |
@fzipi do you want to close this issue? |
I would wait until we release and people say it is fixed for them. |
@guidugli We released a new version yesterday, can you pull it and see if it fixed the problem? |
It is working now. Thank you. |
Thanks for the feedback. |
I was reinstalling a server and noticed that the latest image is not working. Doing some tests I noticed that running the command below on a 3 month old image works, but it fails with the latest one.
podman run --name abc -p 8080:8080 -p 8443:443 -ti -e PROXY=0 -e ALLOWED_METHODS="GET POST PUT" -e MODSEC_RULE_ENGINE=Off --rm docker.io/owasp/modsecurity-crs:nginx
The error happens on both arm and x64.
Here is the log when running the latest image:
The text was updated successfully, but these errors were encountered: