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
User was experiencing an issue when enabling the worker on all zones, and then the service was constantly restarting the issue was that a zone had no (A or AAAA to be confirmed) and was causing restart so most likely there an issue in the code, this should be handled.
For now we will update the documentation to showcase this.
The text was updated successfully, but these errors were encountered:
Hi @LaurenceJJones, Thomas here! (PM for Cloudflare Workers KV)
We're noticing that there's a lot of unnecessary usage on Workers KV by various customers of CrowdSec and package crowdsec-cloudflare-worker-bouncer because of this constant restart.
This usage was previously underreported. We're going to be releasing improvements to our billing system which will accurately count this usage (previously this was undercounted by 10x).
Any chance you are planning on getting this fix in the docs + in the code (such as erroring instead of restarting) some time soon?
I also sent an email out earlier today to see how we can work together to issue a fix
Thanks @blotus, and great work on CrowdSec & the cd-cloudflare-worker-bouncer! Some customers also mentioned that their restarts may be related to another issue, such as crowdsecurity/cs-cloudflare-worker-bouncer#40 (comment) (which you seem to be aware of). Can you keep us updated on these fixes when they go out?
(if you need to get in touch directly, firstinitiallastname at cloudflare dot com, or via Twitter/LinkedIn)
User was experiencing an issue when enabling the worker on all zones, and then the service was constantly restarting the issue was that a zone had no (A or AAAA to be confirmed) and was causing restart so most likely there an issue in the code, this should be handled.
For now we will update the documentation to showcase this.
The text was updated successfully, but these errors were encountered: