The instructions [here](https://mailcow.github.io/mailcow-dockerized-docs/firststeps-rp) seem to be all that is needed to setup an already existing NGINX instance to proxy for the NGINX instance of mailcow. This will work given these two instances are running on the same machine. I can see two things that will not work with a setup involving two machines: - The HTTP/HTTPS bind is local. - The SSL certificates paths are local to the mailcow machine. The first one is easily fixed by changing the bind IPs. I am not sure how to approach the second one? Shared network drive? Manual copying (I expect this not to work since these certificate will eventually be renewed/updated/replaced)? Does anybody have experience with such a configuration?

NGINX reverse proxy on different machine

FBFmkyulYmvpP2c

The instructions here seem to be all that is needed to setup an already existing NGINX instance to proxy for the NGINX instance of mailcow. This will work given these two instances are running on the same machine. I can see two things that will not work with a setup involving two machines:

The HTTP/HTTPS bind is local.
The SSL certificates paths are local to the mailcow machine.

The first one is easily fixed by changing the bind IPs. I am not sure how to approach the second one? Shared network drive? Manual copying (I expect this not to work since these certificate will eventually be renewed/updated/replaced)? Does anybody have experience with such a configuration?

MAGIC

Hello,

I use a RP acme.sh for my certs on a different machine. What I do is just do a simple scp to different VMs which needs certs and restart affected services using a simple bash script.