Sebastian Rohkämper

You have to set the external Port too... ``` http: listen: '[::]:8888' # internal port stays the same external_port: 443 # if you are running behind reverse proxy. certificate: /data/tls.certificate.pem...

Did you set external_host? external_host: warpgate.your.domain Maybe your pangoling config denies access to warpgate? Did you set it to authenticated for your auth provider?

Hm. I guess than the developers have to help. Never forged the headers myself and did set it up to work with external_host etc.

I've described my Setup in this Issue: https://github.com/warp-tech/warpgate/issues/1543#issuecomment-3574611139 Maybe it helps?!

Did you set external Port in your http configs correctly? I had similar problems and always overlooked that one. For testing I also changed to .* for regex redirect matching...

I'm busy this weekend, but I'll try to document my setup, so it might be of use for all. I'll try to answer at the beginning of next week.

# WARPGATE SETUP ### docker-compose.yml ```services: warpgate: image: ghcr.io/warp-tech/warpgate:latest container_name: warpgate expose: - 4422 - 8888 volumes: - ./data:/data stdin_open: true tty: true # optional: dns if you use local...