Applying Anubis Selectively with Middleware Manager

Self-hosted Applications
, ,
4

Thank you for the guide. I can’t get this to work, and I’m kinda stuck debugging this. As of now, I have a forwardAuth middleware file named anubis with the following contents:

{
  "address": "http://anubis:8923",
  "authResponseHeaders": [
    "X-Anubis-Reason",
    "X-Anubis-Status"
  ],
  "trustForwardHeader": true
}

My docker-compose.yml contains the anubis service.

  anubis:
    image: ghcr.io/techarohq/anubis:main
    container_name: anubis
    restart: unless-stopped
    environment:
      - BIND=:8923
      - COOKIE_DOMAIN=example.com
      - DIFFICULTY=4
      - POLICY_FNAME=/data/cfg/botPolicy.yaml
    volumes:
      - ./config/anubis/botPolicy.yaml:/data/cfg/botPolicy.yaml:ro

example.com is my top level domain.

I’ve added the anubis middleware to various resources. The resources load perfectly, just without showing the anubis challenge.

I’ve played around with the botPolicy.yaml file to play around winth the status codes.

status_codes:
  CHALLENGE: 403
  DENY: 403

Changing this to the values above does show the anubis challenge page, but it seems to fail to load multiple resources because of the 403 status code (I assume). It appears that the default 200 status code makes Traefik ignore the middleware? Again, I am not sure… any advise would be appreciated!