Apache ModProxy to zimbra?

[kbaker]

I have my webserver setup to port 80 and zimbra to port 8080. I have a virtualHost setup with modproxy that passes all requests from mail.MYDOMAIN.com to mail.MYDOMAIN.COM:8080 to connect with zimbra. It bounces around to the ssl port and then ends up back on 8080.

How do I configure modproxy to prevent this. I would like it to stay always on port 80 inside my virtual.

I'd be fine with having the zimbra-apache on port 80 and move tomcat to 8080, so long as I can setup the same virtual. Right now I have the zimbra-apache on the default 7780. Since they are on differnt ports the two instances of apache con coexist.

[marcmac]

zimbra-apache is for the spellcheck server, not for the email app - the email app runs in tomcat only.

[andreychek]

Originally Posted by kbaker

I have my webserver setup to port 80 and zimbra to port 8080. I have a virtualHost setup with modproxy that passes all requests from mail.MYDOMAIN.com to mail.MYDOMAIN.COM:8080 to connect with zimbra. It bounces around to the ssl port and then ends up back on 8080.

How do I configure modproxy to prevent this. I would like it to stay always on port 80 inside my virtual.

One way to do this is to use mod_jk instead of mod_proxy. The mod_jk module is designed to talk directly to Tomcat.

There's a HOWTO on setting this up for Zimbra here on the wiki:

http://wiki.zimbra.com/index.php?tit...%28mod_jk %29

I recently set that up and it works pretty well.

That is, Zimbra runs on port 7080, but none of my users ever see that. As far as the users can tell, requests are all going through port 80.

Good luck!
-Eric

[Maja]

As was stated, mod_jk may work just as well, as that's what it is designed for. Otherwise, if you are set on using mod_prozy, it should be fairly straight forward, although I do typically provide it a URL to redirect off.

For example, in your situation, you would have the following in the configuration for your virtual host:

ProxyPass /zimbra http://mail.MYDOMAIN.COM:8080/zimbra
ProxyPassReverse /zimbra http://mail.MYDOMAIN.COM:8080/zimbra

Dont forget the /service proxy, otherwise you will not be able to log in.

ProxyPass /service http://mail.MYDOMAIN.COM:8080/service
ProxyPassReverse /service http://mail.MYDOMAIN.COM:8080/service

This is how I currently have my Zimbra installation set up; I proxy all requests to my Zimbra server from my primary webserver.

Good luck.

[bbska]

In 3.0.1 I've been unable to get mod_jk to work with zimbra. The connector is there, and is passing things correctly to tomcat, though there appears to be an issue in the soap messaging that causes zimbra to not work correctly.

After about two days of that I went ahead and used mod_proxy and have had no issues.