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
Hi all. I've been testing out this plugin by using the docker-compose.yml in the repo. I basically cloned the repo and started the containers.
In the example docker-compose.yml, I expected the banning for the fail2ban-local.localhost route to be based on exceeding the retries for the specified status codes (below) but this doesn't seem to work for me.
I know that this plugin supports banning based on status codes (ref. #108). However, I find the banning to be always based on the number of requests regardless of the status code(s) specified.
Not sure what's going on. Any help/clarification on this would be very appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all. I've been testing out this plugin by using the
docker-compose.yml
in the repo. I basically cloned the repo and started the containers.In the example docker-compose.yml, I expected the banning for the
fail2ban-local.localhost
route to be based on exceeding the retries for the specified status codes (below) but this doesn't seem to work for me.I know that this plugin supports banning based on status codes (ref. #108). However, I find the banning to be always based on the number of requests regardless of the status code(s) specified.
Not sure what's going on. Any help/clarification on this would be very appreciated.
Beta Was this translation helpful? Give feedback.
All reactions