-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] IPs in WHITELIST_IP gets banned for Bad Behavior in the middle of the night #922
Comments
Hi @axeleroy, thank you for opening this issue. I'll investigate on this and let you know. |
This commit should fix your issue, now the whitelist will be also executed on the default-server 😄 |
So I just have to pull the |
Every change should be listed right here: |
Thanks! A bit off-topic but I read "Add new Metrics core plugin that will allow metrics collection and retrieval of internal metrics", is it documented somewhere already? 👀 |
It's a secret 🤫 (stay tuned for more information on the metrics) 🚀 |
I can confirm the bug has been fixed, thanks! |
@axeleroy Happy to see that you can also confirm it 😄 Let's keep that Issue open until the fix is present on an official release if that's alright with you. |
Hello @axeleroy, Fix should be available on the testing version, more info here : https://docs.bunkerweb.io/testing/ Don't hesitate to test it and tell us if everything is ok ! |
Hello @axeleroy, Fix is now available in the v1.5.6 release. Thanks for your feedback ! |
What happened?
Hello,
I have setup Uptime Kuma to track uptimes of services hosted behind Bunkerweb. Since updating to Bunkerweb 1.5.5 every night near 03:00, my local gateway (through which Uptime Kuma pings my services) gets banned, even though its IP is in the
WHITELIST_IP
environment variable.How to reproduce?
docker-compose.yml
files bellow192.168.0.1
192.168.0.1
is banned and the Uptime Kuma monitor is downConfiguration file(s) (yaml or .env)
bunkerweb/docker-compose.yml
freshrss/docker-compose.yml
Relevant log output
I could not really find anything relevant, other than a few findings that confuse me:
the timing of the Uptime Kuma monitor going down seem to match with the ModSecurity configuration reload
but there are occurrences of the IP getting banned before the monitor reports being down at
2024-02-07 03:05:25
BunkerWeb version
1.5.5
What integration are you using?
Autoconf
Linux distribution (if applicable)
Ubuntu Server 22.04
Removed private data
Code of Conduct
The text was updated successfully, but these errors were encountered: