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
After re-configuring service through UI which restarts scheduler to create new config, errors reaching DNSBL servers start appearing in /var/log/bunkerweb/error.log
Hi @Antoninsm, thank you for bringing this issue to our attention! After reviewing it, it appears to be a log entry indicating that a worker exited following a reload. This behavior is expected, as the reload process prevents the timer from starting. It doesn't seem to be a bug, but please let us know if you’re observing any unexpected behavior related to this.
What happened?
After re-configuring service through UI which restarts scheduler to create new config, errors reaching DNSBL servers start appearing in /var/log/bunkerweb/error.log
How to reproduce?
Reconfigure any service through UI and check logs
Configuration file(s) (yaml or .env)
Relevant log output
BunkerWeb version
1.5.12
What integration are you using?
Linux
Linux distribution (if applicable)
Debian 12
Removed private data
Code of Conduct
The text was updated successfully, but these errors were encountered: