crowdsecurity / cs-cloudflare-bouncer

A CrowdSec Bouncer that syncs the decisions made by CrowdSec with CloudFlare's firewall. Manages multi user, multi account, multi zone setup. Supports IP, Country and AS scoped decisions.
MIT License
50 stars 7 forks source link

the account '' is missing token #165

Closed saschabrockel closed 9 months ago

saschabrockel commented 9 months ago

I did everything as I should have but get the following error directly at the start: 2024-01-18T03:27:39.682127461Z time="18-01-2024 03:27:39" level=fatal msg="the account '' is missing token"

My config:

# Config generated by using /etc/crowdsec/bouncers/crowdsec-cloudflare-bouncer.yaml as base
crowdsec_lapi_url: http://crowdsec:8080/
crowdsec_lapi_key: XYZ
crowdsec_update_frequency: 10s
include_scenarios_containing: [] # ignore IPs banned for triggering scenarios not containing either of provided word
exclude_scenarios_containing: [] # ignore IPs banned for triggering scenarios containing either of provided word
only_include_decisions_from: [] # only include IPs banned due to decisions orginating from provided sources. eg value ["cscli", "crowdsec"]
cloudflare_config:
    accounts:
        - id: 123 #xyz@gmail.com's Account
          zones:
            - zone_id: 123 #xyz.de
              actions:
                - managed_challenge
            - zone_id: 123 #xyz.top
              actions:
                - managed_challenge
          token: xyz
          ip_list_prefix: crowdsec
          default_action: managed_challenge
          total_ip_list_capacity: 9990 # only this many latest IP decisions would be kept
    update_frequency: 10s
daemon: false
log_mode: stdout
log_dir: /var/log/
log_level: info
log_max_size: 0
log_max_age: 0
log_max_backups: 0
compress_logs: null
prometheus:
    enabled: true
    listen_addr: 127.0.0.1
    listen_port: "2112"
key_path: ""
cert_path: ""
ca_cert_path: ""

What is wrong?

saschabrockel commented 9 months ago

Just a docker path fail...