How to configure X-Forwarded-For and X-Forwarded-Proto in v2?

I want to configure X-Forwarded-For and X-Forwarded-Proto similar to this post such that I could run my uvicorn server with --proxy-headers. I checked the relevant documentation and configure my target server's container like the following (the last two labels are of interest):

docker create --name brickserver-playground-deployment \
    --rm \
    -it \
    -e LOG_LEVEL="debug" \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v $PWD:/app \
    -e ENABLE_SSL=false \
    --entrypoint /app/docker/ \
    --privileged=true \
    --label "\"myserver\") && ( PathPrefix(\"/docs\") || PathPrefix(\"/dummy-frontend\") || PathPrefix(\"/auth\") || PathPrefix(\"/brickapi\") )" \
    --label \
    --label \
    --label \
    --label "" \
    --label "" \
    --label "traefik.http.middlewares.testHeader.headers.customrequestheaders.X-Forwarded-Proto=https" \

I checked the config through traefik api and confirm the everything are configured as is. But it seems like it's not working even with such a simplest setting.

I'm wondering:

  • What's wrong with above configuration? Why it doesn't work?
  • How to configure the header value dynamically (just like in the above nginx tutorial) according to the user's request rather than hardcoding as what I'm doing in the sample.

@reapor_yurnero unfortunately I can't provide yet any response, I'm struggling with a similar issue.

What I would recommend is maybe got a step back, and use traefik whoami docker image until you get the desired values in your headers.

Good luck!


you have to configure the forwardedHeaders section in the entrypoints:

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.