C
CrowdSec•2mo ago
Artist201

crowdsec X dockerized caddy adding to decision lists but not blocking

hello. i am trying to set a contrainarized caddy and another crowdsec. and managed to make it work detect and read out the logs from stdout. however am still able to access the domain... even though i should be blocked am not sure what is happening. am using coolify btw global settings: 
{
    servers {
            client_ip_headers X-Forwarded-For
            trusted_proxies static private_ranges
            trusted_proxies_strict
    }
    order crowdsec before respond
    crowdsec {
            api_url http://crowdsec-id:8080
            api_key "somekey"
            ticker_interval 3s
            appsec_url http://crowdsec-id:7422
            #disable_streaming
            #enable_hard_fails
    }
    log {
        output stdout
    }
}
{
    servers {
            client_ip_headers X-Forwarded-For
            trusted_proxies static private_ranges
            trusted_proxies_strict
    }
    order crowdsec before respond
    crowdsec {
            api_url http://crowdsec-id:8080
            api_key "somekey"
            ticker_interval 3s
            appsec_url http://crowdsec-id:7422
            #disable_streaming
            #enable_hard_fails
    }
    log {
        output stdout
    }
}
No description
2 Replies
Artist201
Artist201OP•2mo ago
No description
Artist201
Artist201OP•2mo ago
note that the IP is a Cloudflare cf-connection-ip caddy labels: 
      - crowdsec.enable=true
      - crowdsec.labels.type=caddy
      - crowdsec.enable=true
      - crowdsec.labels.type=caddy
app labels 
      - 'caddy_0.log.output=stdout'
      - crowdsec.enable=true
      - crowdsec.labels.type=test1
      - 'caddy_0.crowdsec='
      - 'caddy_0.log.output=stdout'
      - crowdsec.enable=true
      - crowdsec.labels.type=test1
      - 'caddy_0.crowdsec='
ahhh nvm i fixed it app label should be 
      - 'caddy_0.handle_path.crowdsec='
      - 'caddy_0.handle_path.crowdsec='

Did you find this page helpful?