To achieve this in my environment I have done the following: I left the Zimbra installation "standard" including the ports (in my case the webmail responds to 8443 port). I tend to avoid manual editing of files. In front of the zimbra server I have created a separate VM with nginx hosting ...

I may suggest to look at options how to add new disk partitions, see example:
viewtopic.php?f=15&t=62472&p=286278#p286278

And there is also a wiki on Zimbra disk space
https://wiki.zimbra.com/wiki/Ajcody-Disk-Full-Issues

I have a reverse proxy using a different nginx server on the same LAN. In my case I experienced that I have to pass the 3 headers: X_Real-IP, X-Forwarded-For and Host to have the web interface work correctly (and logging the correct IP address) By the way memcached is installed ... proxy_pass https:...

I also would like to do this !

Hello -- my single zimbra server runs behind a reverse proxy server (nginx). Anyway to allow the script read the originating IP ? As today it reads as all successful connection are coming from the reverse proxy IP. Try this... where X.X.X.X is your single server ip. # allow /opt/zimbra/log/audit.lo...

Hello -- my single zimbra server runs behind a reverse proxy server (nginx). As today it reads as all successful connection are coming from the reverse proxy IP. I noticed that my Zimbra server audit.log trace correctly the "oip=xxx.xxx.xxx.xxx" but someway the script reports the "$ip...

Kordian -- To stay safe I have z-push installed on the front-end server, Zimbra server stays behind. I also have 1 IP external for all (mail, web, SSL certbot, etc). There I have nginx reverse-proxy setup to direct to different services based on port (local server for z-push, zimbra server for 8443,...

Ok I understood the importance of leaving the root partition for the operating system separate from the application partition, I also decided that I don't need a /home partition therefore I have taken the below steps without touching the stock partition scheme (yes, it's single disk): - created a VM...

Thanks for the prompt reply
But why creating a new partition? can't just resize the existing root partition using the space made available after reducing the home partition ?

Hello I am in a similar situation ... I am running out of space on "root" while I have a large "home" partition from a Centos7 clean install can I just delete the home partition and resize the root partition to use that space ? It's a simple single server installation for 10 user...