Are you proxying http or https? I've noticed some incidents with https that make life a little more complicated but it still should be possible. Can you give any more details as to what and how you are proxing but not use real IP's?
Originally Posted by pbruna
Here's a couple of example parameters I've needed to proxy for standard 80 and 443:
For 80 (in apache) I'll use Vhosts as an example:
HTTPS is a bit different:
ProxyPass / http://<internal IP address being proxied to>/
ProxyPassReverse / http://<internal IP address being proxied to>/
Ok I know this doesn't solve a problem but I can confirm that both of these configurations work for reverse proxy using apache externally proxying in to another machine/service using both SSL and standard HTTP. If you can confirm a similar setup it should be safe to assume the proxying is working and there might be another issue.
RedirectMatch ^/$ https://<proxied.to.resolvable.name>/
ProxyPass / https://<proxied.to.resolvable.name>/
ProxyPassReverse / https://<proxied.to.resolvable.name>/
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
Can you access your webclient outside of work through the reverse proxy? (not using the Zimbra Desktop application)