[GH-ISSUE #1411] Request for WAF Integration like Fail2ban #7902

New issue

Open

opened 2026-03-12 23:12:21 +03:00 by kerem · 3 comments

kerem commented

2026-03-12 23:12:21 +03:00

Owner

Originally created by @devopsminds on GitHub (Oct 28, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1411

Is your feature request related to a problem? Please describe.

It would be great to have WAF including fail2ban kind of stuff which is similar to cloudflare

Describe the solution you'd like

Its mainly to block or protect against DDOS attack

Describe alternatives you've considered
Cloudflare or fail2ban

Additional context

option to block unwanted IPs
Implement Rate limiting
May nice to have custom rules if possible

Originally created by @devopsminds on GitHub (Oct 28, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1411 **Is your feature request related to a problem? Please describe.** It would be great to have WAF including fail2ban kind of stuff which is similar to cloudflare **Describe the solution you'd like** Its mainly to block or protect against DDOS attack **Describe alternatives you've considered** Cloudflare or fail2ban **Additional context** 1. option to block unwanted IPs 2. Implement Rate limiting 3. May nice to have custom rules if possible

kerem added the

enhancement

label

2026-03-12 23:12:21 +03:00

kerem commented

2026-03-12 23:12:31 +03:00

Author

Owner

@enwikuna commented on GitHub (Oct 28, 2025):

Not sure if NGINX is the correct place to do this. I would suggest you use a docker stack with NGINX UI and install a Fail2Ban on your local system. This will block any traffic before it's even reaching any of your services. I highly recommend this. Doing it inside NGINX UI feels wrong and would not give you that flexibility you would need as a sysadmin.

@enwikuna commented on GitHub (Oct 28, 2025): Not sure if NGINX is the correct place to do this. I would suggest you use a docker stack with NGINX UI and install a Fail2Ban on your local system. This will block any traffic before it's even reaching any of your services. I highly recommend this. Doing it inside NGINX UI feels wrong and would not give you that flexibility you would need as a sysadmin.

kerem commented

2026-03-12 23:12:36 +03:00

Author

Owner

@cheewah-cd commented on GitHub (Nov 10, 2025):

I would suggest to use crowdsec rather than fail2ban.
In order to integrate with crowdsec, it needs to use openresty with the crowdsec bouncer.
With some modification with the nginx-ui , it should be able to integrate with the openresty and crowdsec bouncer.
https://github.com/crowdsecurity/cs-openresty-bouncer
What i did is to use the dockerfile from the crowdsec and inject the nginx-ui binary into the image and fix all the requirements from both.
It is able to pass the nginx-ui requirement test.
I hope the nginx-ui can support the crowdsec, since it comes with WAF and IPS in one package instead of nginx + modsec + fail2ban

@cheewah-cd commented on GitHub (Nov 10, 2025): I would suggest to use crowdsec rather than fail2ban. In order to integrate with crowdsec, it needs to use openresty with the crowdsec bouncer. With some modification with the nginx-ui , it should be able to integrate with the openresty and crowdsec bouncer. https://github.com/crowdsecurity/cs-openresty-bouncer What i did is to use the dockerfile from the crowdsec and inject the nginx-ui binary into the image and fix all the requirements from both. It is able to pass the nginx-ui requirement test. I hope the nginx-ui can support the crowdsec, since it comes with WAF and IPS in one package instead of nginx + modsec + fail2ban

kerem commented

2026-03-12 23:12:42 +03:00

Author

Owner

@Buco7854 commented on GitHub (Nov 29, 2025):

I would suggest to use crowdsec rather than fail2ban. In order to integrate with crowdsec, it needs to use openresty with the crowdsec bouncer. With some modification with the nginx-ui , it should be able to integrate with the openresty and crowdsec bouncer. https://github.com/crowdsecurity/cs-openresty-bouncer What i did is to use the dockerfile from the crowdsec and inject the nginx-ui binary into the image and fix all the requirements from both. It is able to pass the nginx-ui requirement test. I hope the nginx-ui can support the crowdsec, since it comes with WAF and IPS in one package instead of nginx + modsec + fail2ban

No need for openresty you can just use libnginx-mod-http-lua:
https://docs.crowdsec.net/u/bouncers/nginx/

@Buco7854 commented on GitHub (Nov 29, 2025): > I would suggest to use crowdsec rather than fail2ban. In order to integrate with crowdsec, it needs to use openresty with the crowdsec bouncer. With some modification with the nginx-ui , it should be able to integrate with the openresty and crowdsec bouncer. https://github.com/crowdsecurity/cs-openresty-bouncer What i did is to use the dockerfile from the crowdsec and inject the nginx-ui binary into the image and fix all the requirements from both. It is able to pass the nginx-ui requirement test. I hope the nginx-ui can support the crowdsec, since it comes with WAF and IPS in one package instead of nginx + modsec + fail2ban No need for openresty you can just use libnginx-mod-http-lua: https://docs.crowdsec.net/u/bouncers/nginx/