Moved Zimbra behind Apache - Mobile site broken

[liverpoolfcfan]

I moved Zimbra behing Apache using the mod_proxy_ajp method described on the wiki.

All looked to be working correctly when I was in the office yesterday.

However, when I tried to access the mobile site from outside, it became apparant that there is a problem with the display - all the images are missing. It seems that the css does not reference the image folder correctly when running in this manner.

Here is an excerpt from Logwatch which shows that the image folder was not found

    404 Not Found
       /img/arrows/ImgNextPage.gif: 3 Time(s)
       /img/arrows/ImgPreviousPage.gif: 2 Time(s)
       /img/mobile/iphone-ext/AppsNav.png: 8 Time(s)
       /img/mobile/iphone-ext/common.gif: 12 Time(s)
       /img/mobile/iphone-ext/common.png: 10 Time(s)
       /img/mobile/iphone-ext/common2.gif: 8 Time(s)
       /img/mobile/iphone/pinstripes.png: 1 Time(s)
       /img/mobile/wm6/AppsNav.gif: 6 Time(s)
       /img/mobile/wm6/tb.gif: 6 Time(s)

Is there any configuration parameter I can set to fix this behaviour ?

Or - is there a problem with the way the URL's are specified in the CSS files ?

[dave_kempe]

I don't know about mod-ajp, but we use nginx on a seperate IP for hosting SSL certs and stuff. I can share those configs for you.
what does mod-ajp buy you that nginx can't do? I am not familiar with it.

[liverpoolfcfan]

Sent you a PM. I would love to see how you set it up. Thanks.

[dave_kempe]

This is from our wiki. It is for setting up a separate nginx instance that proxies into zimbra.
I have removed some of the steps for confidentiality reasons.


For customers who want their own SSL certificate / hostname pointing to Zimbra, we have set up subroute, an nginx reverse SSL proxy box.

This means we can serve the Zimbra web interface out of https://whatever.example.com rather than its "native" https://zimbrahost.domain.net.

This is priced at $20/month which includes the cost of their own GeoTrust RapidSSL certificate and to rent the additional IP address required on subroute for their hostname.

* Decide on a hostname (e.g. whatever.example.com) and get an SSL certificate for it.
* In subroute, drop the SSL certificate and key into /etc/nginx/ssl//.
* Create a new vhost at /etc/nginx/sites-available/.conf. This should contain something like

# Reverse HTTPS proxy to Zimbra for server_name
#
server {
        listen          ***.***.***.***:443;
        server_name     test-ssl.domain.net;

        ssl on;
        ssl_certificate         /etc/nginx/ssl/test-ssl.domain.net/server.crt;
        ssl_certificate_key     /etc/nginx/ssl/test-ssl.domain.net/server.key;

        ssl_session_timeout  5m;

        ssl_protocols  SSLv2 SSLv3 TLSv1;
        ssl_ciphers  ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP;
        ssl_prefer_server_ciphers   on;

        location / {
                proxy_pass         https://zimbrahost.domain.net/;
                proxy_redirect     off;

                proxy_set_header   Host             $host;
                proxy_set_header   X-Real-IP        $remote_addr;
                proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;

                client_max_body_size       10m;
                client_body_buffer_size    128k;

                proxy_connect_timeout      90;
                proxy_send_timeout         90;
                proxy_read_timeout         90;

                proxy_buffer_size          4k;
                proxy_buffers              4 32k;
                proxy_busy_buffers_size    64k;
                proxy_temp_file_write_size 64k;
        }

        # Intercept the following location/s for interface customisations for this hostname,
        # like custom logos or CSS served as static files by nginx.
        #
        location /zimbra/skins/_base/logos {
                root /var/www/zimbra_resellers/test-ssl.domain.net;
        }
}

# Redirect all http requests to https equivalent
#
server {
        listen          ***.***.***.***:80;
        server_name     test-ssl.domain.net *;
        rewrite     ^(.*)   https://$server_name$1 permanent;
}

.. or simply check out one of the existing examples.

* The important bits to change here are the listen IP, server_names, ssl_certificate paths, and the root of their zimbra_resellers folder (or comment out that entire location stanza if no such customisation is required).
Using nginx to replace some images on the fly means resellers can rebrand the login page of Zimbra easily.
To do what you want, you may only need part of this config of course