Reverse proxy the WSE Manager

[Jason_Bailey]

I need to put the Wowza Streaming Engine Manager behind a reverse proxy (e.g. Apache). I’m not looking for Apache specific help, but rather if there are any specifics to what I need to proxy and how.

For starters, I’ll put http://wowza:8088 behind https://apache:443. But to make that work, do I need to proxy any other wowza related ports or URIs / web paths to make the web gui work correctly behind the proxy?

[Andrew_Ramberg]

Hello,

Can you explain your workflow and goals a bit more? We see reverse proxy configurations more often used with players rather then the Manager.

Are you just looking to add SSL to the Manager connection?

Best regards,

Andrew

[Jason_Bailey]

@Andrew Ramberg

We have a fairly standard configuration with many of our administrative web portals (Wowza or otherwise) where we put Apache in front of the application or service and then reverse proxy the connection – partly for enhanced security and access control, but also for central/universal PKI management, SSL certificates and so forth. It makes host-based configuration management a whole lot easier.

Currently we’re just wanting to reverse proxy the WSE manager ltself. Our standard config calls for Apache to bind to port 443/https which would then reverse proxy to WSE Manager. External requests to port 8088 would either be DNATTED to 443 or the WSE Manager would be simply bound to the local loopback, depending on what is most practical.

I have done this before with Wowza and it worked for the most part, but there were additional URIs, paths, connections, etc that I had not built into the configuration, and it hindered the manager’s interface to a certain degree. If I know exactly what type of connectivity is needed to keep WSE Manager working correctly, I can easily reverse proxy the right stuff through.

Best,

Jason

[Jason_Bailey]

Any thoughts on this?