Reverse Proxy for Indigo https/ssl

I've gotten ssl working on my server and am trying to configure a reverse proxy so Indigo can use it. When I add the lines

ProxyPass /indigo/ http://localhost:8176/
ProxyPassReverse /indigo/ http://localhost:8176/

to my .conf file and address Indigo as http://serverip/indigo/ the control page comes up but serves the links without the /indigo/ so they don't work.

If I try https, the graphical elements are missing from the returned page.

If I don't include the /indigo/ in the .conf lines, Indigo works but all of my pages get routed to the Indigo server instead of Apache.

Has anybody successfully configured a reverse proxy for Indigo. If so, would you please share what your config lines look like?

Or maybe if I scratch my head long enough, ssl will be included in Indigo and all this won't be necessary.

Thanks.

--Dave

I have begun using Prism Reflector and like it better as a setup than the reverse proxy, but mine is still setup and working. In order to avoid any directory issues what I did was to setup a new Site within Apache (using OS X Server so used the GUI tool, but should be able to be created on any Apache installation). SO, I ended up with a website that responded to your custom URL - indigo.whateverddns.com.

In the configuration I reverse proxy everything:

Code: Select all

<IfModule mod_proxy_balancer.c>
     ProxyPass / balancer://balancer-group/
     ProxyPassReverse / balancer://balancer-group
     <Proxy "balancer://balancer-group">
          BalancerMember http://localhost:8176
     </Proxy>
</IfModule>

I believe that is all I had to add to the configuration. It took me a while to setup as I am no Apache expert! (Obviously discounts getting the certificate setup for that website, but you seem to have the certificate installation in hand).

Adam

Thanks Adam. This appears to have the same problem I had earlier with all traffic getting routed to Indigo. Do you know any way to just reroute traffic intended for indigo?

[jay (support)]

[MODERATOR NOTE] Moved to a more appropriate forum since this is an unsupported configuration.

[matt (support)]

See the instructions on the last post here. There is an IndigoWebServer config file you need to tweak as well if you are changing the root path to /indigo.

Thanks Adam. This appears to have the same problem I had earlier with all traffic getting routed to Indigo. Do you know any way to just reroute traffic intended for indigo?

That is how I solved the same issue you are describing -- I have two subdomains, one for "normal" (non-Indigo) access and one for Indigo access. SO, all traffic to, say, home.adam.com goes to the root web server and all traffic to indigo.adam.com goes to Indigo's web server. Same box and IP and everything, Apache just routes based on the host name.

Adam

See the instructions on the last post here. There is an IndigoWebServer config file you need to tweak as well if you are changing the root path to /indigo.

Success! The key was changing the root path to /indigo. The rest of the instructions didn't work but I was able to do it with

ProxyPass /indigo/ http://localhost:8176/indigo/
ProxyPassReverse /indigo/ http://localhost:8176/indigo/

in my .conf file.