Skip to content
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

[Bug] X-Forwarded-Port header causes Internal Server Error #157

Open
OdinVex opened this issue Jul 3, 2024 · 1 comment
Open

[Bug] X-Forwarded-Port header causes Internal Server Error #157

OdinVex opened this issue Jul 3, 2024 · 1 comment

Comments

@OdinVex
Copy link

OdinVex commented Jul 3, 2024

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:

- 'traefik.http.middlewares.web-check_bug-fix.headers.customrequestheaders.X-Forwarded-Port='

@OdinVex
Copy link
Author

OdinVex commented Jul 9, 2024

I forgot to add - and this should be rather helpful - this did not happen in the 1.0.0 Docker image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant