I've tried to let the docker image
nginxproxy/acme-companion and Gitea 1.17.1 automatically configure certificates for me. Both failed on a IPv6-only webserver since they could not reach
https://acme-v02.api.letsencrypt.org/directory. In Gitea, I saw that the DNS lookup for the URL resulted in an IPv4 address. This makes me suspect that there is a problem in the DNS records of
acme-v02.api.letsencrypt.org. However, I have not been able to verify this via
dig. What did work was using
certbot manually. I suspect that
certbot uses another endpoint.
My domain is:
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
nginxproxy/acme-companion and the built-in Gitea manager.