Subject: |
RE: Run Zenoss 6 behind http server |
Author: |
Ryan Matte |
Posted: |
2019-03-03 13:47 |
So one thing to understand here is that we already use an nginx proxy in Control Center and Resource Manager to route the various requests to their proper hosts and containers. So if you're going to put another proxy / webserver in front of that you'll need to make sure it's not interfering with the proxying that is already happening. You mentioned the port based and vhost based public endpoints in Control Center. Those are basically our nginx configs. The only way I could see what you're trying to do working would be to setup a port based Public Endpoint definition in Control Center for Zenoss.resmgr - zproxy (which represents the Resource Manager UI). Then have your apache proxy forward that port from the CC master server. Using a vhost based public endpoint definition and trying to proxy that may or may not work, since it's already handling it as a vhost at that point. It's not a service running on a port that you can just hit directly like you could with a port based approach.
------------------------------
Ryan Matte
------------------------------
Subject: |
RE: Run Zenoss 6 behind http server |
Author: |
Jad Baz |
Posted: |
2019-03-04 04:39 |
I think I understand this but the issue remains.
The only way I can see my problem is solved if I can redirect traffic internally: Apache is the only exposed https service and Zenoss is accessible via http from localhost.
A request to https:<FQDN>/zenoss goes internally to some port
I still don't understand how this is possible in Zenoss 6.
------------------------------
Jad
------------------------------