Let's Encrypt renewal fails despite a working site: check port 80, AAAA records and HTTP-01
A site can appear fully functional in the browser while automatic Let's Encrypt renewal keeps failing, because the HTTP-01 challenge is run from outside the browser's path. Validation requires the ACME challenge file to be reachable over plain HTTP on port 80, from several locations, so a closed port 80 in a server, provider or geo-blocking firewall will cause it to fail. A stale or incorrect AAAA record can also send validation to the wrong server over IPv6, since Let's Encrypt prefers IPv6 when it is present. The article recommends checking DNS records against the server's real addresses, testing the challenge file with curl over both IPv4 and IPv6 from an external machine, and running a certbot dry run. If port 80 must stay closed, DNS-01 validation through a TXT record is suggested as an alternative, provided the DNS provider offers an API.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in