LogoLogo
HomeDiscordYouTubeDisclaimer
  • CrowdSec
    • Docker Compose
      • Traefik Bouncer
        • Authelia Collection
        • Vaultwarden Collection
      • Dashboard
    • Unraid
      • Traefik Bouncer
        • Authelia Collection
        • Vaultwarden Collection
        • Nextcloud Collection
      • CrowdSec-Dashboard
      • Dashboard
    • Useful Commands
  • 🎯DO I NEED AN UPDATE?
    • Update Me!
  • ❗Disclaimer
    • Read Our Disclaimer
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. CrowdSec
  2. Unraid
  3. Traefik Bouncer

Authelia Collection

PreviousTraefik BouncerNextVaultwarden Collection

Last updated 3 years ago

Was this helpful?

Now we have to tell Authelia to write its log file to the shared folder, so that crowdsec can parse it and respond accordingly.

First, edit your Authelia docker template, to map the Authelia log output folder to the shared folder :

Then edit the configuration.yml file in Authelia appdata folder (appdata/authelia), in order to enable logging. (The values maybe already there but edited out, so just search for them).

  log:
  ## Level of verbosity for logs: info, debug, trace.
  level: info

  ## Format the logs are written as: json, text.
  format: json

  ## File path where the logs will be written. If not set logs are written to stdout.
  file_path: /var/log/crowdsec/authelia.log

  ## Whether to also log to stdout when a log_file_path is defined.
  keep_stdout: true

And then, edit your docker crowdsec template to enable Authelia collection, by adding LePresidente/authelia to the COLLECTIONS variable :

And finally, edit your acquis.yml file in your crowdsec's appdata folder (appdata/crowdsec) to add these lines : (don't leave any empty spaces)

---
filenames:
  - /var/log/crowdsec/authelia.log
labels:
  type: authelia

Restart your containers, crowdsec and authelia.

Use the "" cscli collections list and cscli metrics to check your collections and metrics, that should be ok!

Useful Commands