You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run Web-Check behind a Traefik proxy. Since the latest container release it's been throwing a 500 on any/all requests, even favicons. I figured I'd wait a while to see if it was something missed in development but I figured today I'd take a crack at it:
Traefik automatically supplies some headers for forwarded requests, particularly X-Forwarded-Port in this case. Web-Check will always return a 500 if that header exists in a request. I removed the header for now and it's fine:
I run Web-Check behind a Traefik proxy. Since the latest container release it's been throwing a
500
on any/all requests, even favicons. I figured I'd wait a while to see if it was something missed in development but I figured today I'd take a crack at it:Traefik automatically supplies some headers for forwarded requests, particularly
X-Forwarded-Port
in this case. Web-Check will always return a500
if that header exists in a request. I removed the header for now and it's fine:- 'traefik.http.middlewares.web-check_bug-fix.headers.customrequestheaders.X-Forwarded-Port='
The text was updated successfully, but these errors were encountered: