Replies: 2 comments
-
Hello, I am roughly in the same boat as you. I use SWAG from Linuxserver.io which is nginx based. |
Beta Was this translation helpful? Give feedback.
-
I actually ended up solving my problem, turns out I had forward auth middleware set up in Traefik that I forgot to remove when switching from proxy provider to OIDC. Don't know much about using a forward proxy like you are trying to achieve. Hopefully you work it out soon |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
I tried to set up audiobookshelf with authentik in front, using OIDC, but when I launch the audiobookshelf domain, I get a 404 error. The authentik log shows the following error:
{"auth_via": "unauthenticated", "domain_url": "audiobookshelf.domain.com", "event": "/outpost.goauthentik.io/auth/traefik", "host": "audiobooks.domain.com", "level": "info", "logger": "authentik.asgi", "method": "GET", "pid": 53, "remote": "...", "request_id": "*******************", "runtime": 4, "schema_name": "public", "scheme": "https", "status": 404, "timestamp": "2024-05-08T10:59:22.739126", "user": "", "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:125.0) Gecko/20100101 Firefox/125.0"}
Can anyone help me work out why my audiobookshelf application isn't accessible when I try to protect it with authentik? My other applications that are protected with forward auth proxy providers work well. I also use traefik reverse proxy if this is relevant
Beta Was this translation helpful? Give feedback.
All reactions