-
-
Notifications
You must be signed in to change notification settings - Fork 971
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forward Auth with Traefik showing Not Found Page #8932
Comments
UpdateI think i found the issue. in my docker compose, my worker container and server container where of different versions. After making them the same, it seemed to work |
Same problem. I checked and the versions are the same (2024.2.2). I'm using traefik and authentik on a kubernates cluster. |
Make sure that both your worker and server containers are the same version (as they use the same image). Also i am now using 2024.2 which seems to be working. Hopefully that helps! |
For those that stumble across this, I'm using kubernetes with traefik forwardAuth, I had to go into outposts --> integrations and select |
``### Intro
I have been trying to setup Authentik to work with Traefik to authenticate users. I have followed a few guides but seem to keep hitting the same issue. I keep being shown a Not Found page that seems to have no css.
An example is vaultwarden. It works fine in Traefik by itself. However when i add this to its labels:
- "traefik.http.routers.vaultwarden-secure.middleware=authentik@file"
It gives this back
Here is my setup
Traefik version: 2.11.0
Authentik Version: 2024.2.2
Traefik compose
Traefik config Middlewares
Authentik Server compose
Vaultwarden Compose
If i go directly to
http://auth.domain.com:9000/outpost.goauthentik.io/auth/traefik
It also gives a not found page, but with css this timeAuthentik web UI setup
Application
Provider
Outpost
I have been trying to fix this for the past few hours and have gotten no where. If someone knows why this is happening, any help would be appreciated.
Thanks in advance, James
The text was updated successfully, but these errors were encountered: