You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a quite large nginx setup and tried to convert it over to bunkerweb for the additional WAF protection.
We saw that the system itself creates a multitude of configuration files per vhost.
This leads to an increased processing time of nginx -t command.
At a certain point (round about 130 vhosts) nginx -t doesn't finish testing within 3 minutes and breaks down.
Because of this bunkerweb falls to fall back and bunkerweb is no longer functional.
Someone might ask why so many hosts.
We have a software solution that works with white label solutions to provide services for our customers.
Implementations ideas (optional)
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
What's needed and why?
We have a quite large nginx setup and tried to convert it over to bunkerweb for the additional WAF protection.
We saw that the system itself creates a multitude of configuration files per vhost.
This leads to an increased processing time of nginx -t command.
At a certain point (round about 130 vhosts) nginx -t doesn't finish testing within 3 minutes and breaks down.
Because of this bunkerweb falls to fall back and bunkerweb is no longer functional.
Someone might ask why so many hosts.
We have a software solution that works with white label solutions to provide services for our customers.
Implementations ideas (optional)
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: