Fix Prowlarr authentication mode conflict using shared Authentik middleware #2
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "patch/auth_mode_conflict-prowlarr-2026-06-01"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 dedicatedprowlarr_outpostsidecar container is deployed, which duplicates functionality already available via the shared Traefik middleware.Solution
prowlarr_outpostcontainer to eliminate unnecessary duplicationprowlarrserviceauthentik-auth@filemiddleware to enforce forward authenticationChanges
prowlarr_outpostservice (lines with outpost container definition)prowlarrservice including theauthentik-auth@filemiddlewareThis 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.