Pre- and post-hooks for acme-mailcow, using external reverse proxy?

tblancher

I’m running an external nginx reverse proxy, in another docker compose stack, separate from mailcow. I would like to use the acme-mailcow service to manage mailcow’s certificates, but if I understand correctly the ACME service in mailcow will need to listen on the public HTTP (80/tcp) port in order to verify that the domain points to this host. Is this correct?

I don’t see anywhere where I can set pre- and post hooks in order to temporarily shut down the external nginx instance, where would I put that? Would this even be necessary?

This will be my first attempt at running mailcow, I am probably a few weeks away from running docker compose up -d in the mailcow directory. I’m just trying to make sure I understand the pieces I need to modify to get this working as expected.

D4niel

If you’re using a reverse proxy and something like certbot to create certificates for your other domains, it would probably better if that certbot created the certificates instead of mailcow to have a uniform solution: https://docs.mailcow.email/post_installation/firststeps-ssl/#how-to-use-your-own-certificate

tblancher

I asked the question more pointedly in another thread, this is the best answer from that thread:

D4niel

esackbauer

it would probably better if that certbot created the certificates instead of mailcow

This! That is also the way I do it. I have that automated with Ansible, which disables monitoring, copies the SSL certificates into mailcow and then restarts the 3 docker containers using the certs, and re-enables the monitoring.

tblancher

OK, honestly that does sound simpler than trying to have acme-mailcow manage its own certs. Is there anything I need to do to disable the acme-mailcow service? I figure something in mailcow.conf, but it’s not immediately obvious how to disable that (or any other service component of mailcow).

EDIT: I think I found my answer: Disable LE Entirely