Fix Prowlarr authentication mode conflict using shared Authentik middleware #2

Merged
nathan merged 1 commits from patch/auth_mode_conflict-prowlarr-2026-06-01 into main 2026-05-31 21:26:34 -04:00
Owner

Problem

The Prowlarr service has an auth_mode_conflict: Authentik is configured for forward authentication but the current Traefik setup uses no authentication. Additionally, a dedicated prowlarr_outpost sidecar container is deployed, which duplicates functionality already available via the shared Traefik middleware.

Solution

  • Remove the prowlarr_outpost container to eliminate unnecessary duplication
  • Move Traefik router labels from the outpost container to the main prowlarr service
  • Apply the existing authentik-auth@file middleware to enforce forward authentication
  • Keep the security-headers middleware for defense-in-depth

Changes

  • Removed: prowlarr_outpost service (lines with outpost container definition)
  • Added: Traefik labels to prowlarr service including the authentik-auth@file middleware
  • Updated: Service port label to correctly target the prowlarr application port (9696)

This approach leverages the existing shared Authentik middleware infrastructure and simplifies the deployment by eliminating a redundant sidecar container.


After merging, deploy the change to the affected node (pull the repo and reload the service) to apply it.

## Problem The Prowlarr service has an `auth_mode_conflict`: Authentik is configured for forward authentication but the current Traefik setup uses no authentication. Additionally, a dedicated `prowlarr_outpost` sidecar container is deployed, which duplicates functionality already available via the shared Traefik middleware. ## Solution - Remove the `prowlarr_outpost` container to eliminate unnecessary duplication - Move Traefik router labels from the outpost container to the main `prowlarr` service - Apply the existing `authentik-auth@file` middleware to enforce forward authentication - Keep the security-headers middleware for defense-in-depth ## Changes - **Removed**: `prowlarr_outpost` service (lines with outpost container definition) - **Added**: Traefik labels to `prowlarr` service including the `authentik-auth@file` middleware - **Updated**: Service port label to correctly target the prowlarr application port (9696) This approach leverages the existing shared Authentik middleware infrastructure and simplifies the deployment by eliminating a redundant sidecar container. --- _After merging, deploy the change to the affected node (pull the repo and reload the service) to apply it._
nathan added 1 commit 2026-05-31 21:24:03 -04:00
Remove redundant prowlarr_outpost sidecar container and apply the shared
authentik-auth@file middleware to the prowlarr router. The Authentik forward
auth middleware already exists in the Traefik dynamic configuration and
provides the necessary authentication layer without requiring a dedicated
outpost container per service.
nathan added 1 commit 2026-05-31 21:24:04 -04:00
Remove redundant prowlarr_outpost sidecar container and apply the shared
authentik-auth@file middleware to the prowlarr router. The Authentik forward
auth middleware already exists in the Traefik dynamic configuration and
provides the necessary authentication layer without requiring a dedicated
outpost container per service.
nathan merged commit 1fedfcca01 into main 2026-05-31 21:26:34 -04:00
nathan deleted branch patch/auth_mode_conflict-prowlarr-2026-06-01 2026-05-31 21:26:34 -04:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nathan/homelab#2
No description provided.