I think my double reverse proxies need some love, specifically forwarding the right headers to get the client IP received by the app.

WAN traffic gets sent to ports 80 and 443 on a Windows Server box with IIS running ARR to reverse proxy to same domain internally (resolved using internal DNS). The internal domain resolves to one of any Linux servers, usually with Nginx doing a second reverse proxy to a docker container or some other hosted app.

All works great, even websockets, but noticed my internal apps are seeing the client IP as that of my IIS (windows) server instead of the actual client IP. Sounds like the issue is with ARR.

Sign in to participate in the conversation

Come as you are, but be prepared to discuss all code, web development, cooking, dogs, and coffee.