Closed Xeroxxx closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
I don't think this is related to nginx-unauthorrized default conf
but i face similar issue since i've updated to last fail2ban docker image
it appear that any regex containing ".(?i)" fail with that same error
i have a couple that all trigger the same issue
^
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
Fail2Ban loops within the container when you enable nginx-unauthorzed.
Editing and commenting the string, results in a replacement and loop again.
Workaroud start container and edit nginx-unauthorrized conf.
Expected Behavior
Running and not looping.
Steps To Reproduce
Enable jail for nginx-unauthorized
Environment
No response
CPU architecture
x86-64
Docker creation
Container logs