Open jeremyj opened 1 week ago
Hi, thank you for opening this Issue and sorry for the late response. Indeed the problem is present and is caused by ModSecurity. We'll dig into it and let you know about our findings. AFAIK it's because of ModSecurity but we'll have a deeper look!
What happened?
When enabling Modsecurity CRS v4 the bunkerweb container takes time to test the nginx config and the
reload
API call from the scheduler times out. This is tested on a 32GB 4 vCPU AWS machine.How to reproduce?
Deploy a Bunkerweb stack on a host that has 50+ virtual hosts attached to the
bw_services
network and labeled with the following:Try changing the Modsecurity CRS from v3 to v4 either with an
env
variable or via the Web UIConfiguration file(s) (yaml or .env)
Relevant log output
BunkerWeb version
1.5.10
What integration are you using?
Docker
Linux distribution (if applicable)
No response
Removed private data
Code of Conduct