#i want to use authentik with traefik. but the application returns 404 when accessing the outpost URL

1 messages · Page 1 of 1 (latest)

young quarry
#

Application and provider are linked. I added the application to the embedded outpost manually. As far as i understand it should be available under https://auth.tdl.com/outpost.goauthentik.io/auth/traefik

➜ curl -i -k https://auth.tld.com/outpost.goauthentik.io/auth/traefik
HTTP/2 404
content-type: text/html; charset=utf-8
date: Tue, 29 Jul 2025 19:23:53 GMT
referrer-policy: same-origin
vary: Accept-Encoding
vary: Cookie
x-authentik-id: a92b01bd2af04742ae949afef450db39
x-content-type-options: nosniff
x-frame-options: DENY
x-powered-by: authentik

Provider setup:
type: proxy => forward auth (Domainlevel)

fluid spindle
#
  • "traefik.http.routers.authentik-output-rtr1.rule=HostRegexp({subdomain:[a-z0-9-]+}.${DOMAINNAME1}) && PathPrefix(/outpost.goauthentik.io/)"
    - "traefik.http.routers.authentik-output-rtr1.service=authentik-svc"
  • "traefik.http.services.authentik-svc.loadBalancer.server.port=9000"
young quarry
#

hello @fluid spindle sry for the late response. I dont understand why authentik needs a rule which matches *.tld.com and the path prefix? does the redirect not always go to auth.tld.com? so no need for this wide regex?

#

arghs and i get more confused the more i read 😄 under the provider settings i see a documentation snipplet for docker compose, which deploys a authentik-proxy service. is this needed for the "simple" hide a service behind authentik auth use case?

fluid spindle