I'm setting up a Zimbra server with DRBD for a high availability cluster under CentOS. I seem to have gotten the Zimbra install working with cluster in what I can only assume will work at this point.
My next problem is that I have to host a number of websites alongside Zimbra. 3 to start with to be exact.
I was attempting to follow this guide:
ZimbraApache - Zimbra :: Wiki
And I got to the section:
Which I believe is what I want to do as I want the HTTPS side accessible.
Sharing both HTTP and HTTPS between both Zimbra and Apache using Different Domain Names
The problem that I run in to is that the definition of the Zimbra virtualhost doesn't appear to be forwarding to the HTTP side, but rather the HTTPS side.
The guide's definition is as follows:
And my definition is as follows:
CustomLog /var/log/httpd-access.log common
Redirect / https://mail.yourdomain.com:60443/
CustomLog /var/log/zimbra-access.log common
The end result, is when I type in the current internal IP address (behind a firewall so I had to set up Split DNS, which appears to be working at this stage of the game) and the HTTP port number, it does its certificate warning and takes me to the HTTPS site.
CustomLog /opt/www/logs/lrcomm.access.log combined
ProxyPass / http://zimbra.fqdn.com:81/
ProxyPassReverse / http://zimbra.fqdn.com:81/
CustomLog /opt/www/logs/zimbra-lrcomm-access.log common
Now, I'm aware that my directories are /opt/www and it's made that way due to a partitioning screw up I did so I'm content with keep it all on the same partition and mount point. All necessary paths (to my knowledge have been changed).
I've triple checked and my HTTP Zimbra port is 81 and my HTTPS Zimbra port is 51111. But, I haven't even set up the HTTPS redirect as I'll probably never need it, I'll just tack on the port number to any links I direct its way.
Unfortunately, I'm dependent on someone else to give me a public static which they haven't done yet so none of this is public just yet, but I don't see how that would have anything to do with it. Doesn't make sense as to why HTTP would be redirecting to HTTPS, unless I misunderstood the section title and did the wrong steps.
So am I missing something?