Open JoeDurand3 opened 2 years ago
Recently I came across a similar issue in Kubernetes. I added customRequestHeaders
as middleware and its worked as expected.
Instead of traefik.http.middlewares.traefik-forward-auth-headers.headers.customrequestheaders.X-Forwarded-Proto=https
try
traefik.http.middlewares.traefik-forward-auth-headers.headers.customRequestHeaders.X-Forwarded-Proto=https
Hello, I'm having an issue with Auth Host + Selective Auth + Google SSO + Offloaded SSL.
First I was having an issue with a Google
400: redirect_uri mismatch
caused by offloading my SSL to my AWS load balancer. So I added a middleware in front of traefik-forward-auth to force https withX-Forwarded-Proto = https
. This got me to the login page, but maybe this compounds my problem, I'm not sure.Next I was having the common issue of an infinite redirect loop mentioned in issues #158 and #149, so I added traefik-forward-auth as it's own middleware:
"traefik.http.routers.traefik-forward-auth.middlewares = traefik-forward-auth-headers,traefik-forward-auth@consulcatalog"
Now if I ping my test service, I see my traefik instance CPU spike through the roof where it promptly crashes with
Exit Code: 137, Exit Message: "OOM Killed"
. I think what's happening is an infinite middleware loop that eats the CPU until it crashes.Note that I'm using Nomad as my orchestrator. Very similar to k8s syntax, please let me know if i need to clarify something.
Here is my trefik + traefik-forward-auth config:
Thanks in advance.