Which -> Broken Pipe / Could not bind TCP port 80 because it is already in use about certbot-zimbra

[MaxEvron]

Found the beginning of the solution: if an IPv6 address is associated to your domain, certbot will try to use this address for the challenge step.

[maxxer]

do you still need help on this?

[MaxEvron]

Hi,

I'm not sure as I had to proceed to a manual renewal in order to fix the IPv6 issue. For the moment, I have never be able to automatically renew a certificate with the help of your development.
In fact, when an IPv6 AAAA entry is defined for a domain, LetsEncrypt tries to connect to the webserver through IPv6 (without IPv4 failover). This will require Zimbra Proxy (Nginx) to also serve pages to its IPv6 address. I do not know what it will imply in Nginx configuration and, thus, in the included patches to serve the ".well-known" folder.

For the moment, I need to fix an issue with my ISP who does not seem to be able to route IPv6 the right way. I'll get in touch as soon as I have more time to investigate this.

[maxxer]

My prod server runs on IPv6, so you don't need anything special to make it work. Just make sure Zimbra is working in both IPv4 and v6.

https://wiki.zimbra.com/wiki/Configuring_for_IP_V6

If you still need help reopen