I am running a mail solution downstream from acme-companion that needs to generate its own certificates for IMAP, SMTP and POP3 traffic.
However, when the certbot instance in my mail container tries to complete the HTTP-01 challenge, acme-companion does not forward the request to the respective container. The requests get answered with a 404 from the proxy instead.
This happens because acme-companion claims the .well-known/acme-challenge path in its nginx config and does not redirect any traffic to the downstream container, even when it does not need to regenerate a certificate.
acme-companion image version
acme-companion_1 | Info: running acme-companion version v2.2.0-9-g4786de5
Bug description
I am running a mail solution downstream from acme-companion that needs to generate its own certificates for IMAP, SMTP and POP3 traffic.
However, when the
certbot
instance in my mail container tries to complete theHTTP-01
challenge,acme-companion
does not forward the request to the respective container. The requests get answered with a 404 from the proxy instead.This happens because acme-companion claims the
.well-known/acme-challenge
path in its nginx config and does not redirect any traffic to the downstream container, even when it does not need to regenerate a certificate.acme-companion image version
nginx-proxy's Docker configuration
rendered nginx configuration
Rendered nginx configuration (domain name replaced with
<domain>
:Docker host