Skip to main content
Version: Next

Ports inventory

  • tcp/8080 exposes a REST API for bouncers, cscli and communication between crowdsec agent and local api
  • tcp/6060 (endpoint /metrics) exposes prometheus metrics
  • tcp/6060 (endpoint /debug) exposes pprof debugging metrics

Outgoing connections

  • Local API connects to tcp/443 on (signal push and blocklists pull)
  • Local API connects to tcp/443 on (blocklists pull)
  • Local API connects to tcp/443 on (console management)
  • cscli connects to tcp/443 on to fetch scenarios, parsers etc. (1)
  • cscli connects to tcp/443 on to check latest version available. (1)
  • cscli dashboard fetches metabase configuration from a s3 bucket (
  • Installation script is hosted on over HTTPS.
  • Repositories are hosted on over HTTPS.

(1) - both FQDN are cloudfront entries to crowdsec's github repositories so people avoid hitting github's quotas

Communication between components

Bouncers -> Local API

  • Bouncers are using Local API on tcp/8080 by default

Agents -> Local API

  • Agents connect to local API on port tcp/8080 (only relevant )

If there is an error in the agent configuration, it will also cause the Local API to fail if both of them are running in the same machine ! Both components need proper configuration to run (we decide to keep this behavior to detect agent or local API errors on start).

Local API -> Central API

  • Central API is reached on port tcp/443 by Local API. The FQDN is

Local API -> Database

  • When using a networked database (PostgreSQL or MySQL), only the local API needs to access the database, agents don't have to be able to communicate with it.

Prometheus -> Agents

  • If you're scrapping prometheus metrics from your agents or your local API, you need to allow inbound connections to tcp/6060