This is really bugging me, so I’m hoping someone can help me out here.
I have a Wowza server that sits behind a proxy server I do not control.
When I try to stream from that server through the ESA HD player (which has worked for a long time before this proxy came into play) it won’t stream. In looking at the logs, the proxy’s ip address is what’s showing up. On the firewall sitting between the Wowza server and the proxy it looks like all responses are going back to the proxy IP. I can access the Wowza server (in a non-production setting) directly through the firewall and it works, so I know my Wowza configuration is good.
This is streaming VOD and MP3 audio files, nothing live, all over RTMPT (I know there’s a perf hit here, other reasons for this).
I have web servers that sit behind that same proxy, and I don’t have that issue. I have a load balancing engine in front of my web servers and it effectively uses the X-Forwarded-For header mechanism to make sure the web servers know who they’re talking to, and it all works fine.
What am I missing here? I don’t have a ton of experience working with proxies, and like I say I don’t control the one production will ultimately be behind, but is there something I should be having the proxy provider do (like an X-Forwarded-For setting or something similar) to make sure Wowza’s getting the actual client IP and can respond properly?
Thanks!