Unable to setup another bouncer with a new worker

[quentin-fougereau]

Hello,

I'm using crowdsec and the cloudflare-worker-bouncer as docker containers. I was able to successfully setup the the bouncer on one server but now I would like to add a cloudflare-worker-bouncer on another server with the same cloudflare account.

Unfortunately, the new cloudflare-worker-bouncer is failing with the following error :
cloudflare-worker-bouncer | time="2025-01-10T14:15:57Z" level=info msg="Using API key auth" cloudflare-worker-bouncer | time="2025-01-10T14:15:58Z" level=info msg="Cleaning up existing workers" account=REDACTED cloudflare-worker-bouncer | time="2025-01-10T14:16:02Z" level=fatal msg="unable to cleanup existing workers: remove namespace: 'namespace has associated scripts: crowdsec-cloudflare-worker-bouncer-preprod' (10052) for account REDACTED".

I'm using the v0.0.12 of the cloudflare-worker-bouncer and I have added the script_name parameter in the /etc/crowdsec/bouncers/crowdsec-cloudflare-worker-bouncer.yaml file with a different name than "crowdsec-cloudflare-worker-bouncer-preprod".

Do you have any ideas why the bouncer cannot create another worker ?

Thank you

[blotus]

Hello,

It's a limitation of bouncer at the moment.
The KV namespace name is currently hardcoded, so you cannot run 2 different instances of the bouncer for the same account.

A potential workaround would be to have only one bouncer that setup the worker for multiple zones (you can specify multiple zones in the configuration in cloudflare_config.account.zones)

[Lunzya]

Hello,

Is there any update on this topic or is it still hardcoded ?
I have two domains (same account) on two remote locations and still would like to keep them separated in the decision making